Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Meer info

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Blank context menu with Hardware Acceleration

  • 2 antwoorden
  • 2 hebben dit probleem
  • 1 weergave
  • Laatste antwoord van FredMcD

more options

I have a severely irritating problem: After reinstalling Windows 10 the right click menu in Firefox is blank when hardware acceleration is enabled. It still functions, and you can click on invisible menu items, you just can't see anything.

This only started happening after reinstalling everything on a new hard drive, I've never had this problem before in 10+ years of using Firefox. Disabling hardware acceleration is not really a "fix", it just results in a crappy browsing experience, with rough scrolling and screen tearing.

Both Firefox and graphics drivers are fully up to date, I've even tried multiple older versions of both. Tried Firefox without addons and it still occurs.

I need to know how to resolve this without sacrificing Hardware Acceleration.

I have a severely irritating problem: After reinstalling Windows 10 the right click menu in Firefox is blank when hardware acceleration is enabled. It still functions, and you can click on invisible menu items, you just can't see anything. This only started happening after reinstalling everything on a new hard drive, I've never had this problem before in 10+ years of using Firefox. Disabling hardware acceleration is not really a "fix", it just results in a crappy browsing experience, with rough scrolling and screen tearing. Both Firefox and graphics drivers are fully up to date, I've even tried multiple older versions of both. Tried Firefox without addons and it still occurs. I need to know how to resolve this without sacrificing Hardware Acceleration.

Gekozen oplossing

Never mind, I've found the cause... somehow this was being caused by the MSI Gaming App.

Dit antwoord in context lezen 👍 0

Alle antwoorden (2)

more options

Gekozen oplossing

Never mind, I've found the cause... somehow this was being caused by the MSI Gaming App.

more options

That was very good work. Well Done.