Microsoft KB Archive Search

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.

  1. Home
  2. It takes a long time to log on to a domain-joined computer that runs Windows 8.1 or Windows Server 2012 R2

It takes a long time to log on to a domain-joined computer that runs Windows 8.1 or Windows Server 2012 R2

View products that this article applies to.

This article describes an issue after the required updates are installed in Windows 8.1 or Windows Server 2012 R2. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

↑ Back to the top

Symptoms

After you install the updates, a domain-joined computer may freeze during the next logon attempt while the "Please wait" message is displayed on the screen. Additionally, the logon process may be blocked for up to two hours.

↑ Back to the top

Cause

This issue occurs because of a problem when the Service Control Manager starts Windows services.

↑ Back to the top

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:
http://support.microsoft.com/contactus/?ws=support
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 update 2919355 installed in Windows 8.1 or 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.
File information
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows 8.1 and Windows Server 2012 R2 file information and notes

Important Windows 8.1 hotfixes and Windows Server 2012 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 8.1/Windows Server 2012 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:

    VersionProductMilestoneService branch
    6.3.960 0.17 xxxWindows 8.1 and Windows Server 2012 R2RTMGDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 8.1
File nameFile versionFile sizeDateTimePlatform
Gpapi.dll6.3.9600.17415115,67229-Oct-201403:15x86
Gpsvc.dll6.3.9600.176311,207,80812-Jan-201501:10x86
For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File nameFile versionFile sizeDateTimePlatform
Gpapi.dll6.3.9600.17415135,30429-Oct-201404:04x64
Gpsvc.dll6.3.9600.176311,356,80012-Jan-201501:32x64
Gpapi.dll6.3.9600.17415115,67229-Oct-201403:15x86

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2
Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_8adb13ee07275bf3df41ec237075e6e1_31bf3856ad364e35_6.3.9600.17632_none_3cfe9ce41f26aebb.manifest
File versionNot applicable
File size704
Date (UTC)13-Jan-2015
Time (UTC)22:28
PlatformNot applicable
File nameX86_microsoft-windows-grouppolicy-base_31bf3856ad364e35_6.3.9600.17632_none_bcf7245802758df6.manifest
File versionNot applicable
File size154,773
Date (UTC)13-Jan-2015
Time (UTC)22:33
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_59a81c45c1d51e89262a5a46cbce06ea_31bf3856ad364e35_6.3.9600.17632_none_1b70ff6ce8358954.manifest
File versionNot applicable
File size708
Date (UTC)13-Jan-2015
Time (UTC)22:28
PlatformNot applicable
File nameAmd64_5cbcb4a9ea80a681a843c1abd178e4f7_31bf3856ad364e35_6.3.9600.17632_none_9e232f20d5f4c8ea.manifest
File versionNot applicable
File size708
Date (UTC)13-Jan-2015
Time (UTC)22:28
PlatformNot applicable
File nameAmd64_microsoft-windows-grouppolicy-base_31bf3856ad364e35_6.3.9600.17632_none_1915bfdbbad2ff2c.manifest
File versionNot applicable
File size154,779
Date (UTC)13-Jan-2015
Time (UTC)22:36
PlatformNot applicable
File nameWow64_microsoft-windows-grouppolicy-base_31bf3856ad364e35_6.3.9600.17632_none_236a6a2def33c127.manifest
File versionNot applicable
File size67,666
Date (UTC)13-Jan-2015
Time (UTC)22:36
PlatformNot applicable

↑ 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

See the terminology that Microsoft uses to describe software updates.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 3019272
Revision : 1
Created on : 1/7/2017
Published on : 2/11/2015
Exists online : False
Views : 198