Known Issues
In brief
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.
What Intune admins need to know
Users may briefly see OOBE pages configured to be skipped, or the device may not be renamed immediately after reset.
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: Information regarding known issues that might occur during a Windows Autopilot device preparation deployment.
ms.date: 2026-09-14T00:11-18T00:00:00.0000000Z
ai-usage: ai-assisted
ms.custom: msecd-doc-authoring-1030
ms.collection:
- M365-modern-desktop ms.topic: troubleshooting
Known issues
OOBE experience settings for associated devices may not apply immediately after a reset
Date added: November 18, 2026
This issue affects associated devices after a reset. When the device reboots into the out-of-box experience (OOBE), users might advance through setup before organizational settings are downloaded and applied. For example, users might see OOBE pages that their organization configured to skip. The device might not be renamed as configured.
The device needs to complete Trusted Platform Module (TPM) attestation and local device association before it can retrieve the correct organizational policy. Retrieving the policy can take about a minute. During this time, settings that customize OOBE pages or rename the device might not yet be applied.
This issue will be resolved in a future OS release.
Device preparation deployments on Windows 365 devices time out after 60 minutes
Date added: November 10, 2025 Date updated: February 5, 2026
@@ -13,7 +13,9 @@ feedback_system: Standard permissioned-type: public uhfHeaderId: MSDocsHeader-Windows description: Information regarding known issues that might occur during a Windows Autopilot device preparation deployment.-ms.date: 2026-09-14T00:00:00.0000000Z+ms.date: 2026-11-18T00:00:00.0000000Z+ai-usage: ai-assisted+ms.custom: msecd-doc-authoring-1030 ms.collection: - M365-modern-desktop ms.topic: troubleshooting@@ -64,6 +66,16 @@ For more information on using RSS for notifications, see [How to use the docs](/
## Known issues
+### OOBE experience settings for associated devices may not apply immediately after a reset
+
+Date added: *November 18, 2026*
+
+This issue affects associated devices after a reset. When the device reboots into the out-of-box experience (OOBE), users might advance through setup before organizational settings are downloaded and applied. For example, users might see OOBE pages that their organization configured to skip. The device might not be renamed as configured.
+
+The device needs to complete Trusted Platform Module (TPM) attestation and local device association before it can retrieve the correct organizational policy. Retrieving the policy can take about a minute. During this time, settings that customize OOBE pages or rename the device might not yet be applied.
+
+This issue will be resolved in a future OS release.
+
### Device preparation deployments on Windows 365 devices time out after 60 minutes
Date added: *November 10, 2025* Date updated: *February 5, 2026*