Press "Enter" to skip to content

WDS Boot PXE: Fix the 0xc0000001 Error



When you try to start a computer in PXE from a WDS server, the following error is displayed when loading the image:

Windows failed to start. A recent hardware or software change might be the cause. To fix the problem:
1. Insert your Windows installation disc and restart your computer.
2. Choose your language settings, and then click “Next.”
3. Click “Repair your computer.”
if you do not have this disc, contact your system administrator or computer manufacturer for assistance.
Status: 0xc000000l
Info: A required device isn’t connected or can’t be accessed

pxe error wds

The problem appears after you install the March 2019 updates (KB4489883 or KB4489891).


The maximum block size of the TFTP server must be changed.

1. Open the WDS console, right click on the server 1 then click on Properties 2 .

2. Go to the TFTP 1 tab, block size enter 4096 2 . Uncheck Enable Variable Window Expansion 3 and click Apply 4 and OK 5 .
TFTP config

3. Restart the WDS service. Right click on server 1 / All tasks 2 / Restart 3 .
Restart service


Related Posts

MDT: enable monitoring
Presentation In MDT, it is possible to activate the monitoring, which makes it possible to follow the deployment of the stations and to have a progress report from the console. The state of the deployments is kept for 3 days. Activation of the monito

WDS: installation and configuration
In this tutorial, we will see how in place Windows Deployment Services (WDS). WDS is role included with Windows Server that allows to put a TFTP server for PXE boot and installation of images. With these services you can deploy computers (physical or

MDT: Running a PowerShell Script During a Deployment
In this article, I explain how to run a PowerShell script (ps1 file) during a deployment with MDT. Copy the ps1 << 1 >> file to the Scripts folder in the folder. Open the properties of the sequence and add a task of type Run Command Line

  1. km

    Worked! wds on server 2012 r2


  2. Gaz

    This looks specific to windows 2012. I have this issue on 2016 and this fix hasnt worked. I do not have these updates installed.

    • Romain

      Hello, have you tried with a larger value?

  3. Frank

    You saved my day!

  4. Daniel Ruiz

    Worked for me! Thanks.
    I think that was a windows update problem because 1 moth ago worked correctly.

  5. vinod

    It fixed the issue on my server. Thanks for sharing!

  6. Ben Guptill

    After years of running MDT with no problem suddenly my PXE boots started failing with the error shown in your Symptom section. I was out of ideas until I ran across this. It fixed the issue on 2 different servers I was having the issue on. Thanks for sharing!

    • Romain

      I found myself in the same situation, years of use without problems. I think the problem comes from a recently installed update

      • Sjoerd

        I can confirm, the latest Windows update was the problem for me also. After uninstalling the update, the error was gone and MDT started as it used to.

Leave a Reply

Your email address will not be published. Required fields are marked *

It looks like you're using an adblocker.
We use ads to keep our content free. Please support us by turning off your adblocker.