Hi TooFine,
What's the OS version of your Windows 10 image? 1809 or previous? Except the "OOBEREGION", have you got any other issues like "OOBESETTINGSMULTIPAGE" or "OOBELOCAL"? We found
many similar situations occurred during 1803/1809 installation or upgrade period. We collected several workarounds provided by guys who had used to fix their issue:
1. The problem comes from the OOBE program which needs elevation privilege to perform its modifications. Reboot in safe mode to downgrade UAC mode then reboot in standard mode to end 1803 installation and
then reset UAC mode to standard mode. You can check more details using following link:
https://answers.microsoft.com/en-us/windows/forum/all/windows-10-update/48722545-1ebc-43bf-9175-d0ab956d343b .
2. A complete reinstall from an ISO image on USB.
3. When you come to region selection screen, press SHIFT + F10 to open Command Prompt and enter following command: %windir%\System32\Sysprep\sysprep.exe /oobe /reboot. For this sysprep command, were you
running at the region selection screen? We also found someone fixed his issue using this, you can check more details using following link:
https://www.tenforums.com/windows-insider/118225-insider-isos-cant-get-past-oobe-stage.html .
4. There are some blocks for Windows 10 1809: Microsoft halts update if you use flawed Intel drivers. It affects the AMD Radeon HD 2000 or HD 4000 series graphics cards. Are you using one of these? If so,
it's still pending for resolving, you'll need to wait for updates. You can check more details using following link:
https://forums.windowscentral.com/windows-10/482203-cant-install-1809-clean-update.html .
5. If you want, maybe you can try to skip the OOBE phase using an Answer File, using this link for more details of Answer File:
https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-8.1-and-8/hh825121(v=win.10)
Note: these are 3rd party links, we don't have any warranties on these websites. It's just for your convenience.
If above workarounds are all not working, what’s unfortunately, then we may need to collect some related log files for further analyze. Please collect logs under below paths for our reference. \Windows\Panther\UnattendGC\setup*.log
\Winodws\Logs\CBS
\Windows\inf\setupapi.*.log
Since you can’t boot into the system, you could boot into windows recovery mode(using recovery media), then copy out the log file. Then upload them to a network drive and share the link here. Thanks for your
cooperation!
If any other questions, please feel free to post back.
Best regards,
Zoe Mo
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com.
