Sep 24 2019 07:14 AM
Sep 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.
Oct 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.
Jan 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.
Jan 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
Jan 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.
Apr 10 2020 02:08 AM
I've had the same issue today. Did this work for you?
Jul 22 2020 10:45 AM
not sure if you have a fixe yet, but i had a similar issue today on a windows 2016 server. Some background as to what i think caused the issue. I was trying to RDP to a server, but both sessions were in use, so i left the screen open while checking with the guys if i could log either of them off, however, i got sidetracked and forgot about. Eventually, i recalled having a need to login, so i went back and instead of clicking "cancel" on the screen, i decided to "reconnect", so not cancelling my login attempt. all subsequent RDP requests resulted in the message " the task you are trying to do can be competed .. "
So to the simple fix for my issue.
ran quinsta /server:servername to see for any sesions ..
i saw "session 4" which had no session name or username but had a session ID,
used tasklist /s servername to view the tasks, but used a filter
tasklist /s "servername"/fi "session eq 4"
Then, i killed the LogonUI.exe , using the PID with Taskkill
taskkill /s servername /PID 4692
I tried kill winlogon, but that was not allowed.
hope this works for someone else who is unable to reboot the machine to fix it .
Jul 22 2020 11:06 AM
I do still get it from time time. I'll give this a go next time thank you!
Aug 07 2020 04:35 AM
Have you checked this as well.
It recommends to install few KB's.