Are you experiencing an OOBE error in Windows 10 where you’re being launched into the Welcome Screen? When upgrading or reinstalling Windows 10, in some cases you may be launched into the welcome screen rather than the OOBE. This unfortunately is a common bug within Windows 10 and is to be fixed in Windows 11.
Thankfully, here at TechSplat, we focus on finding quick and easy solutions for you and your devices. Today, we have found a quick fix, that should only take 30-60 seconds to fix! Read on below for more information on how to fix this issue!
What causes the Windows 10 to start on the welcome screen instead of the OOBE Issue
If you turn on a new Windows 10 device for the first time and the device starts on the welcome screen instead of OOBE, it’s because the dwm.exe process, a critical process within Windows 10 – is not responding or starting.
In most cases, this can be resolved by simply restarting the device in question, but may sometimes need a little more diagnosing to resolve the issue.
Here’s how to fix the Windows 10 problem, starting with the welcome screen instead of the OOBE
If you are encountering the Windows 10 issue, then below is an easy fix that has been known to fix many users issues, including other Windows 10 boot sequence issues. Complete the following steps to get help instantly!
- Press and hold the Shift key on your device.
- Tap or press the power button in the lower right corner of the welcome screen.
- When prompted, click on the Restart option.
- If that doesn’t work, press and hold the power button for 30 seconds to completely reboot the computer.
Once you complete this, you should now be at the OOBE that you expect. Let us know if this isn’t the case, as your issue may reside within the hardware of your device, or the OS install!
All in all, when Windows 10 boots into the welcome screen instead of the Out of the Box Experience, this can be quite frustrating. Hopefully, this guide has helped you restart and do a power reset on your device to allow you to boot into the OOBE from the start. If this still hasn’t helped, maybe look to speak to Microsoft Support about this issue, or let us know down in the comments!