0X000004EC

Fix 0x000004EC: Program Blocked by Group Policy

Windows Errors Intermediate 👁 0 views 📅 May 26, 2026

This error means Windows security policy is blocking a program. Usually caused by Software Restriction Policies or AppLocker. I'll show you how to fix it.

Software Restriction Policies (Most Common Cause)

Nine times out of ten, this error pops up because of Software Restriction Policies. I saw it last month on a Windows 10 Pro machine where the owner couldn't run a PDF converter they'd used for years. The error code 0x000004EC is Windows telling you a policy says no.

The fix is usually in the Local Group Policy Editor. Here's the exact path:

  1. Hit Win + R, type gpedit.msc, and press Enter.
  2. Go to Computer Configuration > Windows Settings > Security Settings > Software Restriction Policies.
  3. If you don't see anything under that node, right-click Software Restriction Policies and choose New Software Restriction Policies.
  4. Double-click Enforcement on the right side. Make sure it's set to All users except local administrators (or All users if you want it to affect everyone). Then click OK.
  5. Double-click Designated File Types. Check if the file extension of your blocked program (like .exe, .msi, .ps1) is listed. If it's missing, add it.
  6. Now look at Security Levels. If Disallowed is set as the default, that's your problem. Right-click Disallowed and choose Properties. Set it to Not Configured, then click OK.
  7. Close the editor and reboot.

If the program still won't run, check the Additional Rules section under Software Restriction Policies. Sometimes a path rule or hash rule is blocking just that one file. Delete the rule that matches your program.

AppLocker Rules (Second Most Common)

AppLocker is stricter than Software Restriction Policies. It's common on Windows 10/11 Pro, Enterprise, and Education editions. I had a client whose IT department locked down everything except approved apps. Their accounting software got hit with this error after an update changed the file hash.

To check AppLocker:

  1. Open gpedit.msc again.
  2. Go to Computer Configuration > Windows Settings > Security Settings > Application Control Policies > AppLocker.
  3. Click on Executable Rules. Look for any rule that denies your program. It might be a path rule, a publisher rule (based on the digital signature), or a file hash rule.
  4. If you see a deny rule for your program, right-click it and choose Delete. Or if you want to allow it, create an Allow rule: right-click Executable Rules, choose Create New Rule, and follow the wizard. Pick Path as the condition and browse to the program's .exe file.
  5. If your program is a script (like a .ps1 or .vbs), check Script Rules and Windows Installer Rules too.
  6. Run gpupdate /force in an admin command prompt, then reboot.

One thing that trips people up: AppLocker rules can be inherited from a domain. If you're on a company network, you might not be able to change them locally. In that case, talk to your IT admin.

Registry Key Bloating or Corruption (Less Common, but Real)

I've seen this on older machines that had Group Policy updates applied over years of domain changes. The registry gets cluttered with stale policy entries. The 0x000004EC error can show up if a policy key is referencing a program that no longer exists or has moved.

Here's the registry path to check:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Safer\CodeIdentifiers

Also check:

HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Safer\CodeIdentifiers

Before touching the registry, back it up. Export the key first (right-click, Export). Then look for any keys or values that reference your blocked program. If you find one, delete it. Be careful—deleting the wrong thing can break other policies.

After cleaning up, run gpupdate /force and reboot. If the error persists, you might need to reset the entire policy cache. That's a deeper fix: stop the Group Policy Client service in services.msc, delete the contents of C:\Windows\System32\GroupPolicy, then restart the service and run gpupdate /force.

Quick Reference Summary

Cause Fix Where to Check
Software Restriction Policies Check default security level, delete path or hash rules gpedit.msc > Software Restriction Policies
AppLocker Rules Delete or modify deny rules for your program gpedit.msc > AppLocker
Registry Corruption Delete stale policy keys in Safer\CodeIdentifiers Registry Editor

If none of these work, run rsop.msc (Resultant Set of Policy) to see exactly what policies are applying. That tool will show you the exact policy name and source. Then you can hunt it down. Good luck—you'll get this sorted.

Was this solution helpful?