When i try to deploy a custom Windows 8.1 Pro Image Via WDS I get the above error. I have enabled Client side logging and checked WDS logs and install logs on the failed installation (Shift+F10). I don't think the issue is a matter of the drivers that are included in the boot image. If it were a network card issue i would not be able to get the WINPE on the network and start the install. Second i don't think its a storage driver issue, WINPE has formatted the Drive as one may see in  (Shift F10) DISKPART. If it were a storage driver, it would not see the drive and would not format. I am starting to thing that this may be a Windows 8/8.1 Kernel issue that i have found referenced in other forums.

That Said, I still injected my drivers into WDS then into my boot image, i was unable to do some drivers that were unsigned in WDS so i added them in DISM directly to the images. I forced the unsigned drivers so they could be added. I injected the drivers into my install and boot image. and still nothing. I then went back and removed, via DISM, all third party drivers from my boot and install image and it's still giving me the error. Help!!!!!!!!!!!!!

I can upload logs if needed. 

• Edited by wkingswt Thursday, January 29, 2015 11:33 PM

Hi wkingswt,

In addition, please confirm image file source, prevent capturing yourself or got from faulty image or installation media.

please make sure using right version Windows PE, extract Windows PE from Windows 8 installation media.

Check following precautions

First Signed device drivers are a key security feature in Windows. Drivers that are installed on x64-based computers must have a digital signature. If you're adding multiple drivers, you should create separate folders for each driver or driver category. This makes sure that there are no conflicts when you add drivers that have the same file name.

If the drivers are configured in windowsPE configuration pass they are reflected for Windows PE to use. If they are configured within the offlineServicing pass the drivers are staged to the driver store on the Windows image. Check this link for reference

http://support.brainwaregroup.com/kb/article/AA-00702/0/Error%3A-Windows-installation-cannot-continue-because-a-required-driver-could-not-be-installed.html

Also, as a workarround Adding Device Drivers to an Offline Windows Image also is an option.

You could find setup logs from the client computer by referring to following article, and see which driver failed to install.

http://support.microsoft.com/kb/936625/en-us

Regards

Hi wkingswt,

In addition, please confirm image file source, prevent capturing yourself or got from faulty image or installation media.

please make sure using right version Windows PE, extract Windows PE from Windows 8 installation media.

Check following precautions

First Signed device drivers are a key security feature in Windows. Drivers that are installed on x64-based computers must have a digital signature. If you're adding multiple drivers, you should create separate folders for each driver or driver category. This makes sure that there are no conflicts when you add drivers that have the same file name.

If the drivers are configured in windowsPE configuration pass they are reflected for Windows PE to use. If they are configured within the offlineServicing pass the drivers are staged to the driver store on the Windows image. Check this link for reference

http://support.brainwaregroup.com/kb/article/AA-00702/0/Error%3A-Windows-installation-cannot-continue-because-a-required-driver-could-not-be-installed.html

Also, as a workarround Adding Device Drivers to an Offline Windows Image also is an option.

You could find setup logs from the client computer by referring to following article, and see which driver failed to install.

http://support.microsoft.com/kb/936625/en-us

Regards

• Proposed as answer by Alex ZhaozxMicrosoft contingent staff, Moderator Friday, February 06, 2015 5:40 AM

Hi wkingswt,

In addition, please confirm image file source, prevent capturing yourself or got from faulty image or installation media.

please make sure using right version Windows PE, extract Windows PE from Windows 8.1 installation media.

Check following precautions

First Signed device drivers are a key security feature in Windows. Drivers that are installed on x64-based computers must have a digital signature. If you're adding multiple drivers, you should create separate folders for each driver or driver category. This makes sure that there are no conflicts when you add drivers that have the same file name.

Also, as a workarround Adding Device Drivers to an Offline Windows Image also is an option.

You could find setup logs from the client computer by referring to following article, and see which driver failed to install.

http://support.microsoft.com/kb/936625/en-us

Regards

• Proposed as answer by Alex ZhaozxMicrosoft contingent staff, Moderator Friday, February 06, 2015 5:40 AM
• Edited by Deason Wu 2 hours 19 minutes ago

Hi wkingswt,

In addition, please confirm image file source, prevent capturing yourself or got from faulty image or installation media.

please make sure using right version Windows PE, extract Windows PE from Windows 8.1 installation media.

Check following precautions

First Signed device drivers are a key security feature in Windows. Drivers that are installed on x64-based computers must have a digital signature. If you're adding multiple drivers, you should create separate folders for each driver or driver category. This makes sure that there are no conflicts when you add drivers that have the same file name.

Also, as a workarround Adding Device Drivers to an Offline Windows Image also is an option.

You could find setup logs from the client computer by referring to following article, and see which driver failed to install.

http://support.microsoft.com/kb/936625/en-us

Regards

• Proposed as answer by Alex ZhaozxMicrosoft contingent staff, Moderator Friday, February 06, 2015 5:40 AM
• Edited by Deason Wu Monday, February 09, 2015 9:25 AM

The Image was a volume image downloaded from VLSC. I had disabled all drivers in WDS, and I added the offline drivers via dism to the image and it didn't work. I also removed those drivers and tried to image a VM to try to eliminate the question of drivers and it still did not work. I have determined that the issue is not hardware specific and a VM should not require drivers to image.

Hi Wkingswt,

Please try to deploy a clean image to virtual machine without any driver for good measure.

please rebuild Windows PE once and make sure its version is 5.1 for Windows 8.1 since similar case could be caused by wrong version of Windows PE.

Regards,

D. Wu

Hi Wkingswt,

Please try to deploy a clean image to virtual machine without any driver for good measure.

please rebuild Windows PE once and make sure its version is 5.1 for Windows 8.1 since similar case could be caused by wrong version of Windows PE.

Regards,

D. Wu

• Proposed as answer by Nicolas BONNETMVP, Moderator Tuesday, February 10, 2015 7:49 AM
• Marked as answer by Nicolas BONNETMVP, Moderator 14 hours 57 minutes ago

Hi wkingswt,

Thanks for your solution and we will mark it as an anwser so everyone who has similar issue could see it.

Regards

D, Wu

• Edited by Lany ZhangMicrosoft employee, Moderator Thursday, February 12, 2015 7:48 AM update