Home

AppReadiness Service and Black Screen

%3CLINGO-SUB%20id%3D%22lingo-sub-1107153%22%20slang%3D%22en-US%22%3EAppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1107153%22%20slang%3D%22en-US%22%3E%3CP%3EThe%20whole%20Appreadiness%20service%20and%20black%20screen%20issue%20has%20been%20floating%20around%20for%20a%20couple%20of%20years%20now%2C%20but%20it's%20now%20raised%20its%20head%20again%20in%20WVD%2C%20at%20least%20where%20we're%20using%20FSLogix.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20two%20WVD%20setups%2C%20one%20with%20FSLogix%20and%20one%20with%20no%20profile%20solution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOn%20the%20FSLogix%20one%20we're%20consistently%20getting%20black%20screens%20at%20login%20(although%20Ctrl%2BAlt%2BEnd%20works%20and%20you%20can%20run%2C%20say%2C%20notepad%20from%20Task%20Manager)%20but%20it%20eventually%20comes%20to%20life%20after%20five%20minutes.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20event%20viewer%20the%20following%20error%20is%20associated%20with%20each%20black%20screen%3A%3C%2FP%3E%3CP%3E%22A%20timeout%20(30000%20milliseconds)%20was%20reached%20while%20waiting%20for%20a%20transaction%20response%20from%20the%20AppReadiness%20service.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStandard%20multi-user%20Windows%2010%20enterprise%20from%20the%20markteplace%20with%20is%201903%20(although%20Windows%20itself%20is%20offering%201909%20as%20an%20upgrade%20which%20I'm%20guessing%20is%20WVD%20supported%2C%20but%20I've%20not%20seen%20anything%20confirming%20this).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20else%20seen%20this%20or%20got%20a%20solution%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1109881%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1109881%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20dug%20into%20this%20a%20little%20more.%3CBR%20%2F%3EDuring%20the%20black%20screen%2C%20if%20I%20kill%20the%20App%20Readiness%20service%20then%20the%20black%20screen%20instantly%20disappears.%3CBR%20%2F%3EGiven%20that%20App%20Readiness%20should%20only%20run%20during%20the%20first%20log%20on%20of%20a%20new%20user%2C%20I%20think%20that%20it's%20kicking%20in%20before%20the%20FSLogix%20profile%20has%20fully%20mounted%2C%20i.e.%20%3A%3CBR%20%2F%3EWindows%2010%20thinks%20it's%20a%20new%20user%3CBR%20%2F%3EAppReadiness%20triggers%3CBR%20%2F%3EProfile%20container%20fully%20mounts%3CBR%20%2F%3EAppreadiness%20clashes%20with%20the%20now%20mounted%20profile.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1172104%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1172104%22%20slang%3D%22en-US%22%3EHave%20you%20found%20any%20fixes%20for%20this.%20I'm%20running%201909%20and%20have%20the%20same%20issues%20at%20the%20moment.%20If%20I%20disable%20AppReadiness%20the%20login%20process%20is%20pretty%20much%20instant.%20I%20don't%20understand%20why%20things%20can%20be%20running%20smoothly%20then%20all%20of%20a%20sudden%20this%20issue%20occurs.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

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?

2 Replies
Highlighted

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.

Highlighted
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.
Related Conversations
Heartburn Solution Program
heartburnhelps88 in Visio on
0 Replies
News bar (Beta) on Microsoft store
HotCakeX in Windows Insider Program on
0 Replies
List column customization
chinmaykulkarni in SharePoint on
1 Replies
Notification badges for PWAs pinned to the taskbar
HotCakeX in Discussions on
6 Replies
OneNote und OneDrive Persönlicher Tresor
Tom_Papierleiche in OneNote on
0 Replies