


If you suddenly find your Windows 10 computer stuck on the “Preparing to configure” screen for quite a long time now after you run Windows Update, read on as you will be guided on how you can fix that issue in this post.
During an update process, there’s a lot of things that go on in the background which is why Windows Updates take quite a while before it finishes. It can be at 25%, 50%, or even 100% but the only message you’re going to see on your screen is the “Preparing to configure Windows, Don’t turn off your computer”. However, if you notice that the Windows Update is taking a longer time than it’s supposed to, the first option is to wait some more but if it’s still the same, then there’s definitely something wrong. This kind of issue occurs when Windows Update fails to configure in short correctly download and install the update. When this happens, it will revert all the changes which are why you were advised to wait for a couple of hours.
There are two possibilities why your computer is stuck on the “Preparing to configure Windows, Don’t turn off your computer” screen. The first one is that the Windows 10 operating system is installing any updates. The second one is when the user profile takes time to load or encounters an error. There are several options you can try to fix the problem. You can try running System Restore or boot your computer in Safe Mode or repair the corrupted profile via Registry Editor. You might also want to try using installation media to boot and repair your computer if the other options didn’t work.
Note: If you can’t boot into the desktop of your computer, you can run System Restore in the Advanced Startup Options by following these steps:
You can try to tap the F8 key if you have it enabled in your Windows 10 computer, as you start your system to boot into Safe Mode. Once your computer is in Safe Mode, you can access the Start Menu and the Mouse and Keyboard. Aside from that, you can also access your files and other built-in tools in Windows such as Command Prompt, PowerShell, Computer Manager, Device Manager, Event Log Viewer, and many more. On the other hand, if you haven’t enabled the F8 key, you can just go to the Advanced Startup options to boot your computer into Safe Mode. Once you’re there, select Troubleshoot > Advanced Options > Startup Settings > Restart > Tap the number 4 key. After that, your computer will restart in Safe Mode. If you want to reboot into Safe Mode with Networking instead, you can tap the number 5 key and for Safe Mode with Command Prompt, tap the number 6 key. Once your computer is in Safe Mode, you can use any of the built-in tools to restore your computer or troubleshoot the problem that’s causing your computer to get stuck at the “Preparing to configure” screen.
In this third option, you can try to repair the corrupted profile using the Registry but before you proceed, take note that you can only try this if you can boot into your desktop and if you can, make sure to create a System Restore Point and then follow the steps below.
Another thing you can try to resolve the issue is to use the Windows installation bootable media so you can boot and repair the operating system. To use it, follow these steps:
“Windows Sandbox failed to start. Error 0x80070015. The device is not ready. Would you like to submit feedback about this issue?”If you are one of the users who encountered this kind of error in Windows Sandbox, then you’ve come to the right place as this post will help you sort this problem out. All you have to do is follow each one of the options provided below.
powercfg –lastwakeOnce you enter the command given above, it will show you the last device that woke your PC up. After that, you need to type in the next command:
powercfg –devicequery wake_armedAfter entering the command, it will show you a list of all the devices that could wake your PC up. The goal in running these commands is to understand the reason what’s really causing your PC to turn on and see the reason is on the hardware level or not. Here are a couple of options you can try if your Windows 10 PC turns on by itself.
Fooriza is a browser extension for Google Chrome. This extension offers users the latest trending news from the internet. These news widgets are usually sponsored content that the application displays based on your search history or visited links. While this extension is not that dangerous on its own, it usually comes bundled with other Potentially Unwanted Programs and Browser Hijackers that could pose a security risk.
When installed this extension changes your default search engine to yahoo. And while active you might see some additional ads injected into the search results. Due to its bundled nature with other PUP-s and the potential dangers that might come with them, several anti-virus scanners have detected this extension as a Browser Hijacker and are marked for removal.
Chedot is a Chromium-based Browser that replaces your default System Internet Browser. This browser offers users tools for downloading videos, faster browsing, and custom searches. From the publisher: A feature of our browser is a high speed on slow computers, high speed download on a poor internet, support resuming file download when connection is broken and the download in multiple threads, the ability to go on blocked websites and downloading videos from video sites.
While this may seem interesting and good at start, this browser has been marked as a Potentially Unwanted Program. It monitors user activity, collects web traffic data, and user information. While using Chedot you may see additional ads throughout your browsing sessions.
ST0P 0X00000024 (x00190203, 0x82700550, 0xc000012, 0x00000000)Due to this error, both Safe and Normal modes become inaccessible.