I'm glad that you figured it out and thanks for sharing the solution.

That the old 10.0.10240.0 doesn't work isn't that surprising, this was back in the day with VS2015 and then perhaps some of the libraries came with the compiler.

I'm still perplexed by the fact that it doesn't work out of the box for you, if you don't specify -winsdk VsDevCmd.bat is supposed to select the newest as far as I can tell and for you that would be 10.0.22000.0 and that one certainly works for me. According to posts at the Visual Studio community it's supposed to read that information from the registry: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Microsoft SDKs\Windows\v10.0 You could take a look there and see which version it points to.

Otto

After a week spent on this I could manage to solve the problem. Actually, the problem was with Visual Studio 2019 installation. For some strange reason, the command VsDevCmd messes with all the needed environmental variables to do a proper compilation. It is something related with having more than one version of Windows SDK in the computer. It shouldn't be a problem as SM "asked" VS2019 the proper setup to compile its files. The toolkit with all needed headers and libraries is the 10.0.19041.0 version. You can find the toolkits in (if you haven't changed the standard path):

C:\Program Files (x86)\Windows Kits\10\Include

There is a folder for each version:

Solution:

1. Select custom setup for the compiler;
2. Add -winsdk=10.0.19041.0 command to the line "Visual C++ setup script arguments";
3. Click Verify Compiler, it is expected to succeed;
4. Click OK.

My compiler options screen after setup:

Hope this helps anyone with the same problem!

Relevant link: https://renenyffenegger.ch/notes/Windows/dirs/Program-Files-x86/Microsoft-Visual-Studio/version/edition/Common7/Tools/VsDevCmd_bat