search

win32ss / supermium

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

Installer for 122.0.6261.152 (R6) isn't working (win7) #595

Open metapea opened 4 months ago

metapea commented 4 months ago

I been getting this error when initializing: 221 Also I've been getting a prompt to reinstall with recommended setting including previous versions when the installer worked. Here's a basic image of the error: 221

martrant commented 4 months ago

It's probably something to do with your particular system. I've just installed R6 (on top of R5), without any issues (Win7 Pro, 64bit, fully patched), with the presets shown in the image below. Notably, the previous installation of R5 did indeed issue a warning about "This program might not have installed correctly, etc.", which I ignored, as, subsequently, R5 worked absolutely fine. Installation of R6 atop of R5 did not produce this warning. I suppose you'd better fully uninstall it and install it afresh.

Capture

win32ss commented 4 months ago

Make sure that any Supermium executables are not running when the installer is running. Windows 7 file permissions appear to be "sticky" on my test setup with 2020-01 updates, where some files do not delete until the system is rebooted, even manually. So such a system may need to be rebooted before the installer can be used.

metapea commented 4 months ago

Make sure that any Supermium executables are not running when the installer is running. Windows 7 file permissions appear to be "sticky" on my test setup with 2020-01 updates, where some files do not delete until the system is rebooted, even manually. So such a system may need to be rebooted before the installer can be used.

A reboot did fix it, but i think it might've just been a hanged/frozen processes, so checking task manger and end any frozen processes should fix it. Maybe add a check to the installer and instead of "error:win32", and add "supermium is still running", but i'm still not sure if was that or a reboot was actually was required. If a reboot was required then just add a warring in the GitHub release page

Notably, the previous installation of R5 did indeed issue a warning about "This program might not have installed correctly, etc.", which I ignored, as, subsequently, R5 worked absolutely fine.

I know. that's what i said. With R6 i got it once but afterwards it didn't appear again, even after the reboot. I'm unsure if R5 and the other previous version works the same way since i only install them 1-2 times.

krystian3w commented 4 months ago

Maybe possible use logout instead, if browser can't "still" run at login screen without hacks:

REG ADD "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\sethc.exe" /v Debugger /t REG_SZ /d "C:\windows\system32\cmd.exe"