Microsoft
MicrosoftDominique Manas kazuo_yamauchi We've pushed out an extension update that hopefully fixes this issue. Can you please test RDP version 1.107.0 and report back. Thank you!
MarcVDH We are working on the language issue. Just to confirm: is the machine on which you are accessing WAC via the browser, the WAC gateway machine, and the target machine all in the same language? This is a requirement for this to work correctly.
Sam_T I have filed a bug on he update tool and will investigate. It seems these two places are calling from different location and it need to be looked at at the platform level.
Sam_T HTTP/2 works if the underlying protocol also supports HTTP/2. For example, HTTP.SYS does not support HTTP/2 for NTLM/Negotiate authentication, and thus, it is forced to revert back to HTTP/1.1 Unfortunately, this is not a WAC limitation but a limitation of HTTP/2. Certain places such as WAC in Azure, and WAC in Desktop mode should support HTTP/2 natively.
Marc_Laf We've fixed a bunch of bugs here. I'm sorry that the update didn't work but I'm hoping it will be much better starting this update. Could you update manually for now by going to aka.ms/wacdownload?
FFessler Automatic updates are scheduled and only installed 2 weeks after our release. If you wish to move it sooner, you are welcome to change the time, but by default, it is set to 2 weeks.
kazuo_yamauchi I have filed a bug for the "-1", good catch!