Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
metapea opened this issue May 20, 2024 · 4 comments
Open

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

metapea opened this issue May 20, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@metapea
Copy link

metapea commented May 20, 2024

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

@metapea metapea added the bug Something isn't working label May 20, 2024
@martrant
Copy link

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
Copy link
Owner

win32ss commented May 20, 2024

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
Copy link
Author

metapea commented May 20, 2024

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
Copy link

krystian3w commented May 22, 2024

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"

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants