User setup for Windows

Announced last release, the user setup package for Windows is now available on stable. Installing the user setup does not require Administrator privileges as the location will be under your user Local AppData (LOCALAPPDATA) folder. User setup also provides a smoother background update experience.

Download User Setup

If you are a current user of the system-wide Windows setup, you will be prompted to install user setup, which we recommend using from now on. Don't worry, all your settings and extensions will be kept during the transition. During installation, you will also be prompted to uninstall the system-wide setup.

Reference: https://code.visualstudio.com/updates/v1_26#_user-setup-for-windows

Answer from Surenthar Pitchai on Stack Overflow
🌐
Reddit
reddit.com › r/vscode › should i use the user or system installer?
r/vscode on Reddit: Should I use the User or System Installer?
December 13, 2019 - vscode devs recommends user install as it does not need admin proviliges so it is easier to maintain/update in the backgroud. Just install user version, its fine. I personally installed the system version for no reason other than that I like ...
Top answer
1 of 5
95

User setup for Windows

Announced last release, the user setup package for Windows is now available on stable. Installing the user setup does not require Administrator privileges as the location will be under your user Local AppData (LOCALAPPDATA) folder. User setup also provides a smoother background update experience.

Download User Setup

If you are a current user of the system-wide Windows setup, you will be prompted to install user setup, which we recommend using from now on. Don't worry, all your settings and extensions will be kept during the transition. During installation, you will also be prompted to uninstall the system-wide setup.

Reference: https://code.visualstudio.com/updates/v1_26#_user-setup-for-windows

2 of 5
59

I installed the user version side-by-side with the system version with no problems. The basic differences between the two is that the system version installs on the file system like every other app. The user install is basically a click-once (or web installer) version that installs in the User folder of the machine.

The settings made to VS Code in the system version save for Everybody on the computer and the user version the settings are only for the user. I find that the behavior of the user version is a bit annoying for me because I have reasons to want to open multiple copies of VS Code at the same time and the user version only allows one instance. Otherwise, there's not really anything different between the two as far as I can tell.

🌐
Quora
quora.com › What-is-the-difference-between-a-user-installer-and-a-system-installer
What is the difference between a user installer and a system installer? - Quora
Answer (1 of 2): User installer installs in your User folder and does not need Administrator privileges. System installer installs for all users on the system and needs Administrator privileges. Sagar Suba
🌐
Devgex
devgex.com › en › article › 00031713
Comprehensive Analysis of User vs System Installer in Visual Studio Code - DevGex
December 1, 2025 - The System Installer better fits standardized deployments in enterprise environments where IT departments need centralized software installation and update management, or when consistent development environment configurations must be maintained ...
🌐
Visual Studio Code
code.visualstudio.com › docs › setup › windows
Installing Visual Studio Code on Windows
1 week ago - The User setup is the recommended installation for most people because it does not require administrator permissions and supports smoother background updates. VS Code provides both Windows user-level and system-level setups.
🌐
Reddit
reddit.com › r/vscode › ...but what's the actual point of user install instead of system-wide install?
r/vscode on Reddit: ...but what's the actual point of user install instead of system-wide install?
January 22, 2021 -

I have all my software that I install installed system-wide under "Program Files", so I don't get why one program should be an exception. Why should I want user-install? Is there really no way to force system-wide install these days?

Note that I'm not looking for descriptions of differences per se between system-wide and user install. I'm looking for what the actual benefits of user install are, and what the actual disadvantages/problems with system-wide install are.

So far I'm aware of one disadvantage of user install, and that's the fact that the start menu search can't find vscode no matter what, because it's automatically installed to a location that the start menu search ignores.

Top answer
1 of 2
14

Basically a user install doesn't require admin rights. This means if you want to use VSCode on your work computer you don't need to get IT to install it.

It should still show up in the start menu. Assuming you selected the option in the installer it should have a shortcut somewhere in

