Set-Acl cmdlet fails although delegated admins have "Change Permissions" enabled in Windows Server 2012 R2

Applies to: Windows Server 2012 R2 DatacenterWindows Server 2012 R2 StandardWindows Server 2012 R2 Essentials

This article describes an issue that occurs on a Windows Server 2012 R2-based computer that has the Active Directory Domain Services (AD DS) role installed. A hotfix is available to fix this issue. The hotfix has a prerequisite and a restart requirement.


Assume that the delegated admins only have permissions to change the permissions but they're not the owner or in the system access control list (SACL). This issue occurs when delegated admins use PowerShell scripts to manage the access permissions of the objects. When this issue occurs, the admins receive an error message that looks something like this:

This security ID may not be assigned as the owner of this object.

Note This issue also occurs with the initial releases of the Remote Server Administration Tools for Windows 10.

In the newest release that comes with the final release of Windows Server 2016, this problem is solved.


To fix this issue, we have released a hotfix. Even though this issue is observed only in Windows Server 2012 R2, the hotfix also applies to Windows 8.1.

Important If you install a language pack after you install this hotfix, you must reinstall this hotfix. Therefore, we recommend that you install any language packs that you need before you install this hotfix. For more information, see Add language packs to Windows.

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that's described in this article. Apply this hotfix only to systems that are experiencing this specific problem.

If the hotfix is available for download, there's a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section doesn't appear, submit a request to Microsoft Customer Service and Support to get the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that don't qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix Download Available" form displays the languages for which the hotfix is available. If you don't see your language, it's because a hotfix isn't available for that language.


To apply this hotfix, you must have April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed in Windows 8.1 or Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you don't have to make any changes to the registry.

Restart requirement

If there's no active PowerShell instance that uses the AD Provider, you don't have to restart the system.

Hotfix replacement information

This hotfix doesn't replace a previously released hotfix.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


This issue occurs because, when a security descriptor is programmatically updated, the application can ask to only update certain parts of the security descriptor. When a delegated admin can only update the discretionary access control list (DACL), the application needs to specify this. Until this update, the Active Directory PowerShell cmdlet Set-Acl didn't use the correct flags to write out the DACL only. So, the call fails for being unable to write the owner part of the security descriptor.


See the terminology that Microsoft uses to describe software updates.

File Information

The English (United States) version of this software update installs files that have the attributes that are listed in the following tables. The dates and times for these files are listed in Coordinated Universal Time (UTC). Be aware that dates and times for these files on your local computer are displayed in your local time and with your current daylight saving time bias. The dates and times may also change when you perform certain operations on the files.