Home

WDS PXE boot fail with 0xc000023

%3CLINGO-SUB%20id%3D%22lingo-sub-282809%22%20slang%3D%22en-US%22%3EWDS%20PXE%20boot%20fail%20with%200xc000023%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-282809%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20set%20up%20a%20WDS%20server%20based%20on%20Windows%202016%20to%20deploy%20Windows%2010%20on%20UEFI%20devices.%20(we%20used%20to%20have%20a%20Windows%202008%20R2%20which%20worked%20well%20with%20BIOS%20devices).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20test%20the%20PXE%20boot%20it%20fails%2C%20on%20screen%20it%20says%3A%3C%2FP%3E%3CP%3EWindows%20Deployment%20Services%20(Server%20IP%3A%200.0.0.0)%3C%2FP%3E%3CP%3EWindows%20Deployment%20Services%20encountered%20an%20error%3A%3C%2FP%3E%3CP%3EError%20Code%200xc0000023%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDuring%20the%20boot%20it%20seems%20fine%3A%3C%2FP%3E%3CP%3EStart%20PXE%20over%20IPv4%3C%2FP%3E%3CP%3EStation%20IP%20address%20is%2010.x.x.x%20(I%20checked%20the%20IP%20is%20correct%20in%20DHCP)%3C%2FP%3E%3CP%3EServer%20IP%20address%20is%2010.x.x.x.%20(The%20correct%20IP%20for%20the%20WDS%20server)%3C%2FP%3E%3CP%3ENBP%20filename%20is%20boot%5CX64%5Cwdsmgfw.efi%3C%2FP%3E%3CP%3ENBP%20filesize%20is%201054616%20Bytes%3C%2FP%3E%3CP%3EDownloading%20NBP%20file...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E2%20seconds%20after%20this%20the%20screen%20changes%20to%20the%20above%20error%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20the%20WDS%20server%202%20events%20are%20created%20in%20operational%20log%2C%20nothing%20in%20Admin%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEvent%20ID%3A%2057348%3C%2FP%3E%3CP%3E%3CEM%3EA%20Non-Shared%20buffer%20was%20created%20for%20reading%20file%20D%3A%5CRemoteInstall%5Cboot%5CX64%5Cwdsmgfw.efi.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEvent%20ID%3A%204099%3C%2FP%3E%3CP%3E%3CEM%3EThe%20Following%20Client%20started%20TFTP%20Download%3A%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3EClient%20IP%3A%2010.218.115.125%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EFilename%3A%20boot%5CX64%5Cwdsmgfw.efi%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EFile%20Size%3A%201054616%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EClient%20Port%3A%2053089%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EServer%20Port%3A%2062532%3C%2FEM%3E%3CBR%20%2F%3E%3CEM%3EVariable%20Window%3A%20false%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20application%20log%208%20events%20are%20logged%3A%3C%2FP%3E%3CP%3E7%20x%20Event%201305%20(information)%3C%2FP%3E%3CP%3E%3CEM%3ECombined%20BCD%20file%20x86%7B20DF25CC-2591-4A4F-B88B-918B818B1616%7D.bcd%20generated%20successfully%20for%20the%20x86%20architecture.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECombined%20BCD%20file%20x64%7BBDB1C413-856F-4DF8-BA1C-C694F9AFF9AE%7D.bcd%20generated%20successfully%20for%20the%20x64%20architecture.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECombined%20BCD%20file%20ia64%7BBE76E7F5-FBEE-407E-BADB-AFA29ED1FA38%7D.bcd%20generated%20successfully%20for%20the%20ia64%20architecture.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECombined%20BCD%20file%20x86x64%7BBBD1B0F0-2336-4B7B-B638-607605AB366B%7D.bcd%20generated%20successfully%20for%20the%20x86x64%20architecture.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECombined%20BCD%20file%20arm%7BE37A6027-55EC-4237-883C-2C171F83C31F%7D.bcd%20generated%20successfully%20for%20the%20arm%20architecture.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECombined%20BCD%20file%20x86uefi%7BA742BB71-6AC2-4AA9-8137-8845B2B87BD7%7D.bcd%20generated%20successfully%20for%20the%20x86uefi%20architecture.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CEM%3ECombined%20BCD%20file%20x64uefi%7B2707BF3A-1C82-4EF6-93B2-8D69BA02AD5F%7D.bcd%20generated%20successfully%20for%20the%20x64uefi%20architecture.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EEvent%201284%20(Error)%3A%3C%2FP%3E%3CP%3E%3CEM%3EAn%20error%20occurred%20while%20trying%20to%20create%20the%20directory%20for%20the%20architecture.%20%3C%2FEM%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CEM%3EError%20Information%3A%200x3%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20played%20around%20with%20TFTP%20max%20block%20size%20settings%20and%20the%20variable%20window%20extension%2C%20but%20it%20changes%20nothing.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20DHCP%20options%2066%20and%2067%20is%20used%2C%20and%20they%20must%20work%20as%20server%20IP%20and%20filename%20is%20correct.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20goggled%20the%20problem%2C%20but%20found%20no%20answers%20to%20my%20problem.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-282809%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EWindows%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-802781%22%20slang%3D%22en-US%22%3ERe%3A%20WDS%20PXE%20boot%20fail%20with%200xc000023%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-802781%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F238836%22%20target%3D%22_blank%22%3E%40Leif%20Mathiesen%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20news%3F%20Were%20you%20able%20to%20solve%20the%20problem%3F%20For%20days%20I%20have%20been%20searching%20for%20the%20cause%20of%20the%20described%20scenario.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Leif Mathiesen
Occasional Visitor

I have set up a WDS server based on Windows 2016 to deploy Windows 10 on UEFI devices. (we used to have a Windows 2008 R2 which worked well with BIOS devices).

 

When I test the PXE boot it fails, on screen it says:

Windows Deployment Services (Server IP: 0.0.0.0)

Windows Deployment Services encountered an error:

Error Code 0xc0000023

 

During the boot it seems fine:

Start PXE over IPv4

Station IP address is 10.x.x.x (I checked the IP is correct in DHCP)

Server IP address is 10.x.x.x. (The correct IP for the WDS server)

NBP filename is boot\X64\wdsmgfw.efi

NBP filesize is 1054616 Bytes

Downloading NBP file...

 

2 seconds after this the screen changes to the above error

 

On the WDS server 2 events are created in operational log, nothing in Admin:

 

Event ID: 57348

A Non-Shared buffer was created for reading file D:\RemoteInstall\boot\X64\wdsmgfw.efi.

 

Event ID: 4099

The Following Client started TFTP Download:

Client IP: 10.218.115.125
Filename: boot\X64\wdsmgfw.efi
File Size: 1054616
Client Port: 53089
Server Port: 62532
Variable Window: false

 

In the application log 8 events are logged:

7 x Event 1305 (information)

Combined BCD file x86{20DF25CC-2591-4A4F-B88B-918B818B1616}.bcd generated successfully for the x86 architecture.

Combined BCD file x64{BDB1C413-856F-4DF8-BA1C-C694F9AFF9AE}.bcd generated successfully for the x64 architecture.

Combined BCD file ia64{BE76E7F5-FBEE-407E-BADB-AFA29ED1FA38}.bcd generated successfully for the ia64 architecture.

Combined BCD file x86x64{BBD1B0F0-2336-4B7B-B638-607605AB366B}.bcd generated successfully for the x86x64 architecture.

Combined BCD file arm{E37A6027-55EC-4237-883C-2C171F83C31F}.bcd generated successfully for the arm architecture.

Combined BCD file x86uefi{A742BB71-6AC2-4AA9-8137-8845B2B87BD7}.bcd generated successfully for the x86uefi architecture.

Combined BCD file x64uefi{2707BF3A-1C82-4EF6-93B2-8D69BA02AD5F}.bcd generated successfully for the x64uefi architecture.

 

Event 1284 (Error):

An error occurred while trying to create the directory for the architecture.

Error Information: 0x3

 

I have played around with TFTP max block size settings and the variable window extension, but it changes nothing.

 

The DHCP options 66 and 67 is used, and they must work as server IP and filename is correct.

 

I goggled the problem, but found no answers to my problem.

1 Reply

@Leif Mathiesen 

Any news? Were you able to solve the problem? For days I have been searching for the cause of the described scenario.

Related Conversations
Extentions Synchronization
Deleted in Discussions on
3 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
36 Replies
flashing a white screen while open new tab
Deleted in Discussions on
14 Replies
Stable version of Edge insider browser
HotCakeX in Discussions on
35 Replies