Share via

Windows Autopilot deployment failing with OOBE region selection loop on specialized corporate hardware

David Huber 20 Reputation points
2026-06-09T14:20:17.9766667+00:00

During Windows Autopilot provisioning of our rugged field workstation inventory, newly unboxed OEM systems connect online without issue but do not complete the Autopilot process. The devices continuously loop back to the OOBE regional selection screen, preventing the deployment of our custom corporate branding and login experience.

Windows for business | Windows 365 Enterprise
0 comments

Answer accepted by question author

Domic Vo 23,805 Reputation points Independent Advisor
2026-06-09T14:58:18.1933333+00:00

Hi David Huber,

The OOBE loop during Windows Autopilot deployment typically occurs when a device fails to retrieve its assigned configuration profile, either due to a missing hardware hash registration or network-level blocks. To resolve this, ensure the device's hardware hash is correctly registered in the Microsoft Intune admin center and that the device belongs to an Azure AD dynamic group mapped to an active Autopilot deployment profile. Additionally, verify network connectivity to essential Microsoft endpoints during the setup phase and investigate the C:\Windows\Panther\unattendGC\setupact.log file for specific error details if the issue persists.

Domic V.

Was this answer helpful?

1 person found this answer helpful.

0 additional answers

Sort by: Most helpful
Most helpful Newest Oldest

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.