https://bugs.winehq.org/show_bug.cgi?id=51063
--- Comment #3 from Sveinar Søpler cybermax@dexter.no --- (In reply to Robbert van der Helm from comment #2)
@Sveinar Søpler
Check the commit I linked for the version changes I'm talking about. These two version strings are independent of the Windows version you select in winecfg. While I was bisecting this, the Windows version option in winecfg was kept at Windows 7 the entire time.
That is why i used the phrase:
Logic being that if the program assumes the OS is win 7, it expects the dll version to be that of win 7...
And updating the .dll version to that of Win10 without actually setting the prefix to win10 COULD cause issues if a program checks for both. I have no idea what checks is done by this particular program, but i know of a few instances where checks is being done for OS, and if OS = win10, it checks the .dll version to determine what build you are using, so spesific settings can be used.
If you have tried, and it makes no difference, i am sorry for the suggestion :)