Forum Discussion
(Solved) Investigating issue with Windows 10 Enterprise (multi-session), version 2004
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 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
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
