Deploying Windows 8 with Windows Deployment Services (WDS) - Consistent xC0000005 Error

Proposed Answer Deploying Windows 8 with Windows Deployment Services (WDS) - Consistent xC0000005 Error

  • Saturday, October 27, 2012 7:12 PM
     
     

    Every time I install it using WDS, I get the following errors in the attached picture. If I burn that same ISO image to a disc, everything works fine.

    I have tried two different versions of the iso image (en-US and en-GB), verified that the hashes are correct, tried VMs and a physical machine, tried with and without an unattend.xml file.

    Every time I run into that error (xC0000005). I was given some explanations on what would cause that error, the first being bad ram, the second being a bad hard drive. Well, I don't think that that is the case in this scenario unless all of my VMs, and computers are going bad.

    I am running Windows Server 2012 Datacenter Edition which was activated.

    How would I go about resolving this? It has pretty much put my plans on hold at the moment to do testing for Windows 8.

    EDIT:

    I also noticed that you can't select network shares (or I couldn't) for the unattend.xml answer file. I have a Z drive that is a mapped drive to a file server, is this supposed to happen?



    • Changed Type [OCN]GH0 Saturday, October 27, 2012 7:13 PM Better suited as a discussion to resolve the problem
    • Edited by [OCN]GH0 Saturday, October 27, 2012 7:25 PM Asking second question.
    • Edited by [OCN]GH0 Saturday, October 27, 2012 7:26 PM
    • Changed Type [OCN]GH0 Saturday, October 27, 2012 7:27 PM
    •  

All Replies

  • Tuesday, October 30, 2012 7:09 AM
    Moderator
     
     Proposed Answer

    Hi,

    Are you sure you have added the Windows 8 boot.wim on your WDS server?

    At the same time, you are using VMs to do the test. Please let me your VMs type, Hyper-V or other VM productions.

    From the snapshot you provided, it seems that you are not trying to install Windows 8, from my side testing, it could be got installed via WDS:

    If the failure occurs in Windows PE after the disk configuration page of the WDS client is completed, you can find the logs on the local disk volume at the $Windows.~BT\Sources\Panther folder. The local disk volume is usually the drive C. Use Shift+F10 to open a command prompt, and then change the directory to the location.

    Regards,

    James


    James Xiong

    TechNet Community Support

  • Thursday, November 15, 2012 11:43 PM
     
     

    Hello James,

    I have WDS running on 2008 R2 Server. I uploaded the boot.wim from the Windows 8 64bit Enterprise .iso and when I boot a machine to PXE and start the process choosing the Windows 8 boot image, it keeps failing on the "Setup is Starting" screen. It's giving me an error message that says "Windows Setup cannot install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation.

    I thought it was related to network or storage drivers, but it's failing even on a VM from HyperV. I also have an Optiplex 990, I made sure to inject the critical network and storage drivers (http://www.dell.com/support/drivers/us/en/04/DriverDetails/Product/optiplex-990?driverId=92G6N&osCode=W864&fileId=2993148860) and no luck..

    It seems that it is not network related because when the error is presented I can open a command prompt window (shift+F10) and validate that it still has a valid iP and network configuration (ipconfig), I can also ping resources on my network. Then I was wondering if it's a storage driver issue, but at this point of the setup I think we do not have any log nor anything else available to look (log files are created while install.boot is running).

    Any suggestion is welcome!! Thanks

    By the way, all my Windows 7 Install and Boot images are working perfectly.

  • Saturday, November 17, 2012 12:04 AM
     
     
    Have you installed from the media you used to place the .wim files into WDS?  Wondering if you have bad media, because that is such a strange error.

    tim