Black screen when you resume a laptop from hybrid shutdown in Windows

Applies To
Windows Server 2012 R2 Datacenter Windows Server 2012 R2 Standard Windows Server 2012 R2 Essentials Windows Server 2012 R2 Foundation Windows 8.1 Enterprise Windows 8.1 Pro Windows 8.1 Windows RT 8.1

This article describes an issue that occurs when you resume a laptop that is running Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2 from hybrid shutdown. A hotfix is available to resolve this issue. The hotfix has a prerequisite.

Symptoms

Assume that you have hybrid shutdown enabled on a laptop. When you initialize the shutdown operation, before the shutdown operation is complete, you also do something else, such as closing the lid that makes the computer enter into sleep state. After you resume the computer from sleep state, the shutdown operation will continue, and the system enters into hybrid shutdown state. After you resume the laptop from this hybrid shutdown state, you may see a black screen, and you cannot log on to the system.

Resolution

To resolve this issue, install the hotfix that is described in this article together with the April 2015 win32k.sys package (3042216).

Hotfix information

Important Do not install a language pack after you install this hotfix. If you install a language pack, the language-specific changes in the hotfix will not be applied, and you will have to reinstall the hotfix. For more information, see Add language packs to Windows.

 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, go to 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 the April 2014 update rollup for Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 (2919355) installed on Windows 8.1 or Windows Server 2012 R2.

Registry information

To apply 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:

    Version Product Milestone Service branch
    6.3.960 0.16 xxx Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 RTM GDR
    6.3.960 0.17xxx Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 RTM GDR
  • 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 name File version File size Date Time Platform
Lsm.dll 6.3.9600.17728 667,648 13-Mar-2015 02:32 x86
Workerdd.dll 6.3.9600.17415 12,800 29-Oct-2014 02:03 x86

For all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File name File version File size Date Time Platform
Lsm.dll 6.3.9600.17728 780,800 13-Mar-2015 03:21 x64
Workerdd.dll 6.3.9600.17415 14,336 29-Oct-2014 02:48 x64

For all supported Windows RT 8.1

File name File version File size Date Time Platform
Lsm.dll 6.3.9600.17728 530,944 13-Mar-2015 02:17 Not applicable
Workerdd.dll 6.3.9600.16384 12,800 22-Aug-2013 03:14 Not applicable

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 property Value
File name X86_9968fa7cd2df1ab465cfbbe659fa3d0d_31bf3856ad364e35_6.3.9600.17728_none_f002641905e14630.manifest
File version Not applicable
File size 724
Date (UTC) 13-Mar-2015
Time (UTC) 23:06
Platform Not applicable
File name X86_microsoft-windows-t..localsessionmanager_31bf3856ad364e35_6.3.9600.17728_none_3a2962c825f010be.manifest
File version Not applicable
File size 42,063
Date (UTC) 13-Mar-2015
Time (UTC) 23:08
Platform Not applicable

Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2

File property Value
File name Amd64_ba31bf22d5cef321d22712c23fd467cb_31bf3856ad364e35_6.3.9600.17728_none_f3b7a14eabbd197c.manifest
File version Not applicable
File size 728
Date (UTC) 13-Mar-2015
Time (UTC) 23:06
Platform Not applicable
File name Amd64_microsoft-windows-t..localsessionmanager_31bf3856ad364e35_6.3.9600.17728_none_9647fe4bde4d81f4.manifest
File version Not applicable
File size 42,069
Date (UTC) 13-Mar-2015
Time (UTC) 23:10
Platform Not applicable

Additional files for all supported Windows RT 8.1

File property Value
File name Arm_281b4905ccbd7a4b1029fd908f295f22_31bf3856ad364e35_6.3.9600.17728_none_71dba13488673c36.manifest
File version Not applicable
File size 724
Date (UTC) 13-Mar-2015
Time (UTC) 23:06
Platform Not applicable
File name Arm_microsoft-windows-t..localsessionmanager_31bf3856ad364e35_6.3.9600.17728_none_3a2bd52025ed2f84.manifest
File version Not applicable
File size 42,063
Date (UTC) 13-Mar-2015
Time (UTC) 23:06
Platform Not applicable

Status

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

References

See the terminology that Microsoft uses to describe software updates.