Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

Firefox won't let me open Apps after closing

  • 1 reply
  • 0 have this problem
  • 27 views
  • Last reply by Mangoman25

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

All Replies (1)

Mangoman25
Mangoman25 Question owner
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.