SCCM no longer PXE boots after ADK update

[Sheridan]

I decided to update our SCCM 2503 to the latest supported Dec 2024 ADK. This all seemed to go OK and rebooted and updated the Boot images from the ADK images

 

Now nothing will PXE boot - a PC will get the pxe boot screen and try to load the image and just seems to reboot 

 

All I can see in the SMSPXE.log if a few timeout messages:

 

recvfrom() returned 0x8007274c. Waiting for 775.

recvfrom() returned 0x8007274c. Waiting for 775.

recvfrom() returned 0x8007274c. Waiting for 775.

recvfrom() returned 0x8007274c. Waiting for 775.

recvfrom() returned 0x8007274c. Waiting for 775.

timed-out.

 

Not sure if this is a false flag but it was all working 100% before I did this. Before I rollback to the snapshot has anyone seen this before? Its not a network issue as I'm using the same ports/cables etc that were used before the ADK update!

[Sheridan]

Might have inadvertently fixed this 🙂

 

Rebooted again, rebuilt the PXE image again and now working. Maybe the new ADK wasn't loaded correctly into SCCM when I did the first rebuild

[kfx017]

I had this exact same issue but only on Hyper-V Gen2 VMs. The fix for me was to edit the VM's Network Adapter and enable "Device naming" under the Advanced features. The hint that lead me to that setting was the error "PXE-E09" with description "Could not allocate I/O buffers". My guess is that the memory allocation needs the name of the network adapter in order to do its job and Hyper-V must be given permission to provide that. 

Edited December 11, 2025 by kfx017

[Sheridan]

9 minutes ago, kfx017 said:

I had this exact same issue but only on Hyper-V Gen2 VMs. The fix for me was to edit the VM's Network Adapter and enable "Device naming" under the Advanced features. The hint that lead me to that setting was the error "PXE-E09" with description "Could not allocate I/O buffers". My guess is that the memory allocation needs the name of the network adapter in order to do its job and Hyper-V must be given permission to provide that. 

Hmm interesting - my SCCM VM is currently VMWare but will be migrating to Hyper-V next year so worth checking this when I do the move