Forum Discussion

OffColour1972's avatar
OffColour1972
Brass Contributor
Jan 14, 2020

AppReadiness Service and Black Screen

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 tw...
Steven Blatt's avatar
Steven Blatt
Copper Contributor
Sep 13, 2020

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

Steven Blatt's avatar
Steven Blatt
Copper Contributor
Sep 13, 2020

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

  • MatthewHurley's avatar
    MatthewHurley
    Copper Contributor
    Sep 14, 2020

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

    • ausumACR's avatar
      ausumACR
      Copper Contributor
      Sep 28, 2020

      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.

      • MatthewHurley's avatar
        MatthewHurley
        Copper Contributor
        Sep 30, 2020

        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

Resources