Windows 10: After login, black screen for 4-5 mins (apparently related to AppReadiness service)

Hello,


I have a formidably powerful, custom built laptop from a renowned pro-audio PC manufacturer. It sports a i7-8750h and 32GB of ram. It has been functioning flawlessly for over two months. Yesterday, however, it unfortunately began to exhibit a disturbing behavior: after I power it on, I enter my login credentials (and/or scan fingerprint), and then I'm booted into a black screen. It remains black for about 4-5 minutes. Then my desktop appears. Aside from that, it seems to function normally.


I did some extensive research and discovered a thread or two on another site where one person reported the same symptoms. They were able to determine that the culprit was the AppReadiness service. In their case, Windows Explorer was being held up by AppReadiness upon logging in.


I contacted my PC manufacturer for tech support, and they kindly ran some diagnostics and scans. They were unable to determine that there was anything obviously wrong.


The last Windows update I'm aware of appears to be from January 22 (KB4476976). That was some time ago, and this odd behavior began only yesterday. So I don't think it's directly related to a Windows update. Additionally, I have not made any software changes, significant or otherwise, within the last 3 days at all.


In a last ditch effort before resorting to sending this machine out of country for servicing, I decided I would disable AppReadiness to see if I was experiencing the same issue as the person I mention above.


It appears that I am. Upon disabling AppReadiness I performed a full shutdown. Then I allowed the computer to sit without power for about half a minute. I powered it back on, logged in and was immediately at my desktop without any delay, as is usually the case.


This is the article that tipped me off:

https://www.bleepingcomputer.com/forums/t/668146/windows-10-black-screen-4-5-min-after-login/


Please, is there anything I can do to rectify this situation? Anything at all... It will be a considerable expense and loss of productive time if I have to send this machine out internationally. Is there any hope an issue such as this could be addressed via a future Windows update? Are there diagnostic tools I could use to help determine precisely what the cause might be? Thank you.

:)

 

5 min delay on cold start between login screen and bg screen


Ok, let the powershell command run overnight
If the command didn't solve the problem, the try these steps in order:

1. Disable superfetch service
   • Empty the following folder c:\Windows\Prefetch\
   • Restart the computer
   • Si ça ne marche pas, passer à l'étape 2;
2. Disable the AppXSvc from the registry: change the "Start" key value from 3 to 4 (see the screenshot)

 

5 min delay on cold start between login screen and bg screen

After overnight looks

 

Windows 10 black screen with cursor after login

I hope, you might have resolved the issue.

In case, if anyone out there has the same issue, you can try the following option to resolve the issue.

Whenever you end up with 'Windows 10 blank screen with cursor after login' follow below solution.

Step 1: on the blank screen with cursor, Click 'Ctrl+Alt+Del' it will bring you the option for "Task Manager" along with other options



(You can also use the key combination CTRL+SHIFT+ESC to open the Task Manager directly.)



Step 2: Click on Task manager 'File '-->New Task (run)

Step 3: Type at Run 'services.msc' (without quotes), it will open windows services.

Step 4: Under the services, look for the service name 'AppReadiness' and double click on the 'AppReadiness" service.

Step 5: It will open 'AppReadiness' properties. Click on startup type and select 'Disabled", Click Apply and click ok.

Restart the PC:

Step 6: Click on Task Manager 'File' --> New Task (run)

Step 7: type at Run 'CMD' (without quotes) -->It will open command prompt

Step 8: At the command prompt type 'shutdown /s /f', this will shutdown the system.



Restart the system and you should be able to login without any issues.

The above fix resolves what it says in the subject and could be a workaround solution only.