# Cannot write configuration file - question

**URL:** <https://community.mp3tag.de/t/cannot-write-configuration-file-question/57298>\
**Category:** Support\
**Created:** [May 14, 2022, 5:46am UTC](https://community.mp3tag.de/t/cannot-write-configuration-file-question/57298 "2022-05-14T05:46:18Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![JohnE\_EC](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/j/ccd318/32.png) [@JohnE\_EC](https://community.mp3tag.de/u/JohnE_EC)\
**Post date:** [May 14, 2022, 5:46am UTC](https://community.mp3tag.de/t/cannot-write-configuration-file-question/57298/1 "2022-05-14T05:46:19Z")

</div>

When I open mp3tag as a user (not admin), and then close it, I get the message "Cannot write configuration file."

Since I am a user I would not want the conf file to be written. I would only want this when I open mp3tag as an admin.

When I open and close as admin, I don't get this message.

I have recently changed to a new PC with Win11, from an older PC with Win 10. I used the config file from the old PC and used it on the new Win11 one, and since then I get this message every time I use mp3tag.

Is there something I need to do to fix this, please.

---

<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:** [May 14, 2022, 5:51am UTC](https://community.mp3tag.de/t/cannot-write-configuration-file-question/57298/2 "2022-05-14T05:51:28Z")

</div>

> [@JohnE\_EC](#):
>
> I used the config file from the old PC

You have to check the owner of file - and modify the owner so that it works on your new pc.  
The idea to avoid MP3tag to write its own configuration file seems a little strange to me as this something program internal and you don't know what you mess up when you prohibit it by access rights.

---

<div class="post-metadata">

**Author:** ![Florian](https://community.mp3tag.de/user_avatar/community.mp3tag.de/florian/32/5759_2.png) [@Florian](https://community.mp3tag.de/u/Florian)\
**Post date:** [May 14, 2022, 5:56am UTC](https://community.mp3tag.de/t/cannot-write-configuration-file-question/57298/3 "2022-05-14T05:56:03Z")

</div>

You've probably restored the configuration to the program directory `C:\Program Files...` and not to the configuration directory `C:\Users\<username>\AppData\Roaming\Mp3tag` or installed Mp3tag as portable version.

So to verify this, you'd use **Help → About...** to check if Mp3tag is installed as Portable version. If so, remove the file `mp3tag.cfg` from the program folder. You can keep a copy elsewhere for backup purposes or restore your previous backup to the configuration directory.

> **[Download and Installation – Mp3tag Documentation](https://docs.mp3tag.de/getting-started/installation/#installation)**
>
> Details on where to download Mp3tag, Mp3tag's different installation modes, and system requirements for the usage of Mp3tag. Mp3tag is the universal Tag Editor.

---

<div class="post-metadata">

**Author:** ![JohnE\_EC](https://community.mp3tag.de/letter_avatar_proxy/v4/letter/j/ccd318/32.png) [@JohnE\_EC](https://community.mp3tag.de/u/JohnE_EC)\
**Post date:** [May 14, 2022, 9:09pm UTC](https://community.mp3tag.de/t/cannot-write-configuration-file-question/57298/4 "2022-05-14T21:09:46Z")

</div>

Hi Florian,

Thank you very much for your prompt reply.

As you suspected I had installed this as a Portable version. Not sure why I did that.

Anyway, I moved the mp3tag.cfg from the program folder to Roaming/Mp3tag and I no longer get this message.

Thank you for advising me how to fix this. Really appreciate it.

---

<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:** [June 13, 2022, 9:09pm UTC](https://community.mp3tag.de/t/cannot-write-configuration-file-question/57298/5 "2022-06-13T21:09:51Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
