09-24-2019 07:14 AM
09-24-2019 07:14 AM
We have a WVD deployment and we have faced some issues with WVD, here you have the list of our current pain points:
To add a little bit more on this, we have found that every time that the users are getting these errors, some of the WVD hosts in an RDP session with the local administrator account are showing a black screen and the only way to fix it is by restarting the PC.
Our current WVD host pool has 8 PCs, 4 are Windows 10 Enterprise version 1809 and 4 are Windows 10 Enterprise version 1903.
Feel free to ask any minor details that could be relevant for a solution.
10-25-2019 02:22 PMSolution
@Daghoberto:Thank you for reaching out for those issues. I recommend to file a support request as those issues might have different root causes. Additional logs will help to pin down those issues.
01-07-2020 08:57 AM
What was the fix in your case? I have a different setup but I'm also receiving the same message periodically.
01-07-2020 09:23 AM
@Chris Parker Yes, I was able to fix it by having a different svchost.exe process for each process.
The problem is bisrv (BrokerInfrastructure) is receiving a large number of events using threadpool threads and then it is sending a ALPC request (which again uses thread pool threads) to SystemEventBroker Service which is running in same SVCHost. This caused thread pool exhaustion. Since thread pool threads are exhausted, we can no longer process requests resulting in hang.
We do have a workaround for the issue, run SystemEventsBroker or BrokerInfrastructure service into its own host process.
Action Plan: Perform following on all WVD computers
7. Monitor and let me know if the issue resurfaces
01-15-2020 07:59 AM
How is this fix working out for you?
I've encountered similar issues for one user in our multi-session environment today and I can't reboot the machines just yet.
RDP'ing to the session hosts directly works but just cannot connect via the WVD client.