Joe13 Posted February 4, 2020 Report post Posted February 4, 2020 Hi gents. I'm pulling my hair out, whole of last week and this week I'm using OSD to deploy PC's for a new contract. Few hours ago all stopped working, any PC or laptop, intel, hp, lenovo. All fail with this error. Nothing on my environment changed. Some research takes me to the March 2019 CU update. It is not installed on my server. Both these registry keys were set back to default with no difference on the outcome. RamDiskTFTPBlockSize RamDiskTFTPWindowSize I also tried this suggestion: https://andys-tech.blog/2019/03/wds-required-device-isnt-connected-or-cant-be-accessed/ The error reads: Status: 0xc0000001 Info: A required device isn't connected or can't be accessed. Quote Share this post Link to post Share on other sites More sharing options...
Joe13 Posted February 19, 2020 Report post Posted February 19, 2020 Anyone? Quote Share this post Link to post Share on other sites More sharing options...
anyweb Posted February 19, 2020 Report post Posted February 19, 2020 did you try to restart the wds service and redist your boot images after doing the change ? Quote Share this post Link to post Share on other sites More sharing options...
Joe13 Posted February 20, 2020 Report post Posted February 20, 2020 I think I solved it. I made the RamDiskTFTPBlockSize lower than normal... Quote Share this post Link to post Share on other sites More sharing options...
Joe13 Posted February 26, 2020 Report post Posted February 26, 2020 Back to square one. It now takes 30minutes just to download the .wim What logs files and events can I refer to for troubleshooting? I cleared required PXE deployments. I updated the distribution points, default boot images and mine. SMSPXE.txt Quote Share this post Link to post Share on other sites More sharing options...
TrialandError Posted February 26, 2020 Report post Posted February 26, 2020 What is your tftp window size set too? Try setting it to 1 if it's not already. Quote Share this post Link to post Share on other sites More sharing options...
Joe13 Posted February 27, 2020 Report post Posted February 27, 2020 I fixed it for now by changing my network adaptor on VMWare from VMXNET3 to E1000E. It now owrks without issues. Quote Share this post Link to post Share on other sites More sharing options...
radish Posted March 1, 2020 Report post Posted March 1, 2020 I remember this error was some system patches released in March or May last year, updated and then caused this error. Later, a fix patch released by Microsoft around October resolved the sccm pxe boot error. In addition, does the boot integrate the VMXNET3 network card driver? The TFTP accelerated startup mode is modified to try to adjust parameters according to the respective corporate network environment. Quote Share this post Link to post Share on other sites More sharing options...
