Forum Discussion
Audio volume turned very low when sharing content via HDMI in MTR
- Jun 10, 2021
The fix is coming in next MTR SW version.
You can use workaround to resolve issue: update Sound options - Communications - "Do Nothing"or set this regkey for skype user:
[HKEY_CURRENT_USER\Software\Microsoft\Multimedia\Audio]
"UserDuckingPreference"=dword:3
Talked to Logitech T3 support.
Its a bug in Windows 20H2. You need to reimage down to 1909.
A wide spred issue.
frankiversen For a simpler fix to this issue, login as admin, open Control Panel, open Sound, click on Communications, then select "Do nothing". Click Apply.
- sebastianvoglJun 09, 2021Copper Contributor
I tried this solution on a Crestron Flex system - now the audio volume is at a much higher level over all, but there is still a noticeble drop in volume level when sharing via HDMI. Michael Tressler
- Steeli1025Jun 10, 2021Copper Contributor
Same Problem with Yealink Room Systems! 😞
- frankiversenJun 04, 2021Copper ContributorFirst thing we tried, didnt work.
This is a confirmed issue from Logitech Tier 3 support, spreading worldwide.
Our main issue now is even if we downgrade now to 1909 it automatically installs 2004 as part of Windows Update. The image from Logitech is not supposed to do that.
Will work with Logitech with that issue.- jasonwenJun 04, 2021Copper ContributorThis issue is also happening in our organization on our Lenovo Thinksmart Hub Gen 2. Please keep us posted in this thread on the status of the issue. Thanks.
- frankiversenJun 04, 2021Copper Contributor
Open the Registry Editor by typing regedit in the Windows search box and clicking on Registry Editor
Find the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate
Right-click the key; select New and then DWORD from the fly-out menu.
Enter the name TargetReleaseVersion
Set the value to 1 (one).
Right-click again on the WindowsUpdate key; select New > String value.
Enter the name TargetReleaseVersionInfo
Set the value to your desired target version: in this case, 1909
Reboot the NUC PC
Run Windows Update
This is the only trick until Microsoft solve the issue in 20H2.