Max Dupilka

For sure. Reliving my old DOS days :)

Possibly you could add something like that to your script with finding reg.exe, just in case.

Thank you. This is really poor show by Microsoft, but I have come to expect things like that from them.

PROBLEM SOLVED! The script uses "reg query" to find the path to the Kits folder. This is part of "reg.exe" which is in the System32 folder. Microsoft, in their infinite wisdom, does not check if the the System32 path is included in the environment path. When I added it to my environment path all worked as it was supposed to. And OWLNext worked fine. Maybe you could mention that the "C:\Windows\System32" path needs to be in the environment so that reg.exe can be found.

When running with non-administrator these are the includes INCLUDE=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\ATLMFC\include;C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Auxiliary\VS\include When running as administrator they are: INCLUDE=C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.39.33519\include;C:\Program Files\Microsoft Visual...

Thanks for the replies. I install Visual Studio just using its default directories. The installer is in "Program Files (x86)" and the Community version is in "Program Files", Before you do any changing to OWLMaker, I would like to find out why I need the elevated privileges. This never seemed to happed before VS 2022

What I have found out is if I run the Developer Command Prompts for Visual Studio via the Administrator then all the environment paths are there and the OWLNext compile works through that command line. If I run OWLMaker as the administrator the necessary environment paths are still not found by "VcVarsAll.bat". It seems it is running as a non-administrator. when using OWLMaker.

They are already selected. Thanks for all your help. I know what the problem is now. Somehow Visual Studio is not seeing the Windows Kit. I will work on that. I will uninstall all references to Visual Studio and the Kit and try to start over.