חיפוש בתמיכה

יש להימנע מהונאות תמיכה. לעולם לא נבקש ממך להתקשר או לשלוח הודעת טקסט למספר טלפון או לשתף מידע אישי. נא לדווח על כל פעילות חשודה באמצעות באפשרות ״דיווח על שימוש לרעה״.

מידע נוסף

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

  • 1 תגובה
  • 25 have this problem
  • 1 view
  • תגובה אחרונה מאת amezri

more options

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

כל התגובות (1)

more options

פתרון נבחר

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.