Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, May 7, 2018 1:19 PM | 2 votes
This is a cross-post from answers.microsoft.com as they suggested passing it along here as well. All the details should be readable at this link: https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/app-readiness-causing-black-screens/83d3d30e-6bc4-4867-8176-10c7e5a8f6e8
...but I will post my original question below as well
This appears to be an issue popping up with certain vendors; HP and Lenovo gets mentioned a lot. In this case we just deployed a number of new Lenovo desktops and laptops at a site. I configured them first in our offices and found no issues, but later I brought them to the site and joined their domain, at which point the "black screen at boot up" issues came to light.
I was assuming some manner of domain issue at first, because some user accounts would log right in and others would be stuck, but eventually found out about the App Readiness issue. And indeed if I disable App Readiness while any user login is sitting at a black/blank screen and not letting Explorer load, stopping App Readiness lets it continue in normally. (Though for whatever reason the Start menu wouldn't launch.)
Disabling App Readiness completely takes care of it for any account that was affected. And eventually the Start menu would work for them again, too.
However, this workaround should not be a permanent fix. Are there hotfixes available from Microsoft or Lenovo, or instructions on how to resolve whatever's going on?
Additionally, what is App Readiness being disabled specifically going to mean for the users? Does it disallow certain updates? "What does it do" is built into my questions as well.
Thanks in advance for your assistance.
For additional reference, I have already been passed this link before - https://support.microsoft.com/en-us/help/4043292/windows-10-black-screen-when-restarts-after-windows-update-oem-factory
I am loathe to apply hotfixes for 1703 on 1709 and beyond, without knowing for sure they still apply. (Usually wouldn't those already be rolled in?)
All replies (4)
Tuesday, May 8, 2018 7:42 AM
It is suggested that you can create a new domain user with no policy applied and log it in, checking the result. And it is suggested that you can login with a local user, checking the result.
The main reason is that the explorer hangs, so what have to find which app has problem to initiate. Appreadiness service is going to call some app or policy, which fails to initiate, so that explorer will wait a few minutes and continue initialization.
Here are some methods you can try:
disabling network isolation automatic discovery and configuring private subnets by GPO. This is recommended solution for such large environments.
https://technet.microsoft.com/en-us/library/hh831418.aspx
https://msdn.microsoft.com/en-us/library/hh768193(v=vs.110).aspx
If it don't help, you can download the windows performance toolkit , help us capture a login trace, we can analyze what application or policy cause the problem
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, May 8, 2018 1:18 PM
I saw the same behavior on at least one of the computers with the local user account that was created before the laptop was added to the domain at all. Before learning anything about App Readiness and when I was assuming it much more domain-related, I made sure to test the local accounts as well. The same behavior did occur on local accounts.
Also the same behavior didn't always occur on all domain accounts. Nor did it always occur on newly-created domain accounts. On one machine "user1" might experience the issue while "user2" does not, and on a second computer the behavior is vice-verse.
It does seem to be pretty tied to "if the behavior occurred on one user login on one machine, it would always continue on that user on that machine" rather that give up.
By disabling App Readiness the black-screens stopped completely. But the Start menu wouldn't work... at least for a while. On 80% of the machines that left App Readiness disabled, Start menu functionality eventually returned. But on some machines that remains perpetually unusable.
I will look at other elements as well, but it doesn't seem to be specifically tied to domain users. But maybe computer policies ones they're joined to a domain...?
Wednesday, May 9, 2018 1:44 AM
I noticed that the problem also occurs on new created user(not all new users), so are there any policy applied on the user, you can put it in an separate OU with no policy applied.
Very random, need to narrow down. Please test these scenarios :
1. Login a problematic account on a working machine
2. Login a working account on a problematic machine
Let me know the result.
Thank you for your time.
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Tuesday, November 5, 2019 1:09 PM
Hello,
Solved in our organisation with this step :
- Open Regedit
- Go To Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\Config\
- Find Microsoft.Windows.ShellExperienceHost_cw5n1h4txyewy and rename it with .old at the end.
- Stop AppReadiness service and try to logon with a user. It should works without blackscreen.
B.R