
Install error - Windows 7 64bit
Install error - Windows 7 - 64bit
Hello,
I my previous install of Firefox kept crashing. So I eventually tried to uninstall it and reinstall it, hoping that would solve the problems I was having. It would not install again. I kept getting a error message that Firefox was currently running in the background and that I needed to close it before the install could proceed. I opened the task manager and saw that "firefox.exe" was still running. I stop it, and try to check and see if it's still listed in the installed programs menu, and it's not even listed.
I'm not sure whats going on, But I would like to use firefox again. I have been using chrome for a long time now. Any help would be appreciated.
All Replies (8)
Hi StOmPeR, there are two places that Firefox typically would be installed:
- C:\Program Files\Mozilla Firefox -- 64-bit programs folder
- C:\Program Files (x86)\Mozilla Firefox -- 32-bit programs folder for 64-bit Windows
Could you check both of those to see whether that is where your existing Firefox is located?
Please note: if you run Microsoft Office (local install), deleting a program folder can prevent Office from opening links. You can switch your default browser to Internet Explorer and let Office use it once to work around this issue. Or see: https://www.slipstick.com/problems/this-operation-has-been-cancelled-due-to-restrictions/
Yes Thank you for your response. I forgot to look for the local folders, Deleted everything I could find under Programs and Programs x86. Even the shortcuts. Restarted, and tried to run the Firefox installer again, and got the same error message. It says "Firefox is already installed. Let's update it." And asks me to restore default settings and remove old add-ons for optimal performance.
If the Firefox installer will run, I think we should let it run and "update" the installation of Firefox.
Then if you can start Firefox, you can find the program location using the Troubleshooting Information page. Either:
- "3-bar" menu button > "?" Help > Troubleshooting Information
- (menu bar) Help > Troubleshooting Information
- type or paste about:support in the address bar and press Enter
In the first table on the page, the Application Binary row should show the install location.
If firefox.exe is still running in the Windows 7 Task Manager, on the Processes tab, add the "Command Line" column (I think the column chooser is on one of the menus, or if you right-click any existing column heading, you might be able to open it from there). That should show the install location of running processes.
That's just it, it won't run, It says That the currently running copy of Firefox needs to close before the installer can proceed. So nothing happens
StOmPeR said
That's just it, it won't run, It says That the currently running copy of Firefox needs to close before the installer can proceed. So nothing happens
Okay, can you check here:
jscher2000 said
If firefox.exe is still running in the Windows 7 Task Manager, on the Processes tab, add the "Command Line" column (I think the column chooser is on one of the menus, or if you right-click any existing column heading, you might be able to open it from there). That should show the install location of running processes.
Where is the mystery Firefox running from?
I did what you suggested. It showed it was in the same folder I just deleted. After deleting the folders again, and every instance of Mozilla or Firefox I could find, I then tried to manually navigate to find the 64bit windows version of the installer to download. Hoping that would fix the problem. I then restarted, and opened the installer. This installer gave the exact same error. "Firefox is currently running and needs to close before proceeding." I open the task manager and there it is running again.
I have no idea what is causing this.
Modified
Oh, I don't see how it could keep running if it was deleted, but if you right-click > End Task/Process on the process, does it go away?
Correct, I don't either. It goes away, and the moment I start the install it comes back. It's there's something wrong with the registry or something. That would be the only thing I can think of that would cause such a problem.