Windows 10 will reach EOS (end of support) on October 14, 2025. For more information, see this article.

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.

Disabling NoScript bricked my profile

  • 2 replies
  • 0 have this problem
  • 5 views
  • Last reply by Goldstein

Goldstein
Goldstein
more options

I previously had the NoScript extension. I disabled it in preferences and restarted Firefox. It seems like one of these moz-extension:// windows were open at the time, so when I try to launch Firefox, it tries to re-create moz-extensions:// windows and dies. 

I can’t start Firefox. I can’t start Firefox in --safe-mode. I’m happy to provide any debug info needed.
I previously had the NoScript extension. I disabled it in preferences and restarted Firefox. It seems like one of these moz-extension:// windows were open at the time, so when I try to launch Firefox, it tries to re-create moz-extensions:// windows and dies. I can’t start Firefox. I can’t start Firefox in --safe-mode. I’m happy to provide any debug info needed.

Chosen solution

I actually remembered that I do daily backups and restored my profile. I’ll try to reproduce this and file a proper bug though. Thanks!

Read this answer in context 👍 0

All Replies (2)

cor-el
cor-el
  • Moderator
more options

Do you need to retain tabs because if not then you can remove sessionstore.jsonlz4 in the Firefox profile folder to get a clean start ?

You can replace sessionCheckpoints.json in the profile folder with a sessionCheckpoints.json file that only contains "{}" (without the quotes) to get the about:sessionrestore page and select what to restore.

Goldstein
Goldstein Question owner
more options

Chosen Solution

I actually remembered that I do daily backups and restored my profile. I’ll try to reproduce this and file a proper bug though. Thanks!