I’m not a computer expert,but I now know that the Firefox program consists of MANY individual files,including the file that allows it to connect to the web.I can only assume that this file got corrupted during the last Firefox update a few days ago. Luckily,IE is still working,so I deleted the Firefox program and downloaded the current version. It works fine and I downloaded and use Firefox-,until a couple of days ago. So he sold me a newer computer with Windows7 loaded……. The repair man said”My computer was too old and outdated”. I could not go on-line using XP to download a new version of Firefox as even IE would not connect to the Internet on my old XP computer. I used the Firefox browser on both computers. I know its an old thread-but feel I must add my comment!.This problem has caught me out twice,once using Windows XP about 18 months ago,and again this week using Windows7 on a fairly new computer. In my case, the most likely explanation is that the most recent Nightly update somewhat got things messed up so that some files were not updated correctly. I still do not know what caused the issue in first place. If you are experiencing pgort100.dll or XPCOM related error messages in Firefox during start, try installing the browser anew. That's to be expected as yo deal with beta and development software. If you run Nightly or Beta, chance is that you will receive versions every now and then that have issues. Note: As I mentioned earlier, this fixes the issue only if the actual Firefox version that Mozilla pushed out is not buggy. Download the latest Firefox installation file from Mozilla and install the web browser over the existing installation to fix the XPCOM error.Restart the PC and try to load Firefox again.In short, here is what you may want to do: I then launched Firefox and lo and behold, the XPCOM error was gone and the browser did start up like usual. I downloaded the latest Firefox Nightly build and installed it to the same directory that the previous installation was installed in.
I knew that the issue would not be solved if it was an issue of the latest Nightly build, and not a local issue that only I was experiencing.
0 kommentar(er)
