Deployed image boots up with boot/bcd error and BSOD
-
@Quazz yes it was sysprepped with generalize option
-
@holydonut I’d take a look at the BIOS then and take a look at the boot settings, there’s likely something going on there that’s causing this.
-
@george1421 I’m guessing legacy boot is default for network boot?
http://imgur.com/a/eJa4v -
@holydonut You often have to explicitedly enable the UEFI network stack before you can use it as a boot option.
Try disabling UEFI and see if that works.
-
@Quazz no luck
-
How about, removing drivers from the picture entirely first?
I’m assuming you’re using something like the drivers through postdownloadscripts? Sorry I’m not reading too far through this all.
If you have just the base image, no drivers, and test, do things appear to work smoothly? This will tell you immediately if it’s a driver issue or not.
Is it also possible the image as it was uploaded was uploaded improperly? (I don’t know if you already tried recapturing).
-
@Tom-Elliott I think with this specific system the issue is one of two.
- The hardware is configured for raid mode where ahci may be more appropriate.
- The Win7 image doesn’t contain the hardware driver for the disk controller.
The bluescreen stop message basically means that when windows switches to protected mode it can’t access the storage disk.
Does this HP computer have an nvme disk or m.2 disk installed?
-
@george1421 I removed the drivers from the image for the model, changed to ahci and still same error. Yes it has a NVME disk installed
-
@holydonut Ah nvme that might explain it. Did you add in the 2 hot fixes that are required for Win7 to see a nvme disk?
-
@george1421 thanks George, after installing the hot fixes I was able to deploy the image. Thanks for your help everyone!