trio.so
How-Tos

How to Stop Employees From Installing Software on Windows

Seven ways to stop employees installing software on Windows: standard users, AppLocker, App Control for Business, Store policy and MDM allow lists.

Mountain landscape representing leadership perspective and vision
Written by
Atena Ladchartabi

Content writer, trio.so

Published on
Modified on

To stop employees from installing software on Windows, first make everyday accounts standard users instead of local administrators, which blocks most machine-wide installs. Then close the gaps that standard accounts leave open: apps such as Spotify, Zoom and Chrome can install into the user's own profile without admin rights, so you also need execution control (AppLocker or App Control for Business), Windows Installer and Store restrictions, and, across a fleet, a device management (MDM) tool that applies the same rules to every PC.

If unapproved apps keep appearing on company PCs even after you removed admin rights, this guide covers seven methods from the simplest to the strongest, what each one catches and misses, and how to choose the right combination for your setup.

TL;DR

  • Removing local admin is the single most effective step. Do it first.
  • Windows Installer restrictions don't stop apps that install into the user profile (Spotify, Zoom, Chrome). AppLocker or App Control for Business closes that gap.
  • Since update KB5024351 (2023), AppLocker can be enforced on all editions of Windows 10 version 2004 and later and Windows 11, including Pro.
  • Software Restriction Policies (SRP) are deprecated. Reports show them failing silently on Windows 11, so use AppLocker or App Control for Business instead.
  • Blocking the Microsoft Store doesn't block winget, the command-line package manager. Turn it off with Microsoft's App Installer policy or block it with app control.
  • Test AppLocker and App Control rules in audit mode first. Rules without allowances for built-in packaged apps can break the Start menu and Settings on Windows 11.
  • An MDM tool gives you central enforcement, software allow and block lists and an app catalog, which matters once you manage more than a handful of PCs.

Why Standard Users Can Still Install Software (And What You're Actually Controlling)

If you already understand the per-user install loophole and have removed local admin from all users, skip ahead to the methods section.

Windows has two installation models. Machine-wide installs write to C:\Program Files and the HKLM registry hive. They need elevation, so a standard user account can't complete them. This is the model most people picture when they think about blocking software installs, and it is only half the picture.

Per-user installs write to %LocalAppData% or %AppData% (inside C:\Users\<name>\AppData). They don't need a UAC prompt, because Windows doesn't treat them as system-level installs. If software only affects the user's own profile, standard account rights are enough to install it.

Apps like Spotify, Zoom and Chrome offer per-user installers. That is why admins keep finding them on machines where users have no local admin: the software installs to the user profile, not the machine, and standard account restrictions don't touch it.

So you are really controlling two separate things: the act of installing, and the running of software that is already on the disk. They need different tools. Understand that distinction first, then choose the methods that cover both for your environment.

7 Methods to Stop Employees from Installing Software on Windows

Think of these as a layered stack, not a menu where you pick one. Each method covers a different part of the problem, and no single method catches everything. Start with the simplest and add layers based on your environment and risk.

Method 1: Remove Local Admin (Standard User Accounts)

This is the starting point for stopping machine-wide installs. Every other method below assumes you've done it.

What it does: prevents installs to Program Files and HKLM. What it doesn't do: stop per-user installs such as Spotify, Zoom and Chrome.

How to do it: in Computer Management, open Local Users and Groups and remove the user from the Administrators group. At scale, use Group Policy (Restricted Groups or Local Users and Groups preferences) or your MDM to enforce membership across all PCs.

  • Pros: free, immediate, no extra infrastructure
  • Cons: doesn't stop per-user installs into the user profile

Get leadership to agree before you remove local admin. It is the step most rollouts skip, and the one that causes the most reversals.

Method 2: Windows Installer GPO Restriction

Group Policy path: Computer Configuration > Administrative Templates > Windows Components > Windows Installer > Turn off Windows Installer.

Set it to "For non-managed applications only". This blocks user-started MSI installs while keeping software that IT deploys. Don't set it to "Always", which disables Windows Installer for every account, including the one you use to deploy software.

Also enable Prohibit User Installs in the same folder to block per-user MSI installations.

  • Pros: free, low maintenance
  • Cons: only covers MSI installers, not EXE installers or per-user apps packaged another way

If the policy applies but users can still install apps, check how those apps are packaged. The Windows Installer restriction only covers MSI installs.

Method 3: UAC Configuration

Group Policy path: Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options.

Set "User Account Control: Behavior of the elevation prompt for standard users" to Automatically deny elevation requests, and keep "Detect application installations and prompt for elevation" enabled. A standard user who starts an installer that needs admin rights is then refused without a password prompt they could try to talk a colleague through.

Registry equivalent: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System, value ConsentPromptBehaviorUser set to 0.

  • Pros: stops elevation attempts quietly, works with local policy on PCs outside a domain
  • Cons: does nothing for per-user installers that never ask for elevation

Method 4: Software Restriction Policies (SRP)

Group Policy path: Computer Configuration > Windows Settings > Security Settings > Software Restriction Policies.

SRP uses path or hash rules with the Disallowed security level to block executables. Microsoft lists SRP as deprecated, and admins have reported it silently doing nothing on Windows 11, with no error to warn you. If you still have SRP rules on Windows 10 machines, plan to replace them with AppLocker or App Control for Business before those machines move to Windows 11.

  • Pros: built into Windows, no extra licensing
  • Cons: deprecated, unreliable on Windows 11, hash rules break with every app update

Method 5: AppLocker

First, a common misconception: since update KB5024351 (2023), AppLocker policies can be enforced on all editions of Windows 10 version 2004 and later and on Windows 11, including Pro. Many admins on Pro licences skip AppLocker because of outdated advice.

Group Policy path: Computer Configuration > Windows Settings > Security Settings > Application Control Policies > AppLocker.

Before you configure any rules, set the Application Identity service (AppIDSvc) to start automatically. AppLocker does nothing if that service isn't running, and it is the most common cause of "I configured AppLocker but nothing is blocked."

To close the per-user install loophole, create executable rules that cover %USERPROFILE%\AppData and the Downloads folder. Prefer publisher rules to path rules. Path rules are quick to set up but block legitimate business apps that install to user-writable folders too; publisher rules match the code-signing certificate, so you can allow known, signed business apps and block the rest from those folders.

AppLocker's default rules are allow rules for Program Files and the Windows folder. On their own they restrict nothing, so you also need enforcement mode and rules for user-writable paths. Apply deny rules to a group such as Authenticated Users rather than Everyone, so administrators aren't locked out.

Include packaged app rules as well as executable rules. If packaged app rules are enforced without allowing the built-in Windows apps, the Start menu, Search and Settings can stop working. Run every new rule set in audit mode first and read the AppLocker event logs before you enforce.

Microsoft keeps AppLocker supported with security fixes but puts new development into App Control for Business, so plan your long-term rules there.

  • Pros: user and group-level control, available on all supported editions
  • Cons: no new features, needs AppIDSvc running, rules need careful testing

If AppLocker events appear in Event Viewer but nothing is blocked, check that AppIDSvc is set to Automatic and actually running.

Method 6: App Control for Business (Formerly WDAC)

App Control for Business is the forward-looking choice. Microsoft develops it actively, while AppLocker receives security fixes only. It can also control scripts, MSI files and PowerShell, and it is managed through Intune, Configuration Manager, Group Policy or another MDM.

The key difference from AppLocker: App Control policies are usually built as default deny, so anything not explicitly trusted is blocked. That is the stronger posture, and it takes more preparation.

Deploy in audit mode first. Audit mode logs what would be blocked without blocking it. Teams that skip audit mode and go straight to enforcement often find remote support tools, drivers or business apps blocked. In complex environments, run audit mode for several weeks before you enforce.

The managed installer option trusts apps installed by your chosen deployment tool, which cuts down the rule maintenance that makes strict allow lists hard for small teams.

  • Pros: kernel-level control, default deny, actively developed, can use reputation-based trust from Microsoft's Intelligent Security Graph
  • Cons: complex to design, needs an audit period, error messages can be hard to read

If App Control blocks an app that your deployment tool installed, check that the managed installer policy was in place before the app was installed. Trust is set at install time, not afterwards.

Plan for one more thing: once App Control is enforced, an app update signed with a new certificate can be blocked. Add an update test step to your patch process before you enforce. See Windows Defender Application Control for more.

Method 7: Mobile Device Management

MDM is the layer that applies all of the above at scale. Enforcement travels with the device rather than depending on the office network, which is what makes it work for remote staff.

Useful Windows policy settings to apply through an MDM:

  • BlockNonAdminUserInstall set to 1, which stops non-administrators from installing packaged Windows apps (MSIX and AppX). Microsoft lists it for Enterprise and Education editions, Windows 10 version 2004 and later; it does not apply to Pro.
  • MSIAllowUserControlOverInstall left disabled, so users can't change protected installer options.
  • MSIAlwaysInstallWithElevatedPrivileges left disabled, because enabling it lets any MSI install with admin rights.

One gap that surprises admins: blocking the Microsoft Store doesn't block winget. Standard users can run winget install to add per-user packages from the command line even when the Store is blocked. Microsoft's App Installer policies include a setting to turn off the Windows Package Manager command-line interface; you can also block winget.exe with AppLocker or App Control. Test either change on a pilot group first.

An MDM tool lets you apply software allow and block policies to your Windows fleet from one console, targeted to groups so you can pilot restrictions before rolling them out company-wide. It also keeps a record of software changes that Group Policy alone doesn't give you. For the wider picture, see Windows application management.

  • Pros: central enforcement, a record of changes, scales without per-machine Group Policy work, an app catalog reduces help desk requests
  • Cons: some Windows policy settings are Enterprise and Education only; works best paired with AppLocker or App Control for Business

Software Installation Control Methods: Comparison

MethodWindows editionBlocks per-user installs?Domain or MDM needed?MaintenanceBest for
Remove local adminAllNoNoLowFirst step everywhere
Windows Installer policyAllMSI onlyGroup Policy or MDMLowBlocking user-started MSI installs
UAC hardeningAllNoNo (local policy works)LowRefusing elevation requests
SRPDeprecatedPartlyGroup PolicyMediumLegacy Windows 10 machines only
AppLockerAll editions (Windows 10 2004+ and Windows 11)Yes, with rules for user-writable pathsGroup Policy or MDMMedium to highDomain or MDM-managed fleets
App Control for BusinessWindows 10 and 11YesMDM, Configuration Manager or Group PolicyHigh (audit first)Default deny, the long-term choice
MDM policyVaries by settingPartly; combine with app controlMDMLowCentral fleet management

Which Method Fits Your Setup

The table shows what each method catches and misses. Use the guide below to pick a combination for your environment.

What describes your Windows environment?

  • Mixed Windows 10 and 11, no Active Directory domain: remove local admin first, then add AppLocker or App Control for Business through your MDM. Skip SRP.
  • Microsoft Intune or another MDM already in place: device restriction and app control policies from the MDM, with App Control for Business as the long-term target.
  • Active Directory but no MDM: AppLocker through Group Policy as the main tool, with the Windows Installer policy, and executable rules for user-writable paths to close the per-user loophole.
  • Not sure: remove local admin from all users today. That one step blocks most unauthorized installs while you plan the rest.

The Gaps GPO Alone Won't Fix

Even a well-configured Group Policy setup leaves three gaps open. Each is a path for unapproved software, and sometimes for data to leave the company.

The goal isn't a single policy. It is a set of layered controls that catches what any one method misses.

Gap 1: The per-user installer loophole. This is the most common failure in practice. Apps packaged for the user profile bypass every Windows Installer restriction. AppLocker or App Control rules covering %USERPROFILE%\AppData fix it, ideally with publisher rules rather than path rules.

Gap 2: winget. Blocking the Microsoft Store and blocking winget are two separate controls. If the Store is blocked but users still install apps from the command line, winget is almost certainly the channel. Turn off its command-line interface by policy or block winget.exe with app control.

Gap 3: Portable applications. Apps that run without installing, from the Downloads folder or a USB drive, aren't stopped by installer controls. App control rules stop them running, and blocking USB storage closes the USB route: Computer Configuration > Administrative Templates > System > Removable Storage Access in Group Policy, or a USB storage policy in your MDM.

If unapproved software does cause a problem, an MDM lets you act on the device remotely, for example by blocking the app with a policy, opening a remote session to look into it or wiping a company PC, without physical access.

Before You Flip the Switch: The Organizational Layer

The biggest reason software restriction projects stall is that IT announces the policy before leadership has committed to it in writing. Technical controls get reversed when senior staff opt out, and they will if they weren't part of the decision.

Get leadership sign-off first. Admins who have removed local admin company-wide name this as the prerequisite. It helps when the CEO announces the change and is visibly covered by the same rules.

Have HR and Legal own the acceptable use policy. HR and Legal draft it with IT's input, and employees sign it. When a violation happens, HR can act on a document they own, instead of the issue coming back to IT to "fix technically". See our acceptable use policy template.

Plan for legitimate exceptions. Developers and contractors sometimes need elevation for specific tasks. Removing admin rights with no way to grant temporary elevation creates friction and pushback. Just-in-time elevation tools, such as Endpoint Privilege Management in Microsoft Intune, let users request time-limited admin rights for approved tasks. Keep exceptions within the same least privilege approach as everything else.

Managing this across many devices

trio.so lists the installed apps on every Windows PC and controls which apps may run with software allow and block lists, assigned to device groups so you can pilot a restriction before rolling it out. On Windows it can also deploy an App Control for Business policy. Approved apps install from its catalog or as MSI packages, PowerShell scripts run on enrolled PCs, and the trio.so agent can be installed through Group Policy or an RMM tool you already use. Plans start at $5 per device.

A device in the trio.so console, Software tab, listing installed apps with version, publisher and install source.
trio.so lists every installed app on a device, the starting point for an allow or block list.

Frequently Asked Questions

How do I stop employees from installing software on Windows?

Make everyday accounts standard users, restrict Windows Installer and the Microsoft Store, and add AppLocker or App Control for Business to block apps that install into the user profile. Across many PCs, apply these rules from an MDM.

How do I prevent standard users from installing programs in Windows 11?

Standard users can't install machine-wide programs, but they can install per-user apps. Use AppLocker or App Control for Business rules that cover the user profile and Downloads folder, and turn off winget's command-line interface or block it.

How can companies automatically block newly installed software?

Use default-deny app control such as App Control for Business, so anything not on the approved list is blocked from running even if it gets installed, or an MDM block list applied to every PC.

How do I block the Microsoft Store for users?

Turn off the Store app with Group Policy or your MDM, and remember that winget is separate: turn off its command-line interface by policy or block it with app control.

What is the best tool to restrict which apps employees can install?

For a few PCs, standard accounts plus AppLocker. For a fleet, an MDM tool that applies app allow and block lists and App Control for Business policies to every Windows PC from one console.

Related reading: application whitelisting, application blacklisting, Windows application management and Windows Defender Application Control.

Ready-to-use Templates

Must-have Template Toolkit for IT Admins

Explore All
Template Toolkit

Decide which apps can run on every PC

trio.so lists installed apps and blocks or allows software on Windows from one console. Plans start at $5 per device.

Start free trial

Manage Every Device From One Console

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

14-day free trial. No credit card required.

trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.

Smiling womanAbstract geometric patternAbstract geometric patternSmiling womanSmiling woman

Frequently Asked Questions (FAQ)

Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.

Make everyday accounts standard users, restrict Windows Installer and the Microsoft Store, and add AppLocker or App Control for Business to block apps that install into the user profile. Across many PCs, apply these rules from an MDM.

Standard users can't install machine-wide programs, but they can install per-user apps. Use AppLocker or App Control for Business rules that cover the user profile and Downloads folder, and turn off winget's command-line interface or block it.

Use default-deny app control such as App Control for Business, so anything not on the approved list is blocked from running even if it gets installed, or an MDM block list applied to every PC.

Turn off the Store app with Group Policy or your MDM, and remember that winget is separate: turn off its command-line interface by policy or block it with app control.

For a few PCs, standard accounts plus AppLocker. For a fleet, an MDM tool that applies app allow and block lists and App Control for Business policies to every Windows PC from one console.

Related

From the blog

The related industry news, interviews, technologies, and resources.