SJ98 Posted June 10, 2025 Posted June 10, 2025 As the title suggests, we're using SSCM to deploy our image to machines, and we're constantly running into the 0xc0000001 error screen after the deployment fails to download the WIM file. We've tried looking into the TFTP Block/Window size on the SCCM server and modifying the registry key on the server, but this has not made any difference, and we are still met with the same error. We're on SCCM version 2409. Does anyone know what the issue may be? We've not made any changes to our firewall recently either.
Passat1983ICTech Posted June 10, 2025 Posted June 10, 2025 dose your pxe boot work on this as the error message points to this
SJ98 Posted June 10, 2025 Author Posted June 10, 2025 Yes, it should do. We've got a number of the same model that have all carried out images fine in the past. This issue has been going on for a few weeks, but we have been just about getting by with it.
SJ98 Posted June 10, 2025 Author Posted June 10, 2025 Dell Vostro 3400. We have also had this happen on HP 255 G7
Passat1983ICTech Posted June 10, 2025 Posted June 10, 2025 Hello have you check your bios setting for drive it may not like raid try may change this on the dell and the HP
CHiLL Posted June 10, 2025 Posted June 10, 2025 Did you restart WDS after amending the TFTP block/window size?
SJ98 Posted June 30, 2025 Author Posted June 30, 2025 Hello, I did change the TFTP block/window size, restarted the service and the VM. The actual downloading of the WIM is quicker, but it sometimes still errors out? Definitely more successful now than it used to be
Fazza Posted July 1, 2025 Posted July 1, 2025 Are you able to try a different NIC? I've seen SCCM play up like this on some old Dells one of our Schools had and we had to initially PXE boot from the built-in NIC and then when Windows PE had loaded (and you get to choose which Image you want to deploy) was then connected a USB NIC and moved the Ethernet cable from the built-in one to the USB one. Only gotcha we had was making sure the USB NIC driver was included in the boot wim file.
ThomL Posted July 1, 2025 Posted July 1, 2025 Anything interesting in the client/server task sequence/PXE logs?
SJ98 Posted July 1, 2025 Author Posted July 1, 2025 24 minutes ago, Fazza said: Are you able to try a different NIC? I've seen SCCM play up like this on some old Dells one of our Schools had and we had to initially PXE boot from the built-in NIC and then when Windows PE had loaded (and you get to choose which Image you want to deploy) was then connected a USB NIC and moved the Ethernet cable from the built-in one to the USB one. Only gotcha we had was making sure the USB NIC driver was included in the boot wim file. We do it only from the built-in NIC. We don't have USB NICs to spare, we have one which gets lost often because we only use it for machines that don't have an ethernet port.
Fazza Posted July 1, 2025 Posted July 1, 2025 1 hour ago, SJ98 said: We do it only from the built-in NIC. We don't have USB NICs to spare, we have one which gets lost often because we only use it for machines that don't have an ethernet port. Have you tried using the USB one for fault-finding purposes, if the issue goes away then it's something to do with the onboard NIC? If the issue doesn't go away on the computer(s) you're having issues with then it's something else causing the issue.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now