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

After updating to 15.0.1 Firefox opened from C:\Program Files (x86)\Mozilla Firefox\updated\firefox.exe

  • 1 பதிலளி
  • 25 இந்த பிரச்னைகள் உள்ளது
  • 1 view
  • Last reply by amezri

After updating to 15.0.1 this afternoon on a Win 7 64-bit machine, I restarted Firefox. Immediately Comod started showing warnings that firefox.exe was not a recognized program and was asking to access plug-in container, SVC host, and other things. Weird. So I look in Comodo and Explorer and it says the process is running from this path:

C:\Program Files (x86)\Mozilla Firefox\updated\firefox.exe

Except there is no Updated folder. This happens even when clicking the firefox.exe file in the Mozilla Firefox folder.

Is this normal?? It seems not correct.

After updating to 15.0.1 this afternoon on a Win 7 64-bit machine, I restarted Firefox. Immediately Comod started showing warnings that firefox.exe was not a recognized program and was asking to access plug-in container, SVC host, and other things. Weird. So I look in Comodo and Explorer and it says the process is running from this path: C:\Program Files (x86)\Mozilla Firefox\updated\firefox.exe Except there is no Updated folder. This happens even when clicking the firefox.exe file in the Mozilla Firefox folder. Is this normal?? It seems not correct.

தீர்வு தேர்ந்தெடுக்கப்பட்டது

Nevermind. I restarted the computer and everything seems to be back to normal - firewall and paths are correct now. So.. anyone having this problem - try restarting the machine. Never had to do that after a Firefox update before so didn't think of it.

Read this answer in context 👍 15

All Replies (1)

தீர்வு தேர்ந்தெடுக்கப்பட்டது

Nevermind. I restarted the computer and everything seems to be back to normal - firewall and paths are correct now. So.. anyone having this problem - try restarting the machine. Never had to do that after a Firefox update before so didn't think of it.