Firefox 技術支援討論區

I just did the most recent Windows 10 updates:

KB5037768, KB5038350, KB5001716

My version is 22H2 for x64 and .Net 6.0.30

Upon finishing the update and rebooting, Firefox gave me the PR_CONNECT_RESET_ERROR on all websites. Not other browser was having an issue. I've tried all the troubleshooting steps I can find. Is there an error fix based on what I am describing that I can now try?

Thanks!

Today I noticed that typing characters with accents like á, ã, â, etc. doesn't seem to work at all from firefox, they all end up ignoring the dead key and just typing the letter itself. It can render them just fine and I can paste them from another app normally too, but actually typing them is impossible from firefox.

After trying to troubleshoot, I eventually found out a few things: - iBus is not at fault, since it works in every other app and I even restarted it, but the problem persists - This only happens in my main profile, newly created profiles don't have that problem - The problem still happens on troubleshoot mode (as long as it is my main profile) - Compose key also doesn't work (I don't want to use compose key anyway, because my keyboard has specialized dead keys, but I at least tried it)

I suspect the problem lies in a setting on about:config that's different from newly created profiles, but I have no idea which and Ctrl+F searching this site doesn't show any relevant configuration that might be the culprit.

Every time I start up firefox, it takes about a full minute to load. It shows an outline of the UI, but does not become usable for a while, windows also puts up a "firefox is not responding" window when the window is interacted with. After loading, opening a new window is unaffected, and page loading is snappy. just the initial launch is the issue. This remains true even after a clean uninstall + reinstall. Appdata folder was removed as well, and did not affect the issue. I do not have any antivirus software other than windows defender, so that should not be an issue. My hardware is also not likely to be at fault, as it is sufficiently up to date (upgraded within last year, not sharing specs here). Chrome starts up in less than a second for reference. Once again, a fresh install with a new profile has the same symptoms. Have tried every available guide to no effect.