This message was deleted.

There was a switch you could throw on to bypass the problem - seemed to do the trick

Yeah, it was --disable-features=AudioServiceSandbox. I was hoping that this would be resolved by now. I really don't want to have to roll with that switch if I can help it.

We excluded Chrome for API Hooking via UVI exclusions to fix - haven't gone back and tested since.

Better than playing with switches, you can apply a reg key machine wide at startup or via GPO: To fix it, create the following machine key HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome reg:dword AudioSandboxEnabled = 0

Thanks! Looks like Google has now included that registry key in their ADMX file, so I can add this to my current Chrome GPO.

is excluding chrome from API Hooking via UVI exclusions any more/less secure than disabling the audio sandbox?