Fix ERROR_RESOURCE_PROPERTY_UNCHANGEABLE (0x000013E1) on Windows

1. Group Policy Is Overriding Your Changes

This is the most common reason I see this error. You're trying to change a resource property (like a printer permission, a file share security setting, or a scheduled task trigger) and Windows says “nope, can't do that.” The real culprit is almost always a domain group policy that's setting that same property to a different value.

Here's the trigger: You're on a corporate laptop, connected to the office network, and you try to modify a local resource that's also managed by Active Directory. Windows sees the conflict and throws 0x000013E1.

Fix it:

1. Open rsop.msc (Resultant Set of Policy) by hitting Win+R and typing it in.
2. Look under Computer Configuration > Administrative Templates > System > Resource Manager (or the specific path for your resource type).
3. Find the policy that matches the property you're trying to change. It'll say Enabled and show a conflicting value.
4. If you have admin rights on the domain, edit the GPO from your Domain Controller: gpmc.msc → right-click → Edit → find that policy → set it to Not Configured or match your desired value.
5. Run gpupdate /force from an admin command prompt. Reboot. Try again.

If you don't have domain admin rights, you need to talk to your IT team. No workaround here that I'd recommend.

2. Registry Lock — Another Application Holds the Property

Less common but still frequent: a third-party app (antivirus, backup tool, or even a misbehaving driver) has registered a resource property and won't let go. I've seen this with Symantec Endpoint Protection and older versions of Acronis True Image.

Where to check:

1. Open regedit.exe as admin.
2. Navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ and look for the service tied to the resource. For example, if it's a printer, look under Spooler subkeys.
3. Look for a DependOnService or RequiredPrivileges value that includes your target resource. That's the lock.
4. Right-click that value → Modify → remove the conflicting entry. Back up the key first by exporting it.
5. Reboot. If the error persists, the lock might be in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ under a subkey named after the resource type.

Pro tip: Use Process Monitor from Sysinternals. Filter by Path contains 0x000013E1 (or the resource name) and watch which process is holding the key. It's saved me hours.

3. Local Security Policy Conflict (Especially on Windows 10/11 Pro)

If you're not on a domain, the error can still pop up when a local security policy setting clashes with a manual change. This happens most often when you try to change a User Rights Assignment or Audit Policy that's also defined in the local GPO.

Fix it:

1. Open secpol.msc (Local Security Policy).
2. Go to Security Settings > Local Policies > User Rights Assignment (or Audit Policy).
3. Find the setting that matches your resource property. Double-click it.
4. If it says Define these policy settings is checked, uncheck it. Or remove the conflicting user/group from the list.
5. Apply, close, then open an admin command prompt and run gpupdate /force.
6. Reboot.

I've also seen this error on Windows 11 22H2 when trying to modify a scheduled task's Run with highest privileges checkbox. The fix was the same — local security policy had that task locked down.

Quick-Reference Summary Table

You should be back in business after trying the fix that matches your situation. This error tripped me up the first time I saw it on a client's Windows 10 20H2 machine. Took me an hour to realize it was just a stale group policy. Don't let it waste your time.