Known Issues
In brief
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.
What Intune admins need to know
Administrators should verify enrollment status and app reporting before treating these deployment reports as actual enrollment failures.
This summary was assembled from the tracked documentation change. Verify important details in the full Microsoft Learn article.
Documentation change
The comparison below shows only the changed extract. Use the full-page view for complete context.
permissioned-type: public
uhfHeaderId: MSDocsHeader-Windows
description: Be informed about known issues that might occur during Windows Autopilot deployment.
ms.date: 2026-09-08T00:11-16T00:00:00.0000000Z
ms.collection:
- M365-modern-desktop ms.topic: troubleshooting
Known issues
Windows Autopilot deployment report shows failure after successful pre-provisioning
Date added: November 16, 2026
After Windows Autopilot pre-provisioning and the device enrollment status page (ESP) complete successfully, the deployment report might incorrectly show Failure. The report shows a deployment duration of 0-1 seconds. This issue appears under Windows > Monitor > Windows Autopilot deployment status in the Microsoft Intune admin center.
This issue occurs when the report treats an installation error from a nonblocking, best-effort Win32 app as an ESP-blocking failure. It affects deployment reporting, not enrollment. The device is enrolled and works normally.
The report should show Success and the actual deployment duration. The individual app's installation error should still appear in app reporting.
Pre-provisioning fails for Microsoft Entra hybrid join when policy conflict resolution requires domain controller connectivity
Date added: September 1, 2026
@@ -13,7 +13,7 @@ feedback_system: Standard permissioned-type: public uhfHeaderId: MSDocsHeader-Windows description: Be informed about known issues that might occur during Windows Autopilot deployment.-ms.date: 2026-09-08T00:00:00.0000000Z+ms.date: 2026-11-16T00:00:00.0000000Z ms.collection: - M365-modern-desktop ms.topic: troubleshooting@@ -64,6 +64,16 @@ For issues with Windows Autopilot with Co-management, see [Windows Autopilot wit
## Known issues
+### Windows Autopilot deployment report shows failure after successful pre-provisioning
+
+Date added: *November 16, 2026*
+
+After Windows Autopilot pre-provisioning and the device enrollment status page (ESP) complete successfully, the deployment report might incorrectly show **Failure**. The report shows a deployment duration of **0-1 seconds**. This issue appears under **Windows > Monitor > Windows Autopilot deployment status** in the Microsoft Intune admin center.
+
+This issue occurs when the report treats an installation error from a nonblocking, best-effort Win32 app as an ESP-blocking failure. It affects deployment reporting, not enrollment. The device is enrolled and works normally.
+
+The report should show **Success** and the actual deployment duration. The individual app's installation error should still appear in app reporting.
+
### Pre-provisioning fails for Microsoft Entra hybrid join when policy conflict resolution requires domain controller connectivity
Date added: *September 1, 2026*