Configuration Manager PXE boot fail after boot image update.

Question

This week we updated our Configuration Manager hierarchy to the version 2303. Everything went well.

After that, we updated our boot images, and PXE boot stop working worldwide.

We updated the ADK and the WinPE add-on on all our site servers, rebooted them all, and updated the boot images via "Update Distribution Point".

We also tried creating a new boot image.

The error we are getting is "0xC0000000F A required device isn't connected or can't be accessed."

All articles I find about this error points to the WDS TFTP frame config, but we are not using WDS, we are using the SCCM PXE responder.

On the distribution point SCCMPXE.log we are getting "TFTP: <ipaddress> fstat() failed."

On WireShark we get a fail read request for file "\EFI\Microsoft\Boot\boot.stl"

Any ideas?

Thanks!

Answer 1

Well, I hope this helps people in the future, because I found no documentation on it.

Turns out you have to set the Windows PE Scratch Space (MB)

After updating the boot image, it went back to 32MB. I sent it to 512, updated the image in the DPs and voila.

The config is at Boot image properties > Customization.

Hope it helps.

Answer 2

Hi,

Thanks very much for your feedback and sharing. We're glad that the issue is gone now. It's appreciated that you could click "Accept Answer" to the helpful reply, this will help other users to search for useful information more quickly. Here's a short summary for the problem.

Problem/Symptom:

PXE boot failed with the error "0xC0000000F A required device isn't connected or can't be accessed" after boot image update.

Solution/Workaround:

It was a problem about Windows PE Scratch Space (MB) at Boot image properties > Customization.

After updating the boot image, it went back to 32MB. Set it to 512MB, updated the image in the DPs.

Thanks again for your time. Have a nice day!

Best regards,

Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.

Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Answer 3

I was able to resolve this by going into Administration>Distribution Points and then right-clicking on my DP that my PXE Boot was enabled on and clicked on properties. From there I went to the PXE tab and unchecked the box labeled "Enable PXE support for clients." I then applied the changes and hit OK to close out of the properties window. I left this for ~15 Minutes while the DP uninstalled the Windows Deployment Service (This goes automatically after disabling PXE) then I re-enable PXE and waited around another 10 Minutes, ensured the Windows Deployment Service started within the "Services" applications and I was all good to go!