Imaging Windows 11 "Why did my PC restart?" Loop
My Kace SDA is 9.0.146, my Win ADK is the latest
version for WIn 11 22H2, New Unattend and SysPrep created in SDA, Latest KBE
drivers A28. The image starts normally with no issues or errors, downloads and
installs computer drivers (Dell AIO 7400) downloads post tasks, reboots, then
reboots 2-3 more times, and comes up with that blue screen message. "Why
did my PC restart? There's a problem that's keeping us from getting your PC
ready to use, but we think an update will help get things working again" I
am at a loss and am hoping someone can point me in the right direction. I have
given it a wi-fi connection but it still comes back to that msg. Any guidance
is greatly appreciated.
I've had similar results when deploying images from SCCM. Possible fixes included:
* Delete all possible names for the device from AD and from SCCM, change from domain to Workgroup without rebooting, rejoin AD, wait for SCCM to pick up the name, redeploy the SCCM client, start the SCCM image process.
* In BIOS remove all EUFI boot points, boot to Zen boot disk (We're moving from Zen to SCCM), remove all occupied partitions, redeploy previous Zen base image, wait for SCCM to pick up the system name, deploy the SCCM client, start the SCCM image process.
* Boot to the Zen Boot disk, zero out the hard drive (dd if=/dev/zero of=/dev/sda (or of=/dev/nvme depending on drive type ) bs=2048M status=progress && sync && echo done! After the drive is zeroed out, redeploy Zen Base image, wait for SCCM to pick up the system name, deploy the SCCM client, start the SCCM image process.
I expect that a hand install of the OS to the problem unit could have been a viable substitute for "redeploy Zen Base image".
Zeroing out the hard drive in the manner listed above can also be done from a Linux Live CD/DVD/USB boot, or from products like Boot & Nuke or DBAN. It also zeros the image safe area so the part of hard storage where the computer name and dns hostname are stored will be wiped out so unless they're added back prior to imaging, after imaging the system will have a default windows name of some sort.
There are two ways to tackle this:
1- For Glory:
You will need to pull Windows Logs via KBE, and analyze them to see why this sort of BSOD is happening. This will take time unless you are experienced with Windows Logs debugging.
2- For Simplicity:
-Make sure your Image was captured from a VM not from a physical device. (VMs produce stable images).
-Make sure the OS that was Sysprepped, was installed from an ISO using whatever build you want to deploy. (It is considered Bad practice to Sysprep upgraded Windows versions, if you check your Volume License Portal, MS Offers ISOs patched and updated up to last mont).
-BSODs are normally tied to drivers, you could try to deploy the same image again, and uncheck the box to Use Driver Feeds from your Image before testing. If that works check if the drivers supplied by case, are the latest ones from the ENTEPRISE DELL site (not from support.dell.com).
Thank you for your reply, I have never done that - do you have the steps to remove the UEFI boot points?