Closed syntroniks closed 4 years ago
I had a "Command Processor" conda hook that was running a conda bat file that didn't exist.
This would result in each cmd.exe
call to return The system cannot find the path specified.
and have a non-zero exit code I imagine.
By removing the value for HKCU\Software\Microsoft\Command Processor\AutoRun
, I got cmd.exe to be happy again, and all is well.
In fact, by hacking in a VS2019 kit, cmake itself would fail to configure because it was leveraging cmd.exe /C ...
I'm glad you were able to solve your issue. We probably wouldn't have guessed to look in the registry! 😉
Brief Issue Summary
Kit scanning is unable to run vswhere.exe
CMake Tools Log
Platform and Versions
Other Notes/Information
I have vswhere
I also have a copy from chocolatey (produces the same output) which is earlier in my PATH
I am willing to help debug. You'll notice my VS installs are on 2 different drives. My vscode install is per-user (my user)
I've ran as administrator, I've also executed the bundled vswhere and it seems fine.