We have seen a decline in support cases from Hyper-V customers reporting issues that involve the error message “0x0000001” and “Stop 0x0000001a since the release of SP1 for Windows Server Hyper-V R2. Our advice for Hyper-V users, the solution is to install SP1. This TechNet Wiki article tells you How to Install and Manage Hyper-V Server 2008 R2 SP1.
However, there are confusing results presented in search engines, because these error message strings are also found in Windows 7 and Windows XP. Folks who are in a hurry – for example those dealing with some critical and cryptic error – do not always read the content we publish with dogmatic precision.
- if you are running Windows XP and receive “Stop: 0x0000001E” Error Message During Setup –see http://support.microsoft.com/kb/161703
- if you are running Windows 7 and receive error code 0x00000001, this Microsoft Answers post (http://answers.microsoft.com/en-us/windows/forum/windows_vista-windows_install/what-is-error-code-0x00000001/a41e6e0e-84ad-4886-a11b-cd550eefde41) explains the many possible causes and several fix-it steps you can take.
- if you receive a “STOP: 0x0000001a” error message on a computer that has an Intel Westmere processor together with the Hyper-V role installed on Windows Server 2008 or on Windows Server 2008 R2, then this KB (http://support.microsoft.com/kb/981791) explains the hotfix you need to install, or, you can use Windows Update.
- if you receive an error 0x00000101 on a machine with a Nehalem processor and the Hyper-V role on a computer that is running Windows Server 2008 R2, then this KB (http://support.microsoft.com/kb/2264080) explains the update package you need to install, or you can use Windows Update.