%appdata%\Microsoft\Windows\Start Menu\Programs`

Finally Microsoft does provide a system install version that sounds like what you are looking for. It's located on the download page: https://code.visualstudio.com/Download

2 of 2
2

you should default to user install and only use system install when necessary. principle of least power and whatnot.

i somehow always irreparably fuck up my python install on windows because of conflicts between system versions, local versions, system pip, local pip, it’s a fuckin mess. any seasoned python dev will tell you the solution is to use one version of python and only install packages locally, preferably through aggressive use of virtual environments.

the main benefit of user install is isolation and orthogonality. system programs are in program files, personal programs that you would want to keep with you across machines are to be installed locally.

this is less relevant these days now that people rarely share computers, but the idea is the same. i act as if there’s another user who uses my computer under a different account sometimes. some programs should be universal, like photo editing software, video players, etc., while it isn’t really important that everyone have access to my customized text editor or the 800 million fonts i download.

🌐
Profoundadvices
profoundadvices.com › which-is-better-user-installer-and-system-installer
Which is better user installer and system installer? – ProfoundAdvice
User installer installs in your User folder and does not need Administrator privileges. System installer installs for all users on the system and needs Administrator privileges. ... Is there a way to install it one time and it is installed for all users?
🌐
Quora
quora.com › Whats-the-difference-when-choosing-to-install-Visual-Source-Code-using-user-vs-system-install
What's the difference when choosing to install Visual Source Code using 'user' vs 'system' install? - Quora
Answer (1 of 4): Hi, I suppose you are talking about Visual Studio Code, but it doesn't matter much. I also assume you are talking about installing it under Windows ( which in this case is more relevant )… Thus, under Windows, doing a system (-wide ) installation means the installed applicatio...
Find elsewhere
🌐
Glarity
askai.glarity.app › search › What-is-the-difference-between-user-and-system-installers-of-Visual-Studio-Code-on-Windows
What is the difference between user and system installers of Visual Studio Code on Windows? - Ask and Answer - Glarity
2. **System Installer**: Requires ... the machine [1]. 3. User install is recommended for easier maintenance and updates, while system install provides access to all users but requires higher privileges [4]....
🌐
Flathub Documentation
docs.flathub.org › for users › user vs system install
User vs system install | Flathub Documentation
Flatpak applications can be installed either per-user or system-wide. The difference is that per-user installations are only available to the user that installed them, while system-wide installations are available to all users on the system.
🌐
Reddit
reddit.com › r/vscode › question about system installer vs user installer?
r/vscode on Reddit: Question about System Installer vs User Installer?
August 26, 2024 - I heard that the User Installer will install into the AppData and the System Installer will install into the Program Files is this true? I prefer my…
🌐
Prajwal Desai
forums.prajwaldesai.com › home › microsoft cloud › sccm
SOLVED - Difference between Install for system, install for user , deploy to user collection deploy to device collection | Forums on Intune, SCCM, and Windows 11
September 29, 2020 - Install for system if resource is device; otherwise, install for user: If you deploy the application to a device, the client installs it for all users. If you deploy the application to a user, the client only installs it for that user.
🌐
Reddit
reddit.com › r/intune › system vs user install behavior on new store apps?
r/Intune on Reddit: System vs User install behavior on new Store Apps?
May 17, 2023 -

Can anyone explain the difference between System and User install behavior for the new store apps in Intune? I’m hearing different answers from different sources. I know Microsoft got rid of online vs offline installers for store apps.

🌐
Reddit
reddit.com › r/vscode › system vs. user install
r/vscode on Reddit: System vs. User install
August 4, 2019 -

I just got a new SSD and so I decided to do a clean install of Windows.

When I went to install vscode, it was installing a "user" version, which is apparently not a new a behavior, but one I never encountered because I had not needed to do a clean install vscode in a long time, just the auto-updates.

So now I am not sure why it is preferable to install this "user" version to the user AppData folder rather than the "system" version to Program Files.

There is no NTFS file security on the user AppData folder. Any program running can modify those files without elevation, which is risky for executable code. Installing to Program Files gives an added layer of protection that the executable can't be hijacked without elevation.

What convenience does the "user" installation add that is worth giving up the extra security from the "system" version installing the executable in Program Files?

🌐
Radish Logic
radishlogic.com › home › installing visual studio code for all users in windows
Installing Visual Studio Code for All Users in Windows - Radish Logic
April 9, 2022 - Here is a screenshot of the two types of installer side-by-side. The filenames looks similar. The difference is the System Installer does not have the word User, while the User installer has.
🌐
Reddit
reddit.com › r/intune › microsoft store apps - user vs. system install behavior
r/Intune on Reddit: Microsoft Store Apps - User vs. System install behavior
February 12, 2025 -

I have a few questions regarding install behavior for Microsoft Store apps:

  1. What is generally recommended? When doing win32 apps, we do the default System install behavior, only on circumstances we do User type. I noticed when doing MS Store apps, its default is User install behavior. This made me think that User is recommended for MS Store apps.

  2. For apps built-in to Windows or apps that MS forced into Windows (like Copilot), are those apps installed as User or System? And how will I know on an actual machine? Get-AppxPackage does not seem to provide that answer.

  3. Would there be issues when there is discrepancy? Like deploying an app as System when the device has the same app installed as User (and vice versa).

  4. For User deployment, would there be challenges for updating MS Store apps in the future? Like if an outdated MS Store app installed for a user that is not actively logging on a multiple user device.

🌐
Andrew Taylor
andrewstaylor.com › 2022 › 11 › 22 › intune-comparing-system-vs-user-for-everything
Intune – Comparing System vs User for everything! – Andrew Taylor
November 22, 2022 - One other thing to note: If you are wrapping MSI into Win32, you might come across occasions where the MSI itself is hard-coded and forces the User Context. If you find one of these, you can either edit the MSI with something like Orca, or if you wrap it with an installation script (PowerShell or Batch, whatever you prefer) and it will unlock the option to choose. The other one which causes issues, PowerShell scripts, whether deployed through the Scripts blade, Proactive Remediations, or an Application Requirements script. When running any script in the System context, as with the applications, it runs in the SYSTEM user account.