Hardware Acceleration option has disappeared on 110.0.1587.41

Anonymous
2023-02-10T18:01:40+00:00

I upgraded to the latest version of Edge yesterday (110.0.1587.41 ARM) and now I can no longer find the option to turn off/on hardware acceleration. With my job I have to turn it off or on depending on what code or test I am looking at. When Edge updated it was set to off, and now I cannot turn it back on. Does anyone know why it was removed and if there is a backdoor to turn it back on?

Thanks,

Allan

Microsoft Edge | Audio and video playback | Android

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
{count} votes

16 answers

Sort by: Most helpful
  1. Anonymous
    2023-03-13T19:50:38+00:00

    Hi Eric,

    Yes, it is still an issue in 110.0.1587.69. I'm quite surprised something like this has taken so long to fix.

    Allan

    2 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2023-03-13T21:20:00+00:00

    Thanks for checking in Eric, the problem still persists.

    I just updated to Version 111.0.1661.41 (Official build) (arm64) and sites needing WebGL still tell me it's disabled, and there is nowhere in the settings to enable it or hardware acceleration.

    Macbook Pro, 16 inch 2021

    M1 Max

    64gb

    Ventura 13.1

    0 comments No comments
  3. Anonymous
    2023-03-14T07:04:51+00:00

    Hardware Acceleration setting still missing in non ARM version

    Version 111.0.1661.41 (Official build) (x86_64)

    0 comments No comments
  4. Anonymous
    2023-03-15T16:29:12+00:00

    I wanted to let you know that our engineering team is still actively investigating the issue and working to find a resolution. Thank you for your patience.

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2023-03-18T22:02:56+00:00

    Just updated to Version 111.0.1661.44 (Official build) (x86_64) non ARM version still have the same problem!!

    4 people found this answer helpful.
    0 comments No comments