# "Self-deleted" tag and mapping panel

**URL:** https://community.mp3tag.de/t/self-deleted-tag-and-mapping-panel/48565
**Category:** Support
**Created:** [April 14, 2020, 7:01pm UTC](https://community.mp3tag.de/t/self-deleted-tag-and-mapping-panel/48565 "2020-04-14T19:01:39Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![davialves](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/d/c68b51/32.png) [@davialves](https://community.mp3tag.de/u/davialves)
#### Post date: [April 14, 2020, 7:01pm UTC](https://community.mp3tag.de/t/self-deleted-tag-and-mapping-panel/48565/1 "2020-04-14T19:01:39Z")

</div>

Days ago, after updating Mp3tag to version 3.00, when opening the application I came across a incompatibility warning and that it was necessary to update to 3.01. That's what I did, but then I realized that all the mapping settings I did were gone. I thought it happened because of the two consecutive updates, so I accepted.

Until, days later, I notice that my tag panel returned to an older version that I had edited before ... however, there was no plausible justification for this, since I had not updated or tampered with the files or anything. Again, I ignored and redid the tags.

Today, I went to edit the tags of a song by opening Mp3tag through the Windows context menu, and a warning appears saying "the file cannot be edited because it is corrupted" (which was not true). I went to open Mp3tag and: all the tags in the tag panel are gone. Without justification. I didn't touch the AppData folder or anything.  
I would like to know if there is an explanation for these errors and I would like you to correct them. Thanks.

---

<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: [April 14, 2020, 7:13pm UTC](https://community.mp3tag.de/t/self-deleted-tag-and-mapping-panel/48565/2 "2020-04-14T19:13:08Z")

</div>

> [@davialves](#):
>
> I came across a incompatibility warning

Could it be that you installed MP3tag in a different way, standard instead of portable or vice versa? This would explain the lost settings.  
If you changed that then the old settings should still be in the old installation location.  
As I use MP3tag without any problems, you would have to supply way more evidence that you really encountered an MP3tag problem instead of a local one.  
E.g. how do you know that the file was not corrupted? Did you test it? Which program did you use to do the test? How did the program tell you that everything is ok?  
What kind of files are we talking about?  
Could you still supply it so that others could have look at it?

---

<div class="post-metadata">

### Author: ![davialves](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/d/c68b51/32.png) [@davialves](https://community.mp3tag.de/u/davialves)
#### Post date: [April 15, 2020, 12:40pm UTC](https://community.mp3tag.de/t/self-deleted-tag-and-mapping-panel/48565/3 "2020-04-15T12:40:55Z")

</div>

As I recall, I always installed it in standard mode, never portable. And it was an mp3 file, which is not corrupted as it can be heard normally.

---

<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: [April 15, 2020, 12:46pm UTC](https://community.mp3tag.de/t/self-deleted-tag-and-mapping-panel/48565/4 "2020-04-15T12:46:07Z")

</div>

So it is not quite clear whether you installed in a way that kept the old settings or not.  
I would now look for old installation folders of MP3tag and see if you can retrieve some of the old settings.

And as for the file: being playable does not mean that it is not somehow corrupt, esp. as you already get an according message.  
Please see the tools linked in this thread and check it:

> [@How to check files for errors?](https://community.mp3tag.de/t/how-to-check-files-for-errors/44633):
>
> It’s required and often helps to reduce support cycles to check files for errors before filing a bug report. Symptoms of erroneous files are often missing or wrong bitrate or length audible blips or skips tags seem to be sticky and cannot be removed There are some really good tools to check the files for errors, namely MP3 Diags — identifies many different issues in MP3 files Website: [http://mp3diags.sourceforge.net](http://mp3diags.sourceforge.net) Download: [MP3 Diags - Getting MP3 Diags](http://mp3diags.sourceforge.net/010_getting_the_program.html#binWindows) If the font size in MP3 Diags is …

---

<div class="post-metadata">

### Author: ![davialves](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/d/c68b51/32.png) [@davialves](https://community.mp3tag.de/u/davialves)
#### Post date: [April 15, 2020, 5:30pm UTC](https://community.mp3tag.de/t/self-deleted-tag-and-mapping-panel/48565/5 "2020-04-15T17:30:13Z")

</div>

The installation location (ProgramFilesx86) and the location of the .ini file of tags (AppData / Roaming) are the same, the file is modified.

As for the corruption of the music files I will check later.

---

<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:28pm UTC](https://community.mp3tag.de/t/self-deleted-tag-and-mapping-panel/48565/6 "2026-02-09T12:28:31Z")

</div>


