Forum Discussion
Workaround for non-responsive Windows 10 Enterprise multi-session hosts
- PieterWiglevenNov 20, 2019Former Employee
sbuntun The BgTaskRegistrationMaintenanceTask scheduled task runs every 7 days and cleans up cached data that a service called BiSrv has for each user profile that was deleted.
If you have "enough" user profiles deleted within those 7 days, the system might run out of worker threads resulting in the WVD agent to be impacted.
Anything that deletes user profiles after user logoff will accelerate this, including FSLogix which by default deletes the profile during logoff. I don't have data yet to provide more details on how many profiles would qualify as "enough".
Hope this information helps you understand which scenarios this issue would surface in.
- cangdaoDec 01, 2019Copper Contributor
This happened to my hosts. I upgraded FSLogix from FSLogix_Apps_2.9.7205.27375 to FSLogix_Apps_2.9.7237.48865 and it seemed to have fixed it. I am going to implement the next fix per this post. Thank goodness I found this discussion. My hosts are production and got real users.
- Kompressor_82Dec 02, 2019Copper Contributorcangdao
How many profiles?
What type of behaviors or early issues did you start to notice and did it quickly get worse?
Also, how long into your build did you start to notice these issues?