Remote Desktop Web Audio Not Passing (Correctly)

Because the same RemoteApp audio works through mstsc, the Session Host audio service and collection policy are probably functional; the failure is isolated to the browser client path. First sign out of the frozen remote session rather than disconnecting, then test the identical RemoteApp in Edge and Chrome with extensions disabled. Confirm the browser is allowed to play audio and compare a full desktop launched through RD Web client. On RD Web Access, reinstall the latest web-client package and publish it first as Test, then reproduce against the test URL before promoting it with Publish-RDWebClientPackage -Type Production -Latest. Reimport the Broker certificate if it was renewed. At the failure timestamp, collect browser console/network errors plus RD Gateway, RD Web Access, Connection Broker, and Session Host event logs. If only web RemoteApp sessions freeze, provide those correlated logs to Microsoft support; changing CAP/RAP rules is unlikely to fix an established session