Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

You cannot log on as a local administrator when you restart in DSRepair mode


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a domain controller that is running Windows Server 2012 R2 or Windows Server 2012.
  • You apply the following User Account Control Group Policy setting on the server:
    • Admin Approval Mode for the built-in Administrator account
  • You restart the domain controller in DSRepair mode.
  • You log on as a local administrator.

In this scenario, a black screen is displayed after the authentication screen. At this point, you can do nothing except log off by pressing Ctrl+Alt+Delete.

↑ Back to the top


Cause

This problem occurs because the Winlogon service impersonates the split-user token during the logon process, and this token does not have sufficient permissions to log on as an administrator.

↑ Back to the top


Resolution

To resolve this issue in Windows 8.1 or Windows Server 2012 R2, install update 2955164. For more information about update 2955164, click the following article number to view the article in the Microsoft Knowledge Base:
2955164 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: May 2014

To resolve this issue in Windows 8 or Windows Server 2012, install the hotfix that is described in this article.

Hotfix information

A supported hotfix is available from Microsoft Support. 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 the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

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, contact 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, go to 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.

Prerequisites

To apply this hotfix, you must have Windows 8 or Windows Server 2012 installed.

Restart requirement

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

Hotfix replacement information

This hotfix does not replace any previously released hotfix.

↑ Back to the top


File information

For a list of the files that are provided in this update, download the file information for this update 2937044.

↑ Back to the top


Status

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

↑ Back to the top


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbsurveynew, kbbug

↑ Back to the top

Article Info
Article ID : 2937044
Revision : 1
Created on : 1/7/2017
Published on : 11/20/2016
Exists online : False
Views : 237