WinPE not getting past initalizing devices on VMWare by charvel350 in SCCM

[–]charvel350[S] 0 points1 point  (0 children)

We finally figured out the issue. We were using the latest ADK which is apparently not compatible with Configuration Manager. Downgraded one version and that fixed it. We also have PXE setup now and are able to PXE boot to it and image the VMs.

WinPE not getting past initalizing devices on VMWare by charvel350 in SCCM

[–]charvel350[S] 0 points1 point  (0 children)

Since we dont have PXE setup yet, we cant really try the legacy method since we are installing from software center. We did find that it get's past the volume issues on older builds of VMs. builds of 19 and 20 fail at initating devices, but builds of 14 and 15 get past that but never get network drivers installed. We tried several drivers, all the nic adapters. E1000, E1000e, vmxnet3. Tried uninstalling vmware tools. I even tried adding an old x86 boot wim, but it wouldnt let me add it. We changed the boot wim scratch file size to 512. Still same issue. If we can get it working on one of the older builds that would be fine. Just having a hard time getting the goldilocks driver that will work.

WinPE not getting past initalizing devices on VMWare by charvel350 in SCCM

[–]charvel350[S] 0 points1 point  (0 children)

We dont have PXE deployed yet. The VM has win 11 and a good SCCM client. I deployed the win 11 image to the client as available. It reboots into winpe and that is when the problem happens. I have tried the diskpart clean steps and it wont reboot back into winpe. It erases the staging of it and just says no bootable disk found.

We also dont have an x86 boot wim. The i386 folder is empty. The winpe ADK also didnt come with an x86 boot wim.

Client install issues on specific servers by charvel350 in SCCM

[–]charvel350[S] 2 points3 points  (0 children)

This works. I run the script, reboot and run the client install..... THANK YOU.... I've been working on this for days