# Unable to open file for editing

**URL:** <https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925>\
**Category:** Support\
**Created:** [June 12, 2018, 5:01am UTC](https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925 "2018-06-12T05:01:05Z")\
**Posts on this page:** 9\
**Page:** 1

<div class="post-metadata">

**Author:** ![Morningstar](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e480ec/32.png) [@Morningstar](https://community.mp3tag.de/u/Morningstar)\
**Post date:** [June 12, 2018, 5:01am UTC](https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925/1 "2018-06-12T05:01:05Z")

</div>

Hey guys,

I just updated to mpetag v2.88a on a Win 7 system and it keeps giving me unable to open file for editing errors and spewing out temp files.

Is there a fix for this or a way I an go back to 2.87?

---

<div class="post-metadata">

**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\
**Post date:** [June 12, 2018, 5:02am UTC](https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925/2 "2018-06-12T05:02:43Z")

</div>

How long is the filename?  
Have you checked the file for integrity?  
Are the access rights OK?

---

<div class="post-metadata">

**Author:** ![Morningstar](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e480ec/32.png) [@Morningstar](https://community.mp3tag.de/u/Morningstar)\
**Post date:** [June 12, 2018, 5:07am UTC](https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925/3 "2018-06-12T05:07:37Z")

</div>

All of the file names are twenty characters long, file integrity is good, access rights are fine.

I never had a problem before I updated yesterday and I'm working with the exact same files.

---

<div class="post-metadata">

**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\
**Post date:** [June 12, 2018, 5:17am UTC](https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925/4 "2018-06-12T05:17:13Z")

</div>

> [@Morningstar](#):
>
> I just updated to mpetag v2.88a

So perhaps V2.88b would be worth a try. That is the latest version.

Ah yes: editing files while other programs like WMP accessing the same files at the same time frequently leads to such errors.

---

<div class="post-metadata">

**Author:** ![Morningstar](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e480ec/32.png) [@Morningstar](https://community.mp3tag.de/u/Morningstar)\
**Post date:** [June 12, 2018, 5:19am UTC](https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925/5 "2018-06-12T05:19:29Z")

</div>

I just dug out the v2.82 installer out of the depths and problem solved.

Thanks though

---

<div class="post-metadata">

**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\
**Post date:** [June 12, 2018, 5:22am UTC](https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925/6 "2018-06-12T05:22:29Z")

</div>

> [@Morningstar](#):
>
> problem solved

I doubt that.  
If there really is a bug in MP3tag V2.88a why don't you help to investigate it and describe how to reproduce it?

---

<div class="post-metadata">

**Author:** ![Morningstar](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/m/e480ec/32.png) [@Morningstar](https://community.mp3tag.de/u/Morningstar)\
**Post date:** [June 12, 2018, 5:31am UTC](https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925/7 "2018-06-12T05:31:32Z")

</div>

Simply put, the glitch in my install is pervasive and made it basically impossible for me to use the program. I don't use WMP and the files re not being accessed by any other programs. There is obviously a bug in the updated code for version 2.88 since my issue goes away by rolling back.

From what I can see there is a broken object in the file update process, as the temp files with my edits are just orphaned in the directory. Without looking through the code, I would suggest that the finalizing process should be debugged.

---

<div class="post-metadata">

**Author:** ![ohrenkino](https://community.mp3tag.de/user_avatar/community.mp3tag.de/ohrenkino/32/4843_2.png) [@ohrenkino](https://community.mp3tag.de/u/ohrenkino)\
**Post date:** [June 12, 2018, 5:35am UTC](https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925/8 "2018-06-12T05:35:17Z")

</div>

I use V2.88b on systems with W10, W7, W8, installed locally and as portable version and I don't have the problem that you describe.  
So it would be helpful to find out where the differences are between your system and at least 3 other (working) ones.

---

<div class="post-metadata">

**Author:** ![system](https://community.mp3tag.de/uploads/default/original/2X/c/ce7035d426cb755a7916793326d23b465222a407.png) [@system](https://community.mp3tag.de/u/system)\
**Post date:** [February 9, 2026, 12:27pm UTC](https://community.mp3tag.de/t/unable-to-open-file-for-editing/41925/9 "2026-02-09T12:27:28Z")

</div>


