Can't install v33.4.1 on Win 10 Build 17763.6414

[Nuck-TH]

whereas if the check fails in the installer it would just quit - no file extraction needed.

which blatantly won't work on half the systems. even if not half, check itself not working defeats its purpose.

another item to be maintained

program written using WinAPI alone or some other system/minimal functions won't need any significant maintenance.

[moonbat]

which blatantly won't work on half the systems. even if not half, check itself not working defeats its purpose.

True that since that's the source of the complication we have here. I was responding to how this seems like an inefficient hack - extracting the files, then running the program, then deleting the files if the check fails. But if the installer can't check on its own properly then perhaps this is the only way to do it.

[RealityRipple]

idk what it'd entail, but could this NSIS plugin be implemented?

[Moonchild]

idk what it'd entail, but could this NSIS plugin be implemented?

It'd entail incorporating an over a decade old binary component that is built against and including an ancient MSVC runtime, introducing almost certainly serious sec issues.
It's just not been maintained.
For this to be viable, someone who is not me would first have to uplift the plugin to current MSVC and language standards and modern CPUs, release it, and only then we could consider it.

which blatantly won't work on half the systems.

But it will work on the other half, which is better than having nothing at all, was my reasoning. Especially if that "half", more likely 80%+, would benefit from being informed during installation instead of facing an error when trying to start it.

check itself not working defeats its purpose.

The check in its currently released form only "doesn't work" as intended if people are running Windows 10 Enterprise LTSC or IoT 1809, which is an very, very small fraction of the user base. And I'm working on improving that. Still waiting for feedback on it from people on affected versions and/or hardware.

[hermit]

Hmm.. :/ okay. please let me know if this one works any better: https://ftp.palemoon.org/publicbeta/palemoon-33.4.1-addtest-alt.win64.installer.exe

Does not work @
Windows 10 Version 1511 (Build 10586.x)
Windows 10 Version 1607 (Build 14393.x)
Windows 10 Version 1709 (Build 16299.x)
Windows 10 Version 1809 (Build 17763.x)
Windows 10 Version 1909 (Build 18363.x)
😐

Works @
Windows 10 Version 2004 (Build 19041.x)
😉

[Moonchild]

Does not work @
Windows 10 Version 1511 (Build 10586.x)
Windows 10 Version 1607 (Build 14393.x)
Windows 10 Version 1709 (Build 16299.x)
Windows 10 Version 1809 (Build 17763.x)
Windows 10 Version 1909 (Build 18363.x)
😐

Works @
Windows 10 Version 2004 (Build 19041.x)
😉

That doesn't make any sense. 1511-1909 are explicitly checked for and will skip the AVX check in that case, so it should pass and allow installation.
I've gone the route of checking HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ReleaseId which should have the corresponding version number.

EDIT: Well I guess I must be doing something wrong in the NSIS scripting language reading the registry. I'll try to debug it, see if I can find out why my code isn't working.

EDIT2: Yeah dumb mistake on my part. I'll have a new test version in a few hours.

[hermit]

I've gone the route of checking HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ReleaseId which should have the corresponding version number.

EDIT2: ... I'll have a new test version in a few hours.

"ReleaseId" may not be the best choice!? 🤔

Window 10 Version 2004 (Build 19041.x):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"CurrentBuild"="19041"
"CurrentBuildNumber"="19041"
"ReleaseId"="2004"

Window 10 Version 20H2 (Build 19042.x):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"CurrentBuild"="19042"
"CurrentBuildNumber"="19042"
"ReleaseId"="2009"

Window 10 Version 2 1H1 (Build 19043.x):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"CurrentBuild"="19043"
"CurrentBuildNumber"="19043"
"ReleaseId"="2009"

Window 10 Version 21H2 (Build 19044.x):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"CurrentBuild"="19044"
"CurrentBuildNumber"="19044"
"ReleaseId"="2009"

Window 10 Version 22H2 (Build 19045.x):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"CurrentBuild"="19045"
"CurrentBuildNumber"="19045"
"ReleaseId"="2009"


Windows 11 Version 21H2 (Build 22000.x):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"CurrentBuild"="22000"
"CurrentBuildNumber"="22000"
"DisplayVersion"="21H2"
"ReleaseId"="2009"

Windows 11 Version 24H2 (Build 26100.x):
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion]
"CurrentBuild"="26100"
"CurrentBuildNumber"="26100"
"DisplayVersion"="24H2"
"ReleaseId"="2009"

🙄

[Moonchild]

It is the best choice. As said it isn't straightforward, because later versions no longer use it, so it may or may not be present. 2009 there just means it wasn't updated past build 2009 when they switched to DisplayVersion. I already accounted for that.

[hermit]

It is the best choice. As said it isn't straightforward, because later versions no longer use it, so it may or may not be present. 2009 there just means it wasn't updated past build 2009 when they switched to DisplayVersion. I already accounted for that.

Build numbers are looking interesting / unique!
Even cumulative OS updates are bond to build numbers… 🤔

[hermit]

idk what it'd entail, but could this NSIS plugin be implemented?

That looks great! Indeed!

[Moonchild]

That looks great! Indeed!

It does and would avoid having to check windows versions. Unfortunately as mentioned not maintained and unusable in its current state.

---

This version should work: https://ftp.palemoon.org/publicbeta/palemoon-33.4.1-addtest-alt2.win64.installer.exe

[hermit]

This version should work: https://ftp.palemoon.org/publicbeta/palemoon-33.4.1-addtest-alt2.win64.installer.exe

First and foremost:
It installs and runs perfectly @ Windows 10 Version 1809 (Build 17763.6414). Great!
Many thanks. 😊

Does not work @:
Windows 10 Version 1507 (Build 10240.x) supported until 2025-Oct-14
😄 🥳

Successfully tested @:
Windows 10 Version 1511 (Build 10586.x)
Windows 10 Version 1607 (Build 14393.x) supported until 2026-Oct-13
Windows 10 Version 1709 (Build 16299.x)
Windows 10 Version 1809 (Build 17763.x) supported until 2029-Jan 09
Windows 10 Version 1909 (Build 18363.x)