FF on Win10 crashes on startup; won't start and crashes in troubleshooting mode startup
I'm on Win10. This morning I see that MSLOP has updated my desktop PC overnight. FF was open before the update and attempted to restart but couldn't restore pages. I told it to start a new session and the PC blue screened. This has happened before so after the PC restarted I shut it down. It blue screened a few times while also trying to restart FF. I shut it down with the power button. FF will not start with troubleshooting (shift while double clicking on FF icon). It crashes and I get the crash window. Latest crash detail is below. What next? Any help is much appreciated.
UPDATE: I went to windows settings, apps, and clicked on uninstall for FF. Immediately a message box, "Would you like to refresh instead?" popped up. Sure, why not? It thought for a while and updated. I logged in again and I am back to a functioning 147.0.3. I logged into my bitwarden extension and ublock origin is still there. No clue what happened earlier.
由 dave101 於 修改
被選擇的解決方法
I went to windows settings, apps, and clicked on uninstall for FF. Immediately a message box, "Would you like to refresh instead?" popped up. Sure, why not? It thought for a while and updated. I logged in again and I am back to a functioning 147.0.3. I logged into my bitwarden extension and ublock origin is still there. No clue what happened earlier.從原來的回覆中察看解決方案 👍 0
所有回覆 (3)
Hi,
Thank you for sharing the solution! Let me post it as a separate reply and mark accordingly.
選擇的解決方法
I went to windows settings, apps, and clicked on uninstall for FF. Immediately a message box, "Would you like to refresh instead?" popped up. Sure, why not? It thought for a while and updated. I logged in again and I am back to a functioning 147.0.3. I logged into my bitwarden extension and ublock origin is still there. No clue what happened earlier.
由 Denys 於 修改
Thanks, Denys. It's interesting that there is more than one path to refreshing FF. The crash window and troubleshooting paths didn't work but the uninstall path did. I'll have to remember that the next time MSLOP drops a grenade in my desktop.