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’.

Learn More

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

Firefox won't let me open Apps after closing

  • 1 antwoord
  • 0 hebben dit probleem
  • 27 weergaven
  • Laatste antwoord van Mangoman25

more options

For a while now, I had the issue of apps on Windows 11 opening very delayed (approx. 10-15 seconds after the input) on irregular occasions. I was now able to figure out that Firefox seems to be the cause of the problem. Whenever I close Firefox (and thus move to another program), I'm unable to open any other app for a couple of seconds. Task Manager shows three Firefox background processes that only show upon closing it. Only when they disappear, the apps I clicked on finally open. I've tried reinstalling and cleaning Firefox, but nothing changed.

As said, I'm on Windows 11 with a i5-13600k and Firefox is installed on an SSD. I couldn't really find any information on this problem.

For a while now, I had the issue of apps on Windows 11 opening very delayed (approx. 10-15 seconds after the input) on irregular occasions. I was now able to figure out that Firefox seems to be the cause of the problem. Whenever I close Firefox (and thus move to another program), I'm unable to open any other app for a couple of seconds. Task Manager shows three Firefox background processes that only show upon closing it. Only when they disappear, the apps I clicked on finally open. I've tried reinstalling and cleaning Firefox, but nothing changed. As said, I'm on Windows 11 with a i5-13600k and Firefox is installed on an SSD. I couldn't really find any information on this problem.

Alle antwoorden (1)

more options

Forgot to mention: Additionally when opening, Firefox shows only a white screen and the Windows "loading mouse cursor" for like 5 seconds before functioning properly. This happened first only a couple of days ago while the issue described in the original post appeared before that.