Visual Studio Code

For managed Visual Studio Code deployments, use the official Windows setup guidance and pass installer switches directly to the system installer. A common silent system-install pattern is VSCodeSetup-x64.exe /silent /mergetasks='!runcode,addcontextmenufiles,addcontextmenufolders,associatewithfiles,addtopath' to suppress launching Code after setup while still enabling Explorer context-menu entries, file associations, and PATH integration. Microsoft documents the Windows installer and command-line options at https://code.visualstudio.com/docs/setup/windows.

For portable or no-registry deployments, use the official stable Windows x64 archive URL https://update.code.visualstudio.com/latest/win32-x64-archive/stable, extract it to the target folder, and create a data subfolder next to Code.exe before first launch to keep user data/extensions with that portable installation.

Close running Code.exe / Visual Studio Code sessions before updating managed system or user installers. Open VS Code windows can make updates fail with access-denied style results such as exit code 5 or 0x80070005, so Intune/ConfigMgr packages should use conflicting-process handling or a pre-update close/notify step before launching the installer.