Yes, Windows 11 lets you block standard users from installing programs, and you can do it in several ways depending on how much control you need. The most straightforward method is to change a single Group Policy setting that prevents non-administrator accounts from running the Windows Installer (MSI) packages that most setup programs use. You can also use Registry Editor or a standard user account with controlled folder access, though the Group Policy approach is the most reliable for everyday software.
Why Would You Want to Block Installations?
Blocking software installation on a Windows 11 PC is a common request for parents, IT administrators, and anyone who shares a computer. Standard user accounts already have limited permissions—they can’t install most software that writes to Program Files or the system registry. But many installers are poorly written and request administrator elevation, which triggers a UAC prompt. If the user knows the administrator password, they can bypass the restriction. Blocking installation outright removes that possibility and also prevents accidental installs of bundled adware or unwanted toolbars. It’s also a useful security measure: many malware droppers rely on the user clicking “Yes” to a UAC prompt, so preventing installation at the system level reduces that attack surface.
Method 1: Group Policy (Windows 11 Pro, Enterprise, Education)
Group Policy Editor is only available on Windows 11 Pro, Enterprise, and Education editions. Home users will need to use the Registry method below. Here’s how to set it:
- Press Win + R, type
gpedit.msc, and press Enter. - Navigate to Computer Configuration → Administrative Templates → Windows Components → Windows Installer.
- Double-click “Prohibit User Installs” on the right.
- Set it to Enabled. The default option “Hide user installs” will also block the installation but shows the “feature is disabled” message. Choose “Prohibit user installs” to show a more generic error.
- Click OK and restart the computer or run
gpupdate /forcein Command Prompt.
This policy prevents standard users from installing MSI packages. It does not block per-user installs (like some apps that install to AppData) or executable files that don’t use the Windows Installer. For those, you’d need to also restrict execution via AppLocker or Software Restriction Policies, which are more complex.
Method 2: Registry Editor (Works on All Editions)
If you have Windows 11 Home, you can achieve the same effect by editing the registry. This method requires administrator rights and a bit of care, but it’s straightforward:
- Press Win + R, type
regedit, and press Enter. - Navigate to
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer. If theInstallerkey doesn’t exist, right-click onWindows, select New → Key, and name itInstaller. - Right-click on the
Installerkey, select New → DWORD (32-bit) Value, and name itDisableMSI. - Double-click
DisableMSIand set the value to2(which means “Prohibit user installs”). A value of1means “Hide user installs”. - Click OK and restart the PC.
This registry change is the exact same underlying setting as the Group Policy. If you later change your mind, set the value to 0 or delete the DisableMSI value.
Method 3: Use a Standard User Account (and Don’t Share the Admin Password)
The simplest and often most effective method is to ensure the person you want to restrict uses a standard user account. Windows 11 makes this easy:
- Go to Settings → Accounts → Family & other users.
- Click Add account and choose “Add a user without a Microsoft account” (or create a local account).
- After creating the account, select it and click Change account type. Set it to Standard User.
With a standard account, any attempt to install software that requires admin rights will trigger a UAC prompt asking for an administrator password. If you don’t give the user that password, they can’t install. However, some installers can run without admin rights (they install to the user’s AppData folder), so this isn’t a complete block. For those, you’d need to combine with the Group Policy or Registry method.
What About Blocking All Executables?
If you want to block a specific user from running any installer—or any program at all—you can use AppLocker (Windows 11 Pro/Enterprise) or Software Restriction Policies. These are more advanced and can be tricky to configure without breaking legitimate apps. A simpler alternative is to use Controlled Folder Access (part of Windows Security) to prevent programs from writing to protected folders, but that doesn’t stop installation itself. For most home users, the Group Policy or Registry method is sufficient because the vast majority of installers are MSI-based.
Common Problems and Troubleshooting
- Policy doesn’t take effect: Run
gpupdate /forceas administrator or restart the PC. Also, make sure you’re editing the local policy, not a domain policy that might be overridden. - User can still install some programs: Some apps use non-MSI installers (like NSIS or Inno Setup). To block those, you’d need to also restrict executable files. You can do that with AppLocker, but it’s complex. A simpler workaround is to deny write permission to the user’s AppData\Local\Temp folder, but that can break other things.
- You can’t install anything yourself: The policy applies to all standard users, including yourself if you’re using a standard account. Log in as an administrator to make changes or install software.
- Windows Store apps: The policy does not affect Microsoft Store apps. If you want to block those, you can disable the Store via Group Policy or simply not sign in with a Microsoft account.
Comparison of Methods
| Method | Edition | Effectiveness | Difficulty |
|---|---|---|---|
| Group Policy | Pro, Enterprise, Edu | High for MSI | Easy |
| Registry | All | High for MSI | Easy |
| Standard User + UAC | All | Medium (some apps bypass) | Very easy |
| AppLocker | Pro, Enterprise | Very high (all exe) | Hard |
Frequently Asked Questions
Can I block a specific user from installing programs without affecting other users?
Yes. The Group Policy and Registry methods apply to all standard users, but you can also apply a per-user policy by editing the registry under HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer for that specific user. However, this is more complex and rarely needed. The simplest way is to create a separate standard account for each person and set the policy globally.
Will this block updates to already installed programs?
No, the “Prohibit User Installs” policy only blocks new installations. Updates that run with system privileges (like Windows Update) will still work. However, if an update requires user elevation, it will fail for standard users. That’s usually fine because most updates run in the background.
Can the user bypass this by renaming the installer or using a portable app?
Renaming an .exe won’t bypass the policy because the policy is based on the Windows Installer service, not the file name. Portable apps that don’t install (they just run from a folder) will still work because they don’t write to system areas. If you want to block those, you need AppLocker or Software Restriction Policies.
Does this affect the Microsoft Store?
No. The Microsoft Store uses a different installation mechanism. To block Store apps, you can disable the Store via Group Policy or simply not allow the user to sign in with a Microsoft account. On Windows 11 Home, you can also use the “Apps & features” settings to restrict installations to the Store only, but that’s a different setting.
How do I undo the block?
Simply revert the change: set the Group Policy to “Not Configured” or delete the DisableMSI registry value. Then restart the PC. The block is not permanent and does not affect your system’s integrity.
Related
General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.
More in this bed
- OneDrive Connection Problem Windows 10: Fixes
- Android Battery Care: 12 Steps to Longer Life
- Could Not Assign Applications Error on MacBook: Fix
- Fix Slow Search on Windows 11: Top Methods
- Customize Mission Control & Desktop Spaces on Mac
- Code 39 Sound Driver Issue: Fixed?