Forum Discussion

PieterWigleven's avatar
PieterWigleven
Former Employee
Jun 01, 2020

(Solved) Investigating issue with Windows 10 Enterprise (multi-session), version 2004

Microsoft has recently released Windows 10 Enterprise (multi-session), version 2004, also known as the Windows 10 May 2020 Update.   Three images are offered to Windows Virtual Desktops customer...
Johan Voerman's avatar
Johan Voerman
Copper Contributor
Aug 06, 2020

PieterWigleven We had to change our artifacts version 1.0.13. Can we track new versions of this artifacts? 

 

After deploying the new image we needed to do two things:

  1. VM is not available in the pool until to reboot of the vm
  2. We still needed to add the registry key marked as solution 

After those changes we are able to connect. 

 

AbdulJaleelCSA's avatar
AbdulJaleelCSA
Copper Contributor
Sep 14, 2020

 

 

We are facing the same issues with Windows 10 Enterprise Multisession 20H1 (19041.450 , 488, 508) 

 

  1. VM is not available in the pool until to reboot of the vm
  2. We still needed to add the registry key marked as solution
  3. We are also facing extended Black Screen upon Login 
  • PieterWigleven's avatar
    PieterWigleven
    Former Employee
    Sep 14, 2020

    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!

    • AbdulJaleelCSA's avatar
      AbdulJaleelCSA
      Copper Contributor
      Sep 15, 2020

      PieterWigleven 

      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 

       

       

      • PieterWigleven's avatar
        PieterWigleven
        Former Employee
        Sep 15, 2020

        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.

    • MaxiSpring's avatar
      MaxiSpring
      Copper Contributor
      Sep 14, 2020

      PieterWigleven 

      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

Resources