PENDING PXE Boot Failing - PxeGetPxeData failed with 0x80004005

[Jordan B]

Hi, Recently, PXE boot has stopped working. It gets to "Preparing Network Connections: then reboots.



The WDS Events has this recorded:

The Following Client failed TFTP Download:
Client IP: 10.0.10.159
Filename: \SMSBoot\boot.sdi
ErrorCode: 1460
File Size: 3170304
Client Port: 4251
Server Port: 59449
Variable Window: false

SMSTS log shows this:

"Failed to download pxe variable file. Code (0x0000000E)
"PxeGetPxeData failed with 0x80004005"



I've tried restarting the service/server, with no luck. We are running Windows Server 2012 R2. This was working fine then it suddenly broke.

 

[Jordan B]

https://1drv.ms/u/s!Agngd8kPWLRjiilaZSG3FgWBpwGf

Link to SMSTS.LOG

 

[toledotown]

Did you ever resolve this issue? We just updated to 1702 and are having the same problem. The crux of it is that our test environment did not have this issue lol. We have confirmed a valid IP is leased, it can ping all SCCM servers, and there is a disk present.

 

[Prajwal Desai]

Did you ever resolve this issue? We just updated to 1702 and are having the same problem. The crux of it is that our test environment did not have this issue lol. We have confirmed a valid IP is leased, it can ping all SCCM servers, and there is a disk present.

Did you take a back up before you updated to 1702 ?. Revert back to previous setup to see if it works fine.

 

[Prajwal Desai]

Hi, Recently, PXE boot has stopped working. It gets to "Preparing Network Connections: then reboots.



The WDS Events has this recorded:

The Following Client failed TFTP Download:
Client IP: 10.0.10.159
Filename: \SMSBoot\boot.sdi
ErrorCode: 1460
File Size: 3170304
Client Port: 4251
Server Port: 59449
Variable Window: false

SMSTS log shows this:

"Failed to download pxe variable file. Code (0x0000000E)
"PxeGetPxeData failed with 0x80004005"



I've tried restarting the service/server, with no luck. We are running Windows Server 2012 R2. This was working fine then it suddenly broke.

May i know the installed SCCM version ?. From the log file i see multiple issues, can you confirm if the network drivers present ?.

X:\sms\data\WinPE does not exist. TSBootShell 8/15/2017 3:50:31 PM 640 (0x0280)
X:\_SmsTsWinPE\WinPE does not exist. TSBootShell 8/15/2017 3:50:31 PM 640 (0x0280)
Processing volume C:\ TSBootShell 8/15/2017 3:50:34 PM 640 (0x0280)
Unable to find a Windows system root at C:\ TSBootShell 8/15/2017 3:50:34 PM 640 (0x0280)
Processing volume D:\ TSBootShell 8/15/2017 3:50:34 PM 640 (0x0280)
Volume D:\ is not using a supported file system. TSBootShell 8/15/2017 3:50:34 PM 640 (0x0280)
Processing volume E:\ TSBootShell 8/15/2017 3:50:34 PM 640 (0x0280)
Unable to find a Windows system root at E:\ TSBootShell 8/15/2017 3:50:34 PM 640 (0x0280)
Processing volume X:\ TSBootShell 8/15/2017 3:50:34 PM 640 (0x0280)
Volume X:\ is not a local hard drive. TSBootShell 8/15/2017 3:50:34 PM 640 (0x0280)

 

[toledotown]

Did you take a back up before you updated to 1702 ?. Revert back to previous setup to see if it works fine.

No backup, but I resolved the issue. I had windows 10 ADK 1709 installed in production but 1703 is the highest supported. After removing, installing the right version, starting over with the boot.wim files, and distributing them the problem was resolved.

Thanks for your reply.