Novell is now a part of Micro Focus

My Favorites


Please to see your favorites.

Device fails to boot after deployment using Windows Assessment and Deployment Kit (ADK) for Windows® 8

This document (7013318) is provided subject to the disclaimer at the end of this document.


Novell ZENworks Configuration Management


After using Windows Assessment and Deployment Kit (ADK) for Windows® 8, device fails to boot with an error screen that  is black with the following text in white:

Your PC needs to restart.
Please hold down the power button.
Error Code:  0x0000005D


This can occur for two different reasons:

a) Only use systems compatible with Windows 8 - this can be validated by:
  1. Downloading coreinfo.exe from
  2. Running the tool to determine if the system has support for NX, PAE, and SSE2.
  3. If the system is reported to support NX, PAE, and SSE2, it may be possible to use WADK to image the device, otherwise it will be necessary to use the compatible WIM mode based on WINPE 3.x.
b) In addition, some processors like the Intel Xeon may be set to 64-bit mode ("Capable")  instead of 64-bit mode ("Enabled"). WADK will not work in "Capable" mode (see Section 7.5.9)


a) This is a Microsoft limitation. To use the WADK, the device needs to be fully compatible with Windows 8 as shown in Microsoft articles such as:

b) this is because the SMBIOS reports that the device is 64-bit, regardless of the setting, so the 64-bit WADK is used to boot, but when in "Capable" mode the machine is actually using the 32-bit mode, and so the WADK cannot boot.

Additional Information


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.

  • Document ID:7013318
  • Creation Date:18-SEP-13
  • Modified Date:19-SEP-13
    • NovellZENworks Configuration Management

Did this document solve your problem? Provide Feedback