# The dreaded File xxx cannot be opened for writing. error

**URL:** https://community.mp3tag.de/t/the-dreaded-file-xxx-cannot-be-opened-for-writing-error/54061
**Category:** Support
**Created:** [August 13, 2021, 11:56am UTC](https://community.mp3tag.de/t/the-dreaded-file-xxx-cannot-be-opened-for-writing-error/54061 "2021-08-13T11:56:56Z")
**Posts on this page:** 1
**Showing post:** 2

<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: [August 13, 2021, 12:14pm UTC](https://community.mp3tag.de/t/the-dreaded-file-xxx-cannot-be-opened-for-writing-error/54061/2 "2021-08-13T12:14:48Z")

</div>

> [@donwiss](#):
>
> With no Abort button, I have to repeatedly click ignore for every file.

How should MP3tag guess that you have even more files in stall that are apparently up the spout?

I would seriously consider that the files have been corrupted. Looking at

> [@Can't clear Track 1, etc. in Comment/Description field](https://community.mp3tag.de/t/cant-clear-track-1-etc-in-comment-description-field/54021/):
>
> I like to clear junky tags. Here is a header string that I can't clear: 54 67 79 77 77 0 0 0 12 0 0 0 101 110 103 0 84 114 97 99 107 32 50 6 C O M M Nul Nul Nul FF Nul Nul Nul e n g Nul T r a c k [space] 1 I tried adding the field COMM, and some variations with eng, but they didn't get it.

which found its root cause in non-standard ID3 tags instead of only vorbis comments, I wonder what could be wrong with the new set of files.  
I think that foobar2000 has utilities to repair flac files.

---

_[View the full topic](https://community.mp3tag.de/t/the-dreaded-file-xxx-cannot-be-opened-for-writing-error/54061)._
