Edit your WinPE Boot Image in the Configuration Manager console. Go to the Customization tab and check Enable command support (testing only) .
When this file cannot be pulled down, WinPE cannot proceed, resulting in an immediate reboot or a hard stop at the Task Sequence Welcome screen. Step 1: Isolate the Cause via SMSTS.log
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later.
Downloaded PXE variable file. Exit code 0. unable to download pxe variable file. exit code 14 sccm
He pulled up the SMSPXE.log on the distribution point. Scrolled past the usual noise— Client lookup reply: , Found optional policy , No boot action for device . Then, buried in the noise:
During a PXE boot, the client logs into WinPE and attempts to communicate with the Management Point (MP) to download the variables.dat file. This file contains critical configuration data specific to the collection, computer, and task sequence deployment.
When faced with Exit Code 14, do not guess. Read the logs. Edit your WinPE Boot Image in the Configuration
The GUID looked wrong. He double-checked the MAC address in the database. Different GUID. Not wrong— old . The device had been imported into SCCM twice. Two GUIDs, one MAC. The PXE request was coming in on the stale GUID, and the MP was looking for a variable file that didn’t exist under that key.
: The network switch port is performing loop checks, causing a delay that makes WinPE time out before receiving an IP address. Network/Routing Misconfiguration : Incorrect IP Helpers
An translates directly to "The device is not ready" or a communication timeout. In the context of SCCM, it means WinPE cannot contact the Management Point to pull down this critical configuration file. Root Causes of Exit Code 14 Step 1: Isolate the Cause via SMSTS
: If the client and the Distribution Point (DP) or MP are on different subnets, improperly configured IP helpers can prevent the client from finding the necessary resources after the initial boot.
The error (often followed by 0x8004016c ) indicates that a network interruption occurred immediately after the boot image loaded . This prevents the client from downloading the environment variables ( .dat file) required to start the Task Sequence wizard. Immediate Troubleshooting Steps Verify Network Connectivity (F8 Prompt) :
Suggests the file isn't where the MP expects it to be. 0x80070002: The system cannot find the file specified. 6. Network Access Account (NAA) or PKI Certificates
Look for . If it is set to a high number (like 16384 or 8192), lower it to 4096 or 2048 to test stability.
SMSPXE.log showed the MP generating the policy successfully, but the client never received it. Network traces revealed that an intermediate switch had HTTP Intercept enabled (a feature for web filtering). This switch was intercepting the client's HTTP GET request for variables.dat and returning a cached "404 Not Found" page intended for a different web server.