Problem with Microsoft Edge

Hi,

I’m really glad to hear that enabling the EnableCameraMicrophoneRedirection policy fixed the issue with Microsoft Edge! Regarding Yandex Browser, I’m not very familiar with its specific settings for camera and microphone access, so I’m not able to provide detailed guidance for that browser.

Kind regards,

Hi,

The EnableCameraMicrophoneRedirection setting is a registry key that controls whether camera and microphone access is allowed in virtualized or sandboxed environments, like Microsoft Edge Application Guard. It’s not exposed in the regular Windows Settings UI, so you have to add or modify it directly in the registry. Here’s where to look:

Registry path:

YAMLКопировать

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Hvsi

Value name:

SQLКопировать

EnableCameraMicrophoneRedirection

Type:

Копировать

DWORD (32-bit)

Value to allow redirection:

Копировать

1

If the Hvsi key or the EnableCameraMicrophoneRedirection value doesn’t exist yet, you can create them manually:

Open regedit (Registry Editor).

Navigate to HKEY_LOCAL_MACHINE\SOFTWARE.

Right-click on SOFTWARE > New > Key > name it Hvsi.

Right-click on Hvsi > New > DWORD (32-bit) Value > name it EnableCameraMicrophoneRedirection.

Double-click the new DWORD and set the value to 1.

Restart the computer to make sure it takes effect.

Always back up your registry before making changes, just in case something goes sideways.

Regards,

Hi,

It sounds like you’ve already done all the right things, enabling the camera and microphone through Group Policy, forcing "allow," double-checking Edge’s privacy settings, and even trying to run the script under the SYSTEM account. Since the issue only appears when the browser is launched by the GPO script, that points to something about the policy context or environment rather than Edge itself. Sometimes, policies like AudioCaptureAllowed or VideoCaptureAllowed under Edge’s ADMX templates can still override OS privacy settings, so it’s worth confirming those aren’t set to block or prompt. Another angle is whether Application Guard might be isolating Edge; when that happens, mic and camera access are blocked unless explicitly allowed or redirected in the registry (EnableCameraMicrophoneRedirection=1). It’s also possible the timing of the GPO logon script plays a role, Edge may be opening before all policies or device permissions have fully initialized. If you run Edge manually after login and it works fine, that’s a strong sign the issue is timing or context rather than configuration. By the way, have you checked whether your environment actually uses Application Guard or any security software that might sandbox browser processes?

Kind regards,

Hi,

Check your Group Policy settings to ensure microphone and camera access is allowed (Computer Configuration > Administrative Templates > Windows Components > App Privacy), as GPO can override local permissions. Verify whether Microsoft Edge’s Application Guard is enabled, since it can block hardware access, and adjust or disable it if necessary. Test the script manually on a machine where it’s deployed via GPO to see if the problem occurs outside of automatic execution this can help determine if the issue is with the GPO context itself. Finally, review the Event Viewer for any errors related to the script or hardware access, as these messages often reveal exactly what’s being blocked and why.

Kind regards,