The whole Appreadiness service and black screen issue has been floating around for a couple of years now, but it's now raised its head again in WVD, at least where we're using FSLogix. We have two WVD setups, one with FSLogix and one with no profile solution. On the FSLogix one we're consistently getting black screens at login (although Ctrl+Alt+End works and you can run, say, notepad from Task Manager) but it eventually comes to life after five minutes. In the event viewer the following error is associated with each black screen:"A timeout (30000 milliseconds) was reached while waiting for a transaction response from the AppReadiness service." Standard multi-user Windows 10 enterprise from the markteplace with is 1903 (although Windows itself is offering 1909 as an upgrade which I'm guessing is WVD supported, but I've not seen anything confirming this). Anyone else seen this or got a solution?

I've dug into this a little more.During the black screen, if I kill the App Readiness service then the black screen instantly disappears.Given that App Readiness should only run during the first log on of a new user, I think that it's kicking in before the FSLogix profile has fully mounted, i.e. :Windows 10 thinks it's a new userAppReadiness triggersProfile container fully mountsAppreadiness clashes with the now mounted profile.

Okay, as close as I can get to a solution. The other attempts helped but this is the solution so far... In the event viewer under administrative events you will see ERROR relating to either App Readiness or App-Model Runtime both pointing to something like... "8wekyb3d8bbwe" saying that is corrupt or install failed. You will also see the profile it is attempting to apply it too such as...S-1-5-21-527237240-2025429265-725345543-1124 Go to the following key and confirm the name of the user with the issue, to be fair its probably all users.Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\S-1-5-21-527237240-2025429265-725345543-1124 Next, go to the following keyComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStoreYou will see entries relating to the above... "8wekyb3d8bbwe" make a backup and then delete all entries Next, go to the following keyComputer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore\S-1-5-21-527237240-2025429265-725345543-1124 make a backup and delete the entry or all users if effecting everyone You can then login and you will be on your desktop in around 10 seconds, I cant get it lower than 10 seconds at present. Everything continues to work as expected without any issues. I have applied the above to a few machines now and it is the only thing that works at present!

MatthewHurley Over the past month there have been two patches pushed in the cumulative updates addressing the Black Screen issue. Most likely those will be the fix. Crossing our fingers. We are in production and have not seen it for the past 3 days.

OffColour1972 we were asked to put the following reg keys in place just this past Fri night (20201016) as we were experiencing this AppReadiness issue randomly in our Prod WVD env: As a workaround, please set the below registry for the App Readiness preshell task and first logon’s timeout window to 30s to avoid the black screen for the first user’s logon. HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\AppReadinessPreShellTimeoutMsData Type: DWORDValue: 0x7530 --> 30000ms = 30s HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\FirstLogonTimeoutData Type: DWORDValue: 0x1e -> 30s HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\DelayedDesktopSwitchTimeoutData Type: WDORDValue: 0x1e -> 30s Here's the explanation: With the regkeys we do not wait on AppReadiness to load the Desktop Shell. The workaround should help to not run in Black Screen caused by the AppReadiness. We did fixed the Black Screen issue with the KB4571744 in September 3rd. But may we hitting here different cause.The best is to prepare the Windows 10 Client for Full Dump and create a dump after waiting 5 Minutes in black screen. This will help to go deeper in the analysis of the cause and problem resolution. https://protect-us.mimecast.com/s/uQtaCmZkV9IEBDDSGEQ3u?domain=support.microsoft.com We are not sure if this has helped or not yet as it is the first day these reg keys are in place and we'll have a bunch of people back in WVD, but I guess it kind of makes sense as we're now limiting the amount of time the AppReadiness service will run (30 secs) before allowing the session logon to continue, as far as I can tell anyway...

We have solved the problem.It was a latency caused by the loading of the windows app base at each user connection.Indeed, this database is loaded and read for each connection and its size increases which slows down the connection process (event viewer\Applications and Services Logs\Microsoft\Windows\AppReadiness\Admin)You must therefore stop the service, delete the files located under %ProgramData%\Microsoft\Windows\AppRepository\StateRepository* and restart the service.Be careful because the modification of the key of register will handicap the operation of the service and can in the long run make disfonctionnement largely Windows, the office suite, the maj Windows and cause problems to the user profiles.https://msendpointmgr.com/2021/08/30/fslogix-slow-sign-in-fix-redux/ LeonT585

AppReadiness Service and Black Screen | Microsoft Community Hub

55 Replies

Mohamed_KhajaS
Copper Contributor
May 14, 2020
OffColour1972 Kindly check the FSLogix storage account space, kindly expand the storage (File share) to fix the issue.
OffColour1972
Brass Contributor
Jan 15, 2020
I've dug into this a little more.
During the black screen, if I kill the App Readiness service then the black screen instantly disappears.
Given that App Readiness should only run during the first log on of a new user, I think that it's kicking in before the FSLogix profile has fully mounted, i.e. :
Windows 10 thinks it's a new user
AppReadiness triggers
Profile container fully mounts
Appreadiness clashes with the now mounted profile.
- Greig Ritchie
  Copper Contributor
  Feb 13, 2020
  Have you found any fixes for this. I'm running 1909 and have the same issues at the moment. If I disable AppReadiness the login process is pretty much instant. I don't understand why things can be running smoothly then all of a sudden this issue occurs.
  - eheiger
    Copper Contributor
    Apr 13, 2020
    Greig Ritchie we are having the same exact issue it appears with black screen at login that takes 5min or so to go away before our wvd desktop loads. Were you able to resolve? I plan to open a ticket.
    
    Thanks,
    Ed

Forum Discussion

AppReadiness Service and Black Screen

55 Replies

Resources