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: Foobar2k v1.1.1 installer (Read 3639 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Foobar2k v1.1.1 installer

Hello, fb2k user for years, recently decided to upgrade from 1.0.0 to 1.1.1 on my Win7 Ultimate x64 system

The installer went along fine with no problems up until it decided to update the registry settings. At this point the installer just sits there, it doesn't freeze, or become unresponsive, it just keeps on 'working'  without actually doing anything.

After leaving it running for 12+ hours (overnight), I decided to close it via taskman.exe; Now my foobar won't open at all, and if I re-run the installer it does the same thing. Also, I cannot uninstall it because the installer claims that it cannot remove the folder/files at all (instantly fails)


If I've missed any info, please do tell me, I hope I have included enough here.
I'd very much like to get my foobar going again, VLC just doesn't work so great as a replacement.



Thanks, Thefinaldegree

Foobar2k v1.1.1 installer

Reply #1
The updating the registry step calls the installed foobar2000 itself to load components and update registry information such as file type association listings and registering the shell extension. It may help if you can log what the foobar2000.exe process is doing with Process Monitor.

Foobar2k v1.1.1 installer

Reply #2
It may help if you can log what the foobar2000.exe process is doing with Process Monitor.


I'm not sure how to do that, but there was a  power failure which caused my computer to reboot. Foobar2000 seems to be working fine after the forced reboot.

Foobar2k v1.1.1 installer

Reply #3
Yeah, well, you could have located and killed the existing foobar2000.exe process and it would have started normally instead of reporting that there's already an instance running.

Foobar2k v1.1.1 installer

Reply #4
Would be great if you could run the installer again and follow debugging instructions from Appendix B.