Should use ${SystemRoot} ${ProgramFiles} ${SystemDrive} instead of "C:\\Windows" "C:\\Program Files" "C:".
See original GitHub issueNot every Windows PC uses C
as system drive letter. Please replace C:\\Windows
C:\\Program Files
C:\\Program Files (x86)
C:
to ${SystemRoot}
${ProgramFiles}
${ProgramFiles(x86)}
${SystemDrive}
, thanks.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:11 (10 by maintainers)
Top Results From Across the Web
when the boot drive is different from system drive, what can be ...
C : drive functions as system drive and have the users folders there as well as virtualization folders for VM's leaving only 76GB...
Read more >Why are there separate Program Files and Program Files (x86 ...
On Windows editions that support x86 emulation, there are two directories for program files. The C:\Program Files directory is for programs ...
Read more >Recognized Environment Variables - Windows - Microsoft Learn
Learn how to use environment variables to identify folders that may be different on different computers.
Read more >How to use %ProgramFiles% in the Path environment variable?
I'm trying to add a folder to the system's Path environment variable. i want to add %ProgramFiles%\SysInternals to the existing path ...
Read more >Microsoft does not support changing the location of the ...
NoteThe default location of the Program Files folder is systemdrive\Program Files. For example, if Windows is installed on drive C, type C:\Program Files...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, we should fix this.
CMake Tools 1.7.0 was released today and it contains a fix for this issue. Upgrade the extension in VSCode and let us know if you encounter any other problems.