You can also disable the service via the standard services.msc snap-in interface if you prefer that. The reason you need to reenable App Readiness is that without it, the next steps will fail. Reboot again and allow the slow boot procedure to complete. If the problem is solved, next reverse the procedure by rerunning msconfig and rechecking the box next to App Readiness.Upon reboot, if the problem disappears, this is indeed your issue.Either wait out the rest of the boot procedure and then reboot your PC, or force a reboot by returning to Task Manger and running this task: shutdown -r -t 0.Click the Services tab, uncheck App Readiness, and click OK.During the hang at the black screen, press CTRL+SHIFT+ESC to bring up Task Manager.Lots of things can lead to hangs during the boot process, so before you proceed further, it’s a good idea to ensure that the App Readiness hang is actually what is afflicting you: If you experience this exact behavior, I have what is likely a permanent fix for you however, and best of all, it’s easy.įirst, determine if this particular problem applies to your machine. Disabling this service does correct the problem. This is the service which causes all of these headaches.Ī while back, people discovered that the singular service responsible for this behavior is the App Readiness service, which prepares user data the first time a user logs on following the installation or update of a Windows Store app. However, I’ve come to doubt that explanation, as the fix they provide in the relevant KB article has not yet once worked on any of my clients’ machines, and another, more foolproof fix has instead corrected the problem. Microsoft has indeed acknowledged this issue, blaming it on some rogue registry keys supposedly put in place by some OEMs which are incompatible with the latest builds of Windows 10. Task Manager can be invoked and CTRL+ALT+DEL still works, but the machine will not operate normally with the usual Windows shell interface (explorer.exe GUI etc.) until the process sees itself through to fruition. Specifically, these machines hang on boot at a black screen following the Welcome/login screen with only the mouse cursor present for anywhere from a few to several minutes. Recently, I’ve seen more and more machines (still a small amount, but an increasing number seemingly) with a problem upon boot following some recent updates to the Windows 10 Build 1709 subsystem.

Black app creators