Time-out failures after initial deployment of Device Registration service 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 when you try to create a new key in Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.


This issue occurs when new key creation fails in distributed key management (DKM). Additionally, it takes a long time to find a valid key, which affects Active Directory Federation Services (AD FS) extranet access, device authentication, and device registration.

See the cause of the issue in this article.

Hotfix information

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

If the hotfix is available for download, there is a "Hotfix Download Available" section at the top of this Knowledge Base article. If this section does not appear, submit a request to Microsoft Customer Service and Support to obtain 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 do not 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 do not see your language, it is because a hotfix is not available for that language.


To apply this hotfix, you must have update 2919355 installed in Windows Server 2012 R2.

Registry information

To use the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You may have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not 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.

More Information


This issue occurs because the service account for the Device Registration service (DRS) service does not have the correct permissions, and leaves an incomplete object whena new key is created in DKM. The next time that DRS configuration is read, it will run this logic again and create another object. Then, it takes a long time to find a valid key because there are many objects. Specifically, the DKM key objects creation started when the key that is created during Initialize-ADDeviceRegistration became invalid and a new key had to be created. Therefore, an explosion of DKM objects in the DRS configuration causes time-out failures in DRS and AD FS.


See the terminology that Microsoft uses to describe software updates.