You download a Windows app, double-click the installer, and boom—your screen dims, and that familiar pop-up asks if you want to let the app make changes to your device. But then you install a different app, and it flies right through without Windows even batting an eye.

I’ve run into both kinds of installers on the same laptop, sometimes within minutes of each other. Windows can be rather particular about what it allows, but the difference usually comes down to the permissions an installer requests and where it plans to put its files.

Windows doesn’t demand admin rights for every installation

It’s what the installer touches that counts

Windows uses a feature called User Account Control (UAC) to block apps from making major changes without your permission. It’s responsible for the familiar pop-up that darkens your screen and asks, “Do you want to allow this app to make changes to your device?” when a program requests administrator privileges.

Even if you’re logged in as an administrator, Windows usually runs programs with regular user permissions. When a program needs more power, Windows asks for your approval. If you’re using a standard account, you’ll generally need to enter an administrator’s credentials instead.

That said, installing software doesn’t always need admin rights. If an installer can do everything it needs with the permissions you already have, Windows has no reason to stop and ask.

Installers generally need administrator privileges when they’re designed to modify protected parts of Windows. This includes saving files to C:Program Files, installing drivers, setting up system services, or changing system-wide settings. Windows even maintains two separate Program Files folders for different application architectures, although both are protected locations. Because these actions can affect other users or the entire operating system, Windows controls them much more tightly.

How the installer is built matters too. Windows can check the permission level a program requests and uses installer-detection tools to spot setup programs that likely need admin approval.

An installer that starts with ordinary user permissions can’t simply promote itself to administrator halfway through. If it needs access to protected resources, it must request elevation through a separate process or risk having those operations fail.

Your user folder offers another way in

Some apps install without Windows throwing up a warning

Every Windows account comes with its own set of folders where applications can save files and settings without administrator permission. One common destination is %LOCALAPPDATA%Programs, which corresponds to C:UsersYourNameAppDataLocalPrograms. The larger AppData folder already stores plenty of application settings, temporary files, and other personal data.

Because you already own these folders, an installer can easily drop its program files right into them, create desktop shortcuts for you, and update your personal registry settings. All of this happens smoothly using standard permissions.

This setup is called a per-user installation. It just means the app is installed strictly for your specific Windows account, instead of being set up for every single person who logs into that computer.

VS Code lets you choose which route to take

When you download VS Code for Windows, you get two installer options, and each one needs different permissions.

Most people should go with the User Installer. It sets up VS Code for your account only and supports background updates without constantly asking for administrator approval. The System Installer makes the editor available to everyone on the computer, but installing it and applying in-product updates require admin rights. Both versions have the same editing features, so the choice comes down to who needs access and how you want updates handled.

Microsoft Store has its own installation machinery

Applications installed through the Microsoft Store can take another route

Older-style installers usually handle their own file copying and system changes. Apps packaged with Microsoft’s MSIX technology work differently because Windows itself handles the setup.

Windows can install and register these packages for individual users, and the app files are usually kept in a protected folder, C:Program FilesWindowsApps. Windows does the work that a regular app wouldn’t have permission to do on its own. That’s why an installation can finish without you having to approve an admin prompt.

There is a catch, though. The Microsoft Store also lists traditional EXE and MSI apps, and those can install in their own way. On top of that, some MSIX packages will still trigger a pop-up if they need to set up background services or change settings for the whole computer.

An installer that skips UAC hasn’t necessarily earned your trust

Malware can do plenty with ordinary permissions

It’s tempting to think that if an app doesn’t trigger a security prompt, it’s totally safe. Unfortunately, that’s just wishful thinking.

A malicious program running with your standard, everyday permissions can still do a ton of damage. It can read your personal documents, steal saved info from your active browser session, or lock up your files with ransomware. A hacker’s code doesn’t need to take over your entire operating system to ruin your day completely.

User Account Control (UAC) helps prevent unauthorized changes that require administrator privileges. It isn’t an antivirus scanner, and it can’t tell whether a program running with ordinary user permissions has malicious intentions.

That’s also why turning UAC settings down isn’t a smart way to decide whether software is safe. Windows already offers different notification levels, and turning the prompts off removes an important layer of protection.

I’ll take the occasional interruption

I’ve always found Windows’ permission prompts a little theatrical, especially when the whole desktop darkens for a routine installer. However, I prefer having that occasional interruption to handing every application the keys to the kingdom.

And when a program installs without making a fuss, I’m happy to appreciate an installer that knows how to stay within its lane. Windows already has enough reasons to interrupt my work.