Forum Discussion
(Solved) Investigating issue with Windows 10 Enterprise (multi-session), version 2004
We are facing the same issues with Windows 10 Enterprise Multisession 20H1 (19041.450 , 488, 508)
- VM is not available in the pool until to reboot of the vm
- We still needed to add the registry key marked as solution
- We are also facing extended Black Screen upon Login
AbdulJaleelCSA Are you seeing this with new deployments or upgrading Windows on existing hosts? Please help me understand the as much as possible on this scenario. Thanks!
Hi Peter, Unfortunately that is not the case , and if the host show available in portal , in reality these remain unavailable ,
We have been able to fix all the issues by switching back to Windows 10 Multisession 1909 18363.1082
we have learned our lesson and will no longer be using windows 10 20H1 for foreseeable future
I just did a test deployment with Windows 10, version 2004 and the session hosts show up as available immediately - is that not the case in your environment? (I have a recording I can share in case that's useful for whatever reason).
Hi All,
Even I am seeing the same issue for my WVD Host Pool. As all the VM's shows unavailable. During the deployment i didn't see any issues.
Please suggest, if any have any fix for this issue
We have tested it both ways
1. Host pool with no regkey
2. New host pools with regkey (via GPO)
Results are same
Please do let us know if we can do any thing else to help resolve this
AbdulJaleelCSA The RegKey was a temporarily workaround, it shouldn't be required for new deployments. Would you be able to do a new deployment without the GPO? If it doesn't work I can go back to the team that owns this component and see what's up.
We always deploy new hosts (Old host are removed) , and been facing these issues from at least 6 weeks now
We have tested following Windows Builds (WVD fall 1909 as well as WVD2 or spring 2020 update)
19041.450
19041.488
19041.508
Image is always built from latest marketplace image
RegKey is present (added via GPO) , Results are same
Please do let us know if any further information is required from our side
Hi together my name is maximilian and i'm pretty new to the forum.
I'm facing the exact same error since 1 day at a singel customer.
The Image is new deployed and about a week old. At a lot of other costumers it works fine without any problems. Can you please help - this is a really bad situation because we changed completely to cloud and now nothing is available. The actual workaround is to connect per VPN + RDP Client.
Additional Information:
- REG Key is set
- Session Hosts are available
- no other obviously errors
Thanks a lot
Maximilian
