https://bugs.winehq.org/show_bug.cgi?id=48959
Zebediah Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com Keywords| |download, regression URL| |https://www.scuffhamamps.co | |m/download/s-gear-v2 Status|UNCONFIRMED |NEW Component|advapi32 |msi Regression SHA1| |6719bf2e037b95b8338fae9e660 | |c43e8fadafc7a Ever confirmed|0 |1
--- Comment #3 from Zebediah Figura z.figura12@gmail.com --- (In reply to Stan Janssen from comment #2)
I'm not sure whether to relate this to the advapi32.dll component or to the msi component.
Better to set it to "-unknown", unless you've debugged it and can tell.
Anyway, the installer seems to demand (via the LaunchCondition table) that the VersionNT64 property be set to 1000 (or at least, not 600, 601, 602, or 603). The main executable ships with a manifest recognizing Windows 10, but the process that fails is msiexec.exe, which has no such manifest.
Problem is: https://testbot.winehq.org/JobDetails.pl?Key=69985 implies that just adding a manifest to msiexec.exe, or using RtlGetVersion() to set VersionNT64, is the wrong thing to do. I haven't yet figured out how to get VersionNT64 to report anything higher than 603.