When you’re imaging/PXE-booting in SCCM, I think the “0xC0000001” error is one of the strangest errors to troubleshoot, because the source of the error is related to some problem/conflict between TFTP and the network adapter of the machine you’re imaging — but then sometimes it has to do with the network adapter of your distribution point.
I have encountered multiple solutions to this problem, and here are some of them from other blogs:
- Error appears when imaging multiple systems at the same time.
Solution: Update send and receive buffers.
- Error appears on different types of hardware
Solution: Update the registry key of “RamDiskTFTPBlockSize” to a lower value
- Some admins go as far as just reinstalling WDS
- Windows Updates breaking PXE. Per a colleague, KB4489881 is known to cause problems, but I have heard reports that even the fix to KB4489881, KB4503276, is causing problems.
Solution: Uninstall the updates.
There are others.
However for me, I had the following scenario, and my solution turned out to be quite simple.
- Trying to image Pentium-based, 4 GB HP ProBook x360 11 G1 EE laptops
- From a VMWare DP, the machines receive the boot image just fine.
- From a Hyper-V DP, ‘0xC0000001’ error occurs on these laptops.
- For the sake of curiosity, I did the three items above (change reg key, changed network adapter properties, and even reinstalled WDS). None of these worked.
- I reverted all those settings and put the DP back in a ‘vanilla’ state
I found this behavior to be really odd. Why would it download the boot image on one just fine, but not on the other? Perhaps the boot image needs network adapter?
Well, it turns out the solution for this model laptop was to add the network adapter driver* to the boot image. We generally don’t add network drivers to boot images unless necessary, which in this case it turned out it was.
And that was that. If you don’t know how to add drivers to the boot image, I’m not going to reinvent the wheel, but I will direct you to this website that has a decent how-to.
(Edit 20180710 – clarified the use of a driver)
(Edit 20190702 – Added Windows Updates as a potential cause).