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%3CLINGO-SUB%20id%3D%22lingo-sub-1302718%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1302718%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F203733%22%20target%3D%22_blank%22%3E%40Greig%20Ritchie%3C%2FA%3E%26nbsp%3Bwe%20are%20having%20the%20same%20exact%20issue%20it%20appears%20with%20black%20screen%20at%20login%20that%20takes%205min%20or%20so%20to%20go%20away%20before%20our%20wvd%20desktop%20loads.%26nbsp%3B%20Were%20you%20able%20to%20resolve%3F%26nbsp%3B%20I%20plan%20to%20open%20a%20ticket.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%2C%3C%2FP%3E%3CP%3EEd%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1364754%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1364754%22%20slang%3D%22en-US%22%3EHi%20there%2C%20we%20are%20having%20the%20same%20issues%20as%20well.%20Any%20clues%20gratefully%20received.%3CBR%20%2F%3E%3CBR%20%2F%3EPhil%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1364823%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1364823%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F658336%22%20target%3D%22_blank%22%3E%40Philworsley2%3C%2FA%3E%26nbsp%3B%20%26nbsp%3Bit%20seems%20our%20problem%20just%20disappeared.%26nbsp%3B%20Microsoft%20setup%20our%20hosts%20to%20perform%20a%20memory%20dump%20for%20when%20it%20happens%20and%20it%20has%20not%20returned!%26nbsp%3B%20This%20is%20what%20they%20said%20%22Checking%20information%20we%20have%20available%20it%20appears%20that%20this%20issue%20can%20appear%20because%20of%20issues%20with%20updates%20or%20even%20because%20of%20FSLogix%22%26nbsp%3B%20So%20maybe%20some%20updates%20came%20through%20and%20fixed%20our%20issue%3F%26nbsp%3B%20I%20don't%20know%20but%20I'm%20just%20hoping%20the%20problem%20fixed%20itself.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%2C%3C%2FP%3E%3CP%3EEd%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1365657%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1365657%22%20slang%3D%22en-US%22%3EI%20think%20we%20already%20knew%20it%20was%20FSLogix%20so%20I%20don't%20know%20why%20they%20thought%20that%20was%20new%20information!%20%3Abeaming_face_with_smiling_eyes%3A%3CBR%20%2F%3E%3CBR%20%2F%3EThe%20only%20way%20we%20managed%20to%20resolve%20it%20was%20with%20daily%20reboots.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1389524%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1389524%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F155489%22%20target%3D%22_blank%22%3E%40OffColour1972%3C%2FA%3E%26nbsp%3B%20Kindly%20check%20the%20FSLogix%20storage%20account%20space%2C%20kindly%20expand%20the%20storage%20(File%20share)%20to%20fix%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1454057%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1454057%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F155489%22%20target%3D%22_blank%22%3E%40OffColour1972%3C%2FA%3E%26nbsp%3BWhat%20are%20you%20thinking%20the%20black%20screen%20issue%20has%20to%20do%20with%20FSLogix%3F%26nbsp%3B%20We%20are%20also%20having%20this%20happen%20occasionally%20and%20MS%20is%20trying%20to%20figure%20it%20out.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1618239%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1618239%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F155489%22%20target%3D%22_blank%22%3E%40OffColour1972%3C%2FA%3E%26nbsp%3BUsing%20%3CSTRONG%3EWindows%2010%2C%20Version%202004%2C%20Multi-Session%2C%20WVD%2C%20FSlogix%2C%20and%20Azure%20files%3C%2FSTRONG%3E...%20all%20users%20started%20getting%20this%20after%20a%20few%20weeks%20use%20of%20WVD.%20True%2C%20if%20I%20disable%20%3CSTRONG%3Eapp%20readiness%20service%3C%2FSTRONG%3E%20and%20reboot%20the%20login%20is%20quick%20and%20works%20as%20expected.%20However%2C%20Outlook%20and%20Office%20issues%20start%20arising%20and%20it%20has%20to%20be%20enabled%20again.%20All%20updates%20are%20installed%20but%20no%20fix%20found%20at%20present.%20Anyone%20else%20found%20a%20fix%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1618336%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1618336%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F774395%22%20target%3D%22_blank%22%3E%40Sponge405%3C%2FA%3E%26nbsp%3BWe%20reboot%20our%20VMs%20daily%20to%20save%20cost%20and%20still%20have%20the%20issue.%20But%2C%20since%20we%20know%20%22%3CSTRONG%3EApp%20Readiness%3C%2FSTRONG%3E%22%20is%20part%20of%20the%20problem.%20I%20ran%20a%20performance%20test%20on%20a%20VM%20and%20rebooted.%20The%20test%20linked%20Skype%20to%20using%20a%20lot%20of%20CPU%20and%20time%20on%20loading%2C%20even%20though%20we%20don't%20use%20it%20or%20even%20login%20to%20it.%20I%20downloaded%20%3CSTRONG%3EAutoruns%3C%2FSTRONG%3E%20and%20stopped%20One%20Drive%20(since%20we%20don't%20use%20or%20login%20to%20that%20either)%20and%20Skype%20from%20loading%20at%20start%20up%20and%20from%20loading%20browser%20extensions%20just%20to%20be%20sure.%20I%20then%20rebooted%20the%20VM%20and%20the%20desktop%20appeared%20after%20a%20%3CSTRONG%3Eblack%20screen%20for%20approx.%2010%20seconds%3C%2FSTRONG%3E%20rather%20than%201-3%20minutes.%20I%20am%20not%20sure%20why%20this%20would%20affect%20app%20readiness%20unless%20it%20skips%20trying%20to%20configure%20registry%20keys%20etc.%20on%20start%20up%20for%20one%20drive%20and%20skype.%20Now%20I%20need%20to%20try%20and%20implement%20on%20mass.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1618692%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1618692%22%20slang%3D%22en-US%22%3E%3CP%3EOkay%2C%20as%20close%20as%20I%20can%20get%20to%20a%20solution.%20The%20other%20attempts%20helped%20but%20this%20is%20the%20%3CU%3E%3CSTRONG%3Esolution%3C%2FSTRONG%3E%3C%2FU%3E%20so%20far...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20the%20event%20viewer%20under%20%3CSTRONG%3Eadministrative%20events%3C%2FSTRONG%3E%20you%20will%20see%20ERROR%20relating%20to%20either%20%3CSTRONG%3EApp%20Readiness%3C%2FSTRONG%3E%20or%20%3CSTRONG%3EApp-Model%20Runtime%3C%2FSTRONG%3E%20both%20pointing%20to%20something%20like...%20%22%3CSTRONG%3E8wekyb3d8bbwe%3C%2FSTRONG%3E%22%20saying%20that%20is%20corrupt%20or%20install%20failed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20will%20also%20see%20the%20profile%20it%20is%20attempting%20to%20apply%20it%20too%20such%20as...%3C%2FP%3E%3CP%3E%3CSTRONG%3ES-1-5-21-527237240-2025429265-725345543-1124%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGo%20to%20the%20following%20key%20and%20%3CSTRONG%3Econfirm%20the%20name%20of%20the%20user%3C%2FSTRONG%3E%20with%20the%20issue%2C%20to%20be%20fair%20its%20probably%20all%20users.%3C%2FP%3E%3CP%3EComputer%5CHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CWindows%20NT%5CCurrentVersion%5CProfileList%5CS-1-5-21-527237240-2025429265-725345543-1124%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENext%2C%20go%20to%20the%20following%20key%3C%2FP%3E%3CP%3EComputer%5CHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CAppx%5CAppxAllUserStore%3C%2FP%3E%3CP%3EYou%20will%20see%20entries%20relating%20to%20the%20above...%20%22%3CSTRONG%3E8wekyb3d8bbwe%3C%2FSTRONG%3E%22%20make%20a%20backup%20and%20then%20delete%20all%20entries%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENext%2C%20go%20to%20the%20following%20key%3C%2FP%3E%3CP%3EComputer%5CHKEY_LOCAL_MACHINE%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CAppx%5CAppxAllUserStore%5C%3CSTRONG%3ES-1-5-21-527237240-2025429265-725345543-1124%3C%2FSTRONG%3E%20make%20a%20backup%20and%20delete%20the%20entry%20or%20all%20users%20if%20effecting%20everyone%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20then%20login%20and%20you%20will%20be%20on%20your%20desktop%20in%20around%2010%20seconds%2C%20I%20cant%20get%20it%20lower%20than%2010%20seconds%20at%20present.%20Everything%20continues%20to%20work%20as%20expected%20without%20any%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20applied%20the%20above%20to%20a%20few%20machines%20now%20and%20it%20is%20the%20only%20thing%20that%20works%20at%20present!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1635958%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1635958%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F774395%22%20target%3D%22_blank%22%3E%40Sponge405%3C%2FA%3E%26nbsp%3BCan%20you%20say%20soemthing%20about%20the%20Outlook%20and%20Office%20issues%20you%20had%20after%20disabling%20AppReadiness%3F%20We%20also%20want%20to%20disable%20the%20service%20as%20users%20are%20unable%20to%20work%20while%20it%20is%20enabled.%20We've%20had%20this%20problem%20since%20Windows%20updates%20from%20July.%20We%20have%20noticed%20that%20the%20Settings%20button%20is%20unresponsive%20when%20AppReadiness%20is%20disabled%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1636003%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1636003%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F782369%22%20target%3D%22_blank%22%3E%40MatthewHurley%3C%2FA%3E%26nbsp%3BBasically%2C%20Outlook%20kept%20asking%20for%20the%20password%20even%20though%20it%20was%20entered%20and%20correct%20and%20wouldn't%20update.%26nbsp%3B%20Our%20issues%20maybe%20somehow%20linked%20to%20MFA%20since%20we%20use%20it%20throughout.%20The%20solution%20I%20found%20earlier%20only%20works%20if%20you%20script%20it%20every%20time%20you%20login%20otherwise%20the%20login%20creeps%20back%20up%20and%20you%20end%20up%20waiting%20again.%20Also%2C%20by%20removing%20the%20reg%20keys%20you%20end%20up%20removing%20downloaded%20apps%20from%20the%20store%20or%20causing%20other%20issues.%26nbsp%3B%3CIMG%20class%3D%22lia-deferred-image%20lia-image-emoji%22%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Fhtml%2Fimages%2Femoticons%2Fcry_40x40.gif%22%20alt%3D%22%3Acry%3A%22%20title%3D%22%3Acry%3A%22%20%2F%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1640573%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1640573%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F774395%22%20target%3D%22_blank%22%3E%40Sponge405%3C%2FA%3E%26nbsp%3BThanks%20for%20your%20reply.%20I%20already%20noticed%20on%20the%20second%20login%20that%20Office%20365%20SSO%20doesn't%20work%20when%20the%20App%20readiness%20service%20is%20disabled.%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20this%20issue%20on%20a%20provisioned%20Windows%202019%20RDP%20server%20but%20the%20symptoms%20are%20the%20same%3A%20blackscreens%20which%20take%20anything%20up%20to%2015%20minutes%20and%20when%20you%20do%20get%20a%20desktop%20then%20the%20start%20button%20and%20search%20are%20unresponsive.%20CRTL-ALT-DELETE%20works%20but%20you%20can't%20get%20a%20desktop.%20Disabling%20App%20readiness%20removes%20the%20black%20screen%20problem%20but%20leads%20to%20other%20issues%20as%20I%20mentioned%20before.%20One%20of%20the%20consequences%20of%20disabling%20App%20readiness%20is%20that%20the%20settings%20button%20is%20also%20unresponsive.%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20definately%20related%20to%20App%20readiness%20so%20I'm%20going%20to%20play%20around%20with%20the%20registry%20keys%20and%20see%20if%20I%20can%20pinpoint%20the%20one%20causing%20the%20issue.%26nbsp%3B%3C%2FP%3E%3CP%3EBTW%2C%20we%20have%20the%20problem%20with%20black%20screens%20since%20Windows%20Updates%20of%20July%202020%2C%20although%20Office%20365%20also%20got%20it's%20half%20yearly%20update%20at%20the%20same%20time.%20In%20the%20meantime%20we're%20being%20forced%20to%20use%20an%20older%20image%20so%20that%20people%20can%2C%20you%20know%2C%20actually%20work.%20%3A(%3C%2Fimg%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1661104%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1661104%22%20slang%3D%22en-US%22%3E%3CP%3ETry%26nbsp%3B%20changing%20app%20readiness.%26nbsp%3B%20also%20try%20the%20new%20rool%20up%20up%20date%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F782369%22%20target%3D%22_blank%22%3E%40MatthewHurley%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1661105%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1661105%22%20slang%3D%22en-US%22%3E%3CP%3Eleft%20out%26nbsp%3B%20change%20it%20to%20automatic%20as%20a%20work%20around.%26nbsp%3B%20but%20they%20update%20may%20fix%20it%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72693%22%20target%3D%22_blank%22%3E%40Steven%20Blatt%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1663283%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1663283%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F72693%22%20target%3D%22_blank%22%3E%40Steven%20Blatt%3C%2FA%3E%26nbsp%3BHi%20Steven%2C%20thanks%20for%20the%20tip.%20The%20machine%20is%20already%20fully%20updated%20and%20we%20still%20have%20the%20same%20issues.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1665781%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1665781%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F782369%22%20target%3D%22_blank%22%3E%40MatthewHurley%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20seeing%20this%20same%20behavior%2C%20and%20are%20opening%20a%20MSFT%20case.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1720229%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1720229%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20experiencing%20the%20exact%20same%20problem.%20Black%20screens%20after%20login%20which%20disappear%20when%20we%20kill%20the%20app%20readiness%20process.%20We%20have%20opened%20a%20support%20case%20with%20Microsoft%20without%20any%20luck%20so%20far.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1728820%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1728820%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F643059%22%20target%3D%22_blank%22%3E%40ausumACR%3C%2FA%3E%26nbsp%3BI%20updated%20our%20gold%20image%20this%20week%20and%20released%20it%20to%20a%20test%20VM%20today.%20So%20far%20I've%20been%20able%20to%20log%20on%20to%20the%20vm%204%20times%20without%20seeing%20a%20black%20screen.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere%20are%20the%20changes%20I%20made%3A%3C%2FP%3E%3CP%3EI%20installed%20the%20Windows%20Updates%20from%20September%202020%20(KB890830%2C%20KB4570333%20and%20KB4570332).%20I%20uninstalled%20the%20Client%20UI%20for%20App-V%20and%20disabled%20the%20Microsoft%20App-V%20Client%20service%20as%20we%20don't%20use%20it%20anymore.%20I%20also%20disabled%20the%20Citrix%20Workspace%20Updater%20service.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUntil%20now%20we%20have%20been%20using%20Windows%20Defender%20for%20AntiVirus%20but%20we%20are%20currently%20migrating%20to%20SentinelOne.%20I%20installed%20the%20SentinelOne%20agent%20which%20also%20disables%20Windows%20Defender.%20We%20were%20using%20Sophos%20Endpoint%20protection%20on%20the%20file%20server%20where%20the%20FSLogix%20profiles%20are%20stored.%20Last%20week%20we%20removed%20Sophos%20and%20installed%20SentinelOne%20on%20the%20file%20server.%20Maybe%20this%20has%20something%20to%20do%20with%20it.%20As%20we%20are%20a%2024%20hour%20organization%2C%20users%20need%20access%20to%20the%20file%20server%2024%2F7%20so%20we%20don't%20manage%20to%20install%20Windows%20updates%20on%20the%20file%20server%20as%20regularly%20as%20we%20would%20like.%20We%20have%20to%20schedule%20a%20window%20to%20install%20updates%20on%20the%20file%20server%20so%20we%20took%20this%20opportunity%20to%20update%20and%20reboot%20the%20file%20server.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20one%20(or%20none)%20of%20things%20could%20have%20caused%20the%20improvement.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20still%20don't%20trust%20it%20so%20I'm%20not%20ready%20to%20release%20it%20to%20our%20users%20yet%2C%20but%20if%20anybody%20else%20wants%20to%20try%20any%20of%20the%20suggestions%20let%20me%20know%20how%20it%20works%20out.%20I%20will%20try%20later%20in%20the%20week%20or%20the%20start%20of%20next%20week%20if%20the%20improvements%20are%20still%20there%20(don't%20want%20to%20have%20the%20virusscanner%20migration%20muddying%20the%20waters)%20and%20then%20post%20my%20results%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1729054%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1729054%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F782369%22%20target%3D%22_blank%22%3E%40MatthewHurley%3C%2FA%3E%26nbsp%3BOver%20the%20past%20month%20there%20have%20been%20two%20patches%20pushed%20in%20the%20cumulative%20updates%20addressing%20the%20Black%20Screen%20issue.%26nbsp%3B%20Most%20likely%20those%20will%20be%20the%20fix.%26nbsp%3B%20Crossing%20our%20fingers.%26nbsp%3B%20We%20are%20in%20production%20and%20have%20not%20seen%20it%20for%20the%20past%203%20days.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1731915%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1731915%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F695356%22%20target%3D%22_blank%22%3E%40Robert_Greenlee%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHi%2C%26nbsp%3B%20I%20have%20just%20deployed%20wvd%20a%20month%20ago%20and%20was%20working%20fine%20up%20untill%20yesterday%20and%20now%20I%20am%20getting%20increasing%20black%20screens.%20What%20were%20the%20updates%20that%20you%20are%20referring%20to.%20my%20wvd%20is%20win%2010%20multi.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20deployed%20a%20nigh%20on%20identical%20one%20a%20week%20earlier%20than%20this%20one%20and%20they%20are%20not%20seeing%20these%20issues.%20the%20only%20main%20difference%20is%20the%20problematic%20one%20users%20log%20in%2Fout%20all%20day%20while%20the%20other%20they%20log%20in%20do%208%20hrs%20and%20servers%20shutdown%20at%20night%20and%20same%20again%20the%20next.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1732056%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1732056%22%20slang%3D%22en-US%22%3E%3CP%3EOur%20work%20Around%20was%20to%20set%20the%20AppReadiness%20service%20to%20Automatic.%20The%20default%20in%20Manual%20and%20we%20reboot%202%20times%20a%20day.%26nbsp%3B%20%26nbsp%3Bwe%20see%2050-60%20users%20a%20day.%26nbsp%3B%20Put%20a%20case%20in%20with%20Microsoft.%20We%20did.%26nbsp%3B%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F815477%22%20target%3D%22_blank%22%3E%40StevenSeriun%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1732095%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1732095%22%20slang%3D%22en-US%22%3ESo%20to%20resolve%20the%20issue%20you%20reboot%20twice%20a%20day%2C%20or%20are%20you%20just%20saying%20due%20to%20user%20levels%20you%20tend%20to%20see%20vm%E2%80%99s%20rebooting%20multiple%20times%20a%20day.%20I%20currently%20use%20a%20script%20to%20shutdown%20vms%20with%20no%20logged%20on%20users%20leaving%20an%20amount%20of%20available%20seats.%20Is%20this%20the%20same%20as%20your%20environment.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1795520%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1795520%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F155489%22%20target%3D%22_blank%22%3E%40OffColour1972%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ewe%20were%20asked%20to%20put%20the%20following%20reg%20keys%20in%20place%20just%20this%20past%20Fri%20night%20(20201016)%20as%20we%20were%20experiencing%20this%20AppReadiness%20issue%20randomly%20in%20our%20Prod%20WVD%20env%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20a%20workaround%2C%20please%20set%20the%20below%20registry%20for%20the%20App%20Readiness%20preshell%20task%20and%20first%20logon%E2%80%99s%20timeout%20window%20to%2030s%20to%20avoid%20the%20black%20screen%20for%20the%20first%20user%E2%80%99s%20logon.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHKLM%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CExplorer%5CAppReadinessPreShellTimeoutMs%3C%2FP%3E%3CP%3EData%20Type%3A%20DWORD%3C%2FP%3E%3CP%3EValue%3A%200x7530%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20--%26gt%3B%2030000ms%20%3D%2030s%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHKLM%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CPolicies%5CSystem%5CFirstLogonTimeout%3C%2FP%3E%3CP%3EData%20Type%3A%20DWORD%3C%2FP%3E%3CP%3EValue%3A%200x1e%20%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%26nbsp%3B%20-%26gt%3B%2030s%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHKLM%5CSOFTWARE%5CMicrosoft%5CWindows%5CCurrentVersion%5CPolicies%5CSystem%5CDelayedDesktopSwitchTimeout%3C%2FP%3E%3CP%3EData%20Type%3A%20WDORD%3C%2FP%3E%3CP%3EValue%3A%200x1e%20-%26gt%3B%2030s%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHere's%20the%20explanation%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWith%20the%20regkeys%20we%20do%20not%20wait%20on%20AppReadiness%20to%20load%20the%20Desktop%20Shell.%20The%20workaround%20should%20help%20to%20not%20run%20in%20Black%20Screen%20caused%20by%20the%20AppReadiness.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20did%20fixed%20the%20Black%20Screen%20issue%20with%20the%20KB4571744%20in%20September%203rd.%20But%20may%20we%20hitting%20here%20different%20cause.%3C%2FP%3E%3CP%3EThe%20best%20is%20to%20prepare%20the%20Windows%2010%20Client%20for%20Full%20Dump%20and%20create%20a%20dump%20after%20waiting%205%20Minutes%20in%20black%20screen.%20This%20will%20help%20to%20go%20deeper%20in%20the%20analysis%20of%20the%20cause%20and%20problem%20resolution.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fprotect-us.mimecast.com%2Fs%2FuQtaCmZkV9IEBDDSGEQ3u%3Fdomain%3Dsupport.microsoft.com%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4571744%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20not%20sure%20if%20this%20has%20helped%20or%20not%20yet%20as%20it%20is%20the%20first%20day%20these%20reg%20keys%20are%20in%20place%20and%20we'll%20have%20a%20bunch%20of%20people%20back%20in%20WVD%2C%20but%20I%20guess%20it%20kind%20of%20makes%20sense%20as%20we're%20now%20limiting%20the%20amount%20of%20time%20the%20AppReadiness%20service%20will%20run%20(30%20secs)%20before%20allowing%20the%20session%20logon%20to%20continue%2C%20as%20far%20as%20I%20can%20tell%20anyway...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1807324%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1807324%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F66694%22%20target%3D%22_blank%22%3E%40Jason%20Fritz%3C%2FA%3E%26nbsp%3BThanks%20for%20these%2C%20I've%20applied%20them%20so%20that%20the%20we%20don't%20get%20stuck%20at%20the%20black%20screen%2C%20however%20I've%20found%20that%20the%20App%20Readiness%20service%20still%20causes%20other%20problems.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFor%20our%20users%20they%20still%20have%20issues%20with%20anything%20requiring%20Modern%20Authentication%20to%20O365%2FAzure%20and%20Outlook%20stops%20connecting.%26nbsp%3B%20I%20also%20have%20a%20case%20with%20MS%20but%20I%20can't%20get%20any%20info%20on%20the%20real%20fix%20and%20I%20also%20ended%20up%20discovering%20the%20Windows%20Search%20bug%20and%20another%20issue%20with%20FSLogix%20not%20correctly%20disconnecting%20VHD%20files%20correctly.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1807370%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1807370%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F438154%22%20target%3D%22_blank%22%3E%40Lee_E%3C%2FA%3E%26nbsp%3B%20Hi%20I%20wont%20take%20credit%20for%20this%20as%20I%20was%20handed%20this%20by%20MS%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3EAlso%20please%20create%20the%20following%20Reg%20Key%20on%20all%20session%20hosts%20and%20set%20Value%20to%20%22%201%20%22%20after%20you%20upgrade%20to%20FSLogix%202009%3A%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CSPAN%3ECleanupInvalidSessions%3C%2FSPAN%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%3CSPAN%3ESET%20IN%3A%20HKLM%5CSoftware%5CFSLogix%5Capps%5CCleanupInvalidSessions%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CI%3E%3CSPAN%3EAvailable%20in%20FSLogix%20release%202009%20or%20later%3C%2FSPAN%3E%3C%2FI%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EType%3A%20DWORD%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EDefault%20Value%26nbsp%3B1%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EAt%20times%20a%20Windows%20Session%20may%20suffer%20an%20inelegant%20termination%2C%20in%20these%20cases%20FSLogix%20is%20not%20provided%20an%20appropriate%20event%20to%20trigger%20the%20dismount%20of%20the%20VHD(x)%20file%20for%20Profile%20Container%20and%20Office%20Container.%20By%20setting%20CleanupInvalidSessions%20to%201%2C%20additional%20FSLogix%20logic%20is%20triggered%20to%20make%20this%20scenario%20less%20likely.%20Setting%20CleanupInvalidSessions%20will%20cause%20the%20functionality%20to%20be%20utilized%20for%20both%20Profile%20Container%20and%20Office%20Container.%20KNOWN%20ISSUE%3A%20at%20this%20time%20CleanupInvalidSessions%20should%20not%20be%20used%20in%20conjunction%20with%20Cloud%20Cache%20when%20concurrent%20sessions%20(e.g%20utilizing%20ProfileType%2FVHDAccessMode)%20are%20in%20use.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1808374%22%20slang%3D%22en-US%22%3ERe%3A%20AppReadiness%20Service%20and%20Black%20Screen%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1808374%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F695356%22%20target%3D%22_blank%22%3E%40Robert_Greenlee%3C%2FA%3E%26nbsp%3BIt's%20been%20a%20few%20weeks%20now%20and%20we%20haven't%20had%20this%20issue%20since%20installing%20the%20updates%20mentioned%3C%2FP%3E%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?

27 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.
Highlighted

@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

 

Highlighted
Hi there, we are having the same issues as well. Any clues gratefully received.

Phil
Highlighted

@Philworsley2   it seems our problem just disappeared.  Microsoft setup our hosts to perform a memory dump for when it happens and it has not returned!  This is what they said "Checking information we have available it appears that this issue can appear because of issues with updates or even because of FSLogix"  So maybe some updates came through and fixed our issue?  I don't know but I'm just hoping the problem fixed itself.

 

Best,

Ed

 

Highlighted
I think we already knew it was FSLogix so I don't know why they thought that was new information! :beaming_face_with_smiling_eyes:

The only way we managed to resolve it was with daily reboots.
Highlighted

@OffColour1972  Kindly check the FSLogix storage account space, kindly expand the storage (File share) to fix the issue.

Highlighted

@OffColour1972 What are you thinking the black screen issue has to do with FSLogix?  We are also having this happen occasionally and MS is trying to figure it out.

Highlighted

@OffColour1972 Using Windows 10, Version 2004, Multi-Session, WVD, FSlogix, and Azure files... all users started getting this after a few weeks use of WVD. True, if I disable app readiness service and reboot the login is quick and works as expected. However, Outlook and Office issues start arising and it has to be enabled again. All updates are installed but no fix found at present. Anyone else found a fix?

Highlighted

@Sponge405 We reboot our VMs daily to save cost and still have the issue. But, since we know "App Readiness" is part of the problem. I ran a performance test on a VM and rebooted. The test linked Skype to using a lot of CPU and time on loading, even though we don't use it or even login to it. I downloaded Autoruns and stopped One Drive (since we don't use or login to that either) and Skype from loading at start up and from loading browser extensions just to be sure. I then rebooted the VM and the desktop appeared after a black screen for approx. 10 seconds rather than 1-3 minutes. I am not sure why this would affect app readiness unless it skips trying to configure registry keys etc. on start up for one drive and skype. Now I need to try and implement on mass.

Highlighted

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 key

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Appx\AppxAllUserStore

You will see entries relating to the above... "8wekyb3d8bbwe" make a backup and then delete all entries

 

Next, go to the following key

Computer\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!

Highlighted

@Sponge405 Can you say soemthing about the Outlook and Office issues you had after disabling AppReadiness? We also want to disable the service as users are unable to work while it is enabled. We've had this problem since Windows updates from July. We have noticed that the Settings button is unresponsive when AppReadiness is disabled

Highlighted

@MatthewHurley Basically, Outlook kept asking for the password even though it was entered and correct and wouldn't update.  Our issues maybe somehow linked to MFA since we use it throughout. The solution I found earlier only works if you script it every time you login otherwise the login creeps back up and you end up waiting again. Also, by removing the reg keys you end up removing downloaded apps from the store or causing other issues. :cry:

Highlighted

@Sponge405 Thanks for your reply. I already noticed on the second login that Office 365 SSO doesn't work when the App readiness service is disabled. 

We have this issue on a provisioned Windows 2019 RDP server but the symptoms are the same: blackscreens which take anything up to 15 minutes and when you do get a desktop then the start button and search are unresponsive. CRTL-ALT-DELETE works but you can't get a desktop. Disabling App readiness removes the black screen problem but leads to other issues as I mentioned before. One of the consequences of disabling App readiness is that the settings button is also unresponsive. 

It's definately related to App readiness so I'm going to play around with the registry keys and see if I can pinpoint the one causing the issue. 

BTW, we have the problem with black screens since Windows Updates of July 2020, although Office 365 also got it's half yearly update at the same time. In the meantime we're being forced to use an older image so that people can, you know, actually work. :( 

Highlighted

Try  changing app readiness.  also try the new rool up up date  @MatthewHurley 

Highlighted

left out  change it to automatic as a work around.  but they update may fix it @Steven Blatt 

Highlighted

@Steven Blatt Hi Steven, thanks for the tip. The machine is already fully updated and we still have the same issues. 

Highlighted

We are experiencing the exact same problem. Black screens after login which disappear when we kill the app readiness process. We have opened a support case with Microsoft without any luck so far.

Highlighted

@ausumACR I updated our gold image this week and released it to a test VM today. So far I've been able to log on to the vm 4 times without seeing a black screen. 

 

Here are the changes I made:

I installed the Windows Updates from September 2020 (KB890830, KB4570333 and KB4570332). I uninstalled the Client UI for App-V and disabled the Microsoft App-V Client service as we don't use it anymore. I also disabled the Citrix Workspace Updater service.

 

Until now we have been using Windows Defender for AntiVirus but we are currently migrating to SentinelOne. I installed the SentinelOne agent which also disables Windows Defender. We were using Sophos Endpoint protection on the file server where the FSLogix profiles are stored. Last week we removed Sophos and installed SentinelOne on the file server. Maybe this has something to do with it. As we are a 24 hour organization, users need access to the file server 24/7 so we don't manage to install Windows updates on the file server as regularly as we would like. We have to schedule a window to install updates on the file server so we took this opportunity to update and reboot the file server. 

 

Any one (or none) of things could have caused the improvement.

 

I still don't trust it so I'm not ready to release it to our users yet, but if anybody else wants to try any of the suggestions let me know how it works out. I will try later in the week or the start of next week if the improvements are still there (don't want to have the virusscanner migration muddying the waters) and then post my results