E
ewitz
Guest
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: App Readiness causing black screens.
...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...hen-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?)
More...
...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...hen-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?)
More...
