Repository navigation
cppbuild task uses stale cached VS Developer Environment after upgrading to a newer Visual Studio installation #14800
Description
Environment
- OS and Version: Windows 11 24H2
- VS Code Version: 1.126.0 (User setup)
- C/C++ Extension Version: 1.34.4
- If using SSH remote, specify OS of remote machine: Running locally
Bug Summary and Steps to Reproduce
Bug Summary:
After upgrading Visual Studio Build tools from 2022 to 2026, IntellSense correctly reports the latest path, while the 'cppbuild' task in .vscode/tasks.json still uses the cached environment, resulting C1083 error: include path cannot be found.
Initially, I speculated that it's a issue in Build tools, but I tried repairing and reinstalling, none of them worked. The enviroment variables in Code.exe seems consistent with vcvarsall.bat, and directly building in command line worked as well.
This suggests the problem must be within the VSCode itself. Eventually I tried "Set VS Developer Environment" (#4742, added in 1.29.0), which fixed the issue.
Seems it caches the detected developer environment somewhere, and this cache is not invalidated/refreshed when the underlying VS installation changes.
Steps to reproduce:
- Install VS Build tools 2022
- Building any C++ project using cl.exe inside VSCode
- Remove VS Build tools 2022, then update to 2026
- See error
Expected behavior:
VSCode starting from vcvarsall.bat should build the project successfully.
Configuration and Logs
{
"configurations": [
{
"name": "Win32",
"includePath": [
"${workspaceFolder}/**"
],
"defines": [
"_DEBUG",
"UNICODE",
"_UNICODE"
],
"windowsSdkVersion": "10.0.26100.0",
"compilerPath": "cl.exe",
"cStandard": "c17",
"intelliSenseMode": "windows-msvc-x64"
}
],
"version": 4
}
Current database path: %userprofile%\AppData\Local\Microsoft\vscode-cpptools\5a1572067cb7701b835e17d775b99ce1\.BROWSE.VC.DB
Translation Unit Mappings:
[ <PROJECT_DIR>\<file>.cpp - source TU]:
Translation Unit Configurations:
[ <PROJECT_DIR>\<file>.cpp ]
Process ID: 23980
Memory Usage: 194 MB
Compiler Path: C:\Program Files (x86)\Microsoft Visual Studio\18\BuildTools\VC\Tools\MSVC\14.51.36231\bin\Hostx64\x64\cl.exe
Language: C++
Include Paths:
include: C:\Program Files (x86)\Microsoft Visual Studio\18\BuildTools\VC\Tools\MSVC\14.51.36231\include
include: C:\Program Files (x86)\Microsoft Visual Studio\18\BuildTools\VC\Auxiliary\VS\include
include: C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\ucrt
include: C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\um
include: C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\shared
include: C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\winrt
include: C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\cppwinrt
system include: C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\um
system include: C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\ucrt
system include: C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\shared
system include: C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\winrt
system include: C:\Program Files (x86)\Windows Kits\10\Include\10.0.26100.0\cppwinrt
include (recursive): <PROJECT_DIR>
Defines:
_DEBUG
UNICODE
_UNICODE
Standard Version: ms_c++20
IntelliSense Mode: windows-msvc-x64
Other Flags:
--using_directory
C:\Program Files (x86)\Microsoft Visual Studio\18\BuildTools\VC\Tools\MSVC\14.51.36231\lib\x64
--using_directory
C:\Program Files (x86)\Microsoft Visual Studio\18\BuildTools\VC\Tools\MSVC\14.51.36231\lib\x86\store\references
--using_directory
C:\Program Files (x86)\Windows Kits\10\UnionMetadata\10.0.26100.0
--using_directory
C:\Program Files (x86)\Windows Kits\10\References\10.0.26100.0
--using_directory
C:\Windows\Microsoft.NET\Framework64\v4.0.30319
Total Memory Usage: 194 MBOther Extensions
No response
Additional context
Related issues
- VS developer environment not found after following tutorial steps; blocked from building #14352 and Problem when compiling with 1.29.2 #14089 report a similar-sounding "developer environment" failure, but those describe the feature never successfully applying in the first place.
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
sean-mcmanus commentedon Sep 29, 2026
Chao-Freeman Are you re-using the same terminal? Is this issue fixed after you reload your terminal? The terminal inherits the environment variables and requires a reload afterwards.
Chao-Freeman commentedon Sep 29, 2026
No, the issue persists after reloading the terminal. I tried starting VSCode from Native Command Prompt, but it won't build either. However, the integrated terminal contains the correct include path inherited from Native Command Prompt, as follows: