search

win32ss / supermium

Chromium fork for Windows XP/2003 and up
https://win32subsystem.live/supermium/
BSD 3-Clause "New" or "Revised" License
2.46k stars 85 forks source link

can't uninstall #1014

Open edgelord12 opened 1 week ago

edgelord12 commented 1 week ago

Describe the bug can't uninstall

To Reproduce Steps to reproduce the behavior: through the control panel

Expected behavior i expect the program to uninstall

Screenshots super

Desktop (please complete the following information):

Additional context was able to remove it safe mode but not normal

XakerTwo commented 1 week ago

wait a second, i have an idea why - cuz uninstaller lock directory, right?

Botardor commented 1 week ago

I also experience the the problem described herein on Windows XP Professional with Service Pack 3 and for the Supermium 126.0.6478.254 R4 32-bit installable version. In my case, Supermium program directory is "E:\Program Files\Supermium\".

win32ss commented 1 week ago

The uninstaller is usually located in the program directory, but when executed it copies itself to a temp directory, runs the copy with a command line parameter to indicate that it's in a different directory, and then starts the uninstallation process. By then, the original uninstaller in the program directory has quit, so under normal conditions, there should be no lock on the directory.

It's possible that something else may have locked the directory, which would explain why a reboot fixed it in that case.

Botardor commented 1 week ago

In my case, the problem has occurred since somewhere in the Supermium 126.x series (maybe Supermium 126.0.6478.249 (Release) ). I consistently can no longer get the unistaller to work. After answering the question about whether to keep the user data, that is when the error message appears. One is able to proceed past the initial question as to whether one wants to uninstall Supermium.

I am still able to manually remove Supermium (program, data directory, shortcuts, and registry entries). I believe that I had tried rebooting when first experiencing the problem (I do not remember if Safe Mode was tried, but it might have been), but the problem persisted. My impression is that the problem is with the uninstaller.

win32ss commented 1 week ago

Then it may be an issue of unreliability in SHFileOperation. Very sporadic but it happened with the installer on XP in a couple of cases.