Skip to main content
Topic: Error reading configuration/theme file (Read 20915 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Error reading configuration/theme file

I tried to see if anyone else had posted about this issue with foobar2000, but I couldn't find anything, so here goes.
I experience this very often with foobar and it's quite upsetting. Sometimes, I shut down the pc before closing foobar, and next time I try to open it I get this issue (not sure how connected the error and shutting down the pc before closing foobar are, but that's how it seems to me):

"Error reading theme file (Unsupported format or corrupted file).
Continue?"

After I click "OK", I get this:

"Error reading configuration file (Unsupported format or corrupted file (header mismatch)).
Continue?"

I hit "OK" again, and then foobar starts, but without having the theme I had chosen for it, so I have to set up the theme all over again. I also have to fill up the media library too, because now it's empty. I would really love it if foobar stopped having this behaviour, even if I shut down my pc that way.

How can I get rid of this issue, please? Thanks.

Error reading configuration/theme file

Reply #1
I second that: happened to me six or seven times in the last few weeks. Very annoying... Even more so as I did not find a component that is able to do a quick backup of the %appdata%\foobar folder. For a second I thought that 'foo_jesus' would do this, but apparently not...

So: Is there any way to avoid this reset, or a way to automatically back up the config to prepare against the reset? (without third-party software, that is)?

Thanks in advance, pano

Error reading configuration/theme file

Reply #2
Happens to me also.

Error reading configuration/theme file

Reply #3
Seems related to something happened to me, try 2E7AH's solution.

Error reading configuration/theme file

Reply #4
This thread needs more component lists.

Error reading configuration/theme file

Reply #5
So: Is there any way to avoid this reset, or a way to automatically back up the config to prepare against the reset? (without third-party software, that is)?


why not take some responsibility for the files that you value? treat your foobar config like any other files you spend time on and back them up yourself. every time i make major changes to my foobar config, the first thing i do is close foobar and backup my files to an alternate location. does everybody really need components to do everything for them? :/


Error reading configuration/theme file

Reply #6
@marc2003: Because having a component that backs everything up for you automagically is far more convenient...

Error reading configuration/theme file

Reply #7
surely backing up your files manually is more convenient than configuring foobar from scratch every time your files get corrupted? 

also, you could create a batch file to do the backup and tie it to a button in foobar using foo_run. what could be more convenient than that?

Error reading configuration/theme file

Reply #8
I'll say it again: without component lists showing what components you have installed, this thread is going absolutely nowhere. This behaviour is not known to occur in stable configurations. I suspect that you are using some questionable component and that is why you're having dataloss issues. Prove me wrong! I'd love it!

Error reading configuration/theme file

Reply #9
You can see if you have any troubling components by using the built-in troubleshooter: Help > Online Troubleshooter.

Or use this page and paste the component list.
http://help.foobar2000.org/troubleshooter/
Windows 10 Pro x64 // foobar2000 1.3.10

Error reading configuration/theme file

Reply #10
There's plenty of automatic backup software out there, some of it free. A web search should turn up something suitable for this.

As well, you can, as Canar seems to be suggesting, take steps to improve the stability of your foobar2000 installation or your computer system. (The last time I had this issue on a regular basis, my "component list" included a computer with a dying motherboard.) Backups are still a good idea for anything you care about preserving, of course.

 
SimplePortal 1.0.0 RC1 © 2008-2019