Known Issues
Doc updateThe documentation now notes that associated devices may enter OOBE before organizational settings are downloaded and applied. TPM attestation and local device association can delay policy retrieval by about a minute.
Windows Autopilot’s Known Issues documentation now covers two enrollment behaviors: TPM attestation and local device association can delay policy retrieval by about a minute, while completed pre-provisioning and ESP can still produce Failure reports with 0–1 second durations when a nonblocking Win32 app error is treated as ESP-blocking.
The Windows Autopilot Known Issues page now notes that associated devices may enter OOBE before organizational settings are downloaded and applied. TPM attestation and local device association can delay policy retrieval by about a minute, causing briefly visible OOBE pages that should be skipped and delayed device renaming after reset.
The documentation now describes reports showing Failure with a 0–1 second duration even after pre-provisioning and ESP complete successfully. The device remains enrolled and functional; a nonblocking Win32 app error is being treated as ESP-blocking. Administrators should verify enrollment status and app reporting before classifying these reports as actual enrollment failures.
This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.
The documentation now notes that associated devices may enter OOBE before organizational settings are downloaded and applied. TPM attestation and local device association can delay policy retrieval by about a minute.
The documentation now describes reports showing Failure and a 0–1 second duration after pre-provisioning and ESP complete successfully. The device remains enrolled and functional; the issue is caused by a nonblocking Win32 app error being treated as ESP-blocking.