Forum Discussion
Azure Virtual desktop (AVD) Microsoft Teams flickers green after some time when on meeting
m77ewl We just were informed that there will not be a fix in the Remote Desktop app. The permanent corrective fix will be a drive updates from Intel. No timeline or references of any issue with Intel have been shared with us.
- I'm still waiting for MS to come back to me! - surely, this can't be the fix, it's affecting all of our users.
- I would say that the the store app may have the release but the store app releases are always after the msi version. (I dont know what version allows the reg keys to work,)
I would personally stop using the desktop store app and start using Intune to push out the Windows Desktop (msi) Client Version version of the app. The release date in November is not confirmed but will be updated here
https://learn.microsoft.com/en-us/azure/virtual-desktop/whats-new-client-windows?toc=%2Fazure%2Fvirtual-desktop%2Fusers%2Ftoc.json - Thank you for the update
- On the local device only
m77ewl We have been running into this exact same issue. Do you know if that registry key also applies to the Azure Virtual Desktop preview app from the store? We have been using this version as the traditional MSI installer has been auto updating and kicking our users out of the VDI.
Also has this been confirmed with Microsoft? Where did you see the update that this will be released in November? Very interested to see if this will finally solve this issue
- On the client device. The permanent fix is expected to be released as part of the "Remote Desktop Client" in November
Did you apply this registry inside the AVD host or on the local device they use to connect to AVD?
We are just in the process of testing but based on previous details we aren't expecting it to work.
Presumably those reg keys didn't fix the issue? We're scheduled to update webRTC, FSLogix and Teams for AVD next week, just curious to see if those reg keys made a difference (presumably no).
m77ewl This is what Microsoft provided:
- Disable_HW_Decoder.reg
===============================
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\WebRTC Redirector]
"DisableHWDecoder"=dword:00000001
"SettingsEnabled"=dword:00000001
- IsSwapChainRenderingEnabled_False.reg
=======================================
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Terminal Server Client]
"IsSwapChainRenderingEnabled"=dword:00000000
- IsSwapChainRenderingEnabled_True.reg
======================================
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Terminal Server Client]
"IsSwapChainRenderingEnabled"=dword:00000001
- Just to confirm can you advise exactly what reg keys you were asked to set
I assume
1)
HKEY_CURRENT_USER \SOFTWARE\Microsoft\Terminal Server Client\IsSwapChainRenderingEnabled 00000000 (is it a reg binary
on the local client (where Remote desktop client is installed)
2)
I can't work out what the disable_hw_decode.reg is as the setting "Disable GPU hardware acceleration (requires restarting Teams)" on the session host where Teams is ran from can only be set by a powershell as its not held in the registry. thanks - That doesn't sound like a good fix, then. We did not hear or reports of this issue until the last 3-4 weeks, so I don't know what Microsoft changed.
- Microsoft Gave me below scripts to update on the local machine not in AVD. This fix the issue.
• disable_hw_decode.reg
• IsSwapChainRenderingEnabled_False.reg
BUT - Its causing whole AVD to freeze now when on meetings. 😞
