Skip to main content ↑ ↓

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Cannot update fromFB 2.24.4 32bit to FB 2.24.5 32 bit (Read 427 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Cannot update fromFB 2.24.4 32bit to FB 2.24.5 32 bit

Got a error message: ''the install directory'C:\program files (x86)\foobar2000' contains configuration data, but Foobar2000 is not using portable mode. This is no longer supported since Fobar2000v2.0''

I do have a permanent installation on my hard drive.
thanks.

Re: Cannot update fromFB 2.24.4 32bit to FB 2.24.5 32 bit

Reply #1 –
Your installation directory contains foobar2000 profile, which means it's either a portable install or it has been a portable install that was later turned into a hybrid portable/standard version.
As the error message states, foobar2000 v2.0 introduced a policy change and such custom hybrid setup is no longer allowed. Reason for that change is most likely to ease maintenance. That setup was never officially supported and alpha development stage showed that to be bugged.
Best option is to move the profile directory to where it belongs. Depending on how old the install is your profile dir is called either "configuration" or "profile". Move the profile directory to %appdata% and rename it to "foobar2000-v2".

Re: Cannot update fromFB 2.24.4 32bit to FB 2.24.5 32 bit

Reply #2 –
Another problem, while updating and reach to the end, always I have to kill the fb2k process that the installer started, and then (after killed) it finished as nothing happened
 

Re: Cannot update fromFB 2.24.4 32bit to FB 2.24.5 32 bit

Reply #3 –
Thank you for the help.

Re: Cannot update fromFB 2.24.4 32bit to FB 2.24.5 32 bit

Reply #4 –
If foobar2000 process doesn't close it's a quite clear sign there's a buggy component involved. You should be able to find the name of the culprit by following Appendix A of support forum rules till point 3. You should see the name of the problematic component in the Threads list directly.