asked on LiteTouchPEx64.wim Returns 0xc0000001 Error During Boot
I upgraded my deployment server to MDT 2013 Update 2 and my ADK to the Windows 10 version. Then I regenerated by boot image with the Update Deployment Share tool and replaced the LiteTouchPEx64.wim in the Deployment Services>Boot Images with the new .WIM.
Now when I try to boot any computer off of the deployment server I get "Status: 0xc0000001 Info: A required device isn't connected or can't be accessed." error at the end of the Loading Files: (Path to the boot directory of Deployment Services folder) screen.
I've been looking and the only things I can find on this are related to attempting to deploy a VM with RAID drives and the issue seemed to revolve around the RAID drivers. But in this case the deployment process worked correctly before upgrading to MDT 2013 Update 2 and no drivers have been added since.
Does anyone have any insight as to why I am getting this error. Or failing that, where I might be able to find logs that could point me in the right direction?
Now when I try to boot any computer off of the deployment server I get "Status: 0xc0000001 Info: A required device isn't connected or can't be accessed." error at the end of the Loading Files: (Path to the boot directory of Deployment Services folder) screen.
I've been looking and the only things I can find on this are related to attempting to deploy a VM with RAID drives and the issue seemed to revolve around the RAID drivers. But in this case the deployment process worked correctly before upgrading to MDT 2013 Update 2 and no drivers have been added since.
Does anyone have any insight as to why I am getting this error. Or failing that, where I might be able to find logs that could point me in the right direction?
Windows OSMicrosoft Legacy OSInstallation
Last Comment
Mdamon808
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
Not the ideal, but I was unable to rebuild the BCD correctly.
Here is a post where MDT assigned the wrong block size for the storage: https://graemebray.wordpress.com/2014/01/16/unable-to-boot-to-winpe-0xc0000001-a-required-device-isnt-connected/
Here is how to manually rebuild the BCD: http://rajandmk.blogspot.com/2012/09/how-to-create-clean-bcd-file-to-fix.html
One post; however, suggested you needed to reboot the MDT server and then recreate the image.