540764 - Downgrade (some or all of the app files) after app upgrade due to ZoneAlarm Forcefield

Status: RESOLVED INCOMPLETE

(Toolkit :: Application Update, defect)

Description

[profklein]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.7 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.6) Gecko/20091201 Firefox/3.5.7 (.NET CLR 3.5.30729)

Suspiciously looks just like Bug 512334 for version 3.0.11.

Reproducible: Always

Steps to Reproduce:
1. Install Firefox 3.5.7
2. Restart Firefox 
3. If pop-up does not ask you to update, then go to Help and select Check for Updates.




Note that Help..About Firefox still shows Firefox 3.5.6 at the top, but 3.5.7 at the bottom.

Comment 1

[Matthias Versen [:Matti]]

Your Gecko Version is 1.9.1.6 but it should be Gecko 1.9.1.7.
Do you use security Software like Zonealarm forcefield ?
Any user changed settings in about:config with the filter useragent ?

Comment 2

[Robert Strong (they/them - no direct email)]

Please attach the last-update.log after this happens along with the updates.xml
file. If you've installed under program files these will typically be located
under %LOCALAPPDATA%\Mozilla\Firefox\Mozilla Firefox\ and the last-update.log is inside the updates directory.

The updates.xml may also be located in your installation directory and the last-update.log is inside the updates directory.

Comment 3

[profklein]

Do you use security Software like Zonealarm forcefield ?
Answer: Yes

Comment 4

[Matthias Versen [:Matti]]

Please read https://bugzilla.mozilla.org/show_bug.cgi?id=505961#c9

Comment 5

[profklein]

I thought about turning off ZoneAlarm Forcefield and installing Firefox 3.5.7; but decided against that. Reason: I uninstalled FF 3.5.7 via the Windows XP control panel, then installed FF 3.5.6 via its installation packet without problem. 

ZA Forcefield doesn't mess with FF 3.5.6, so why would it mess with FF 3.5.7? If it does, then there is something in FF 3.5.7 that is allowing it to.

I will try the update to FF 3.5.7 again and attach the logs as requested above.

Comment 6

[Robert Strong (they/them - no direct email)]

We've had other reports of Forcefield breaking app update. It appears to virtualize the file system which causes the updated files to be removed when the virutal file system is purged.

Links for reference
http://forums.zonealarm.com/showthread.php?t=72370
http://www.eweek.com/c/a/Security/ZoneAlarm-ForceField-Complicates-Browser-Security/

Comment 7

[profklein]

Well now... After reading that article, it sure sounds like I have been having a ZA Forcefield problem with other issues as well. Thanks for the link.

I tried to upgrade FF 3.5.6 to FF 3.5.7 via the Help...Upgrade Firefox. But when I clicked on the Restart Firefox button, I got the infamous Error message "Platform version '1.9.1.6' is not compatible with minVersion >= 1.9.1.7 maxVersion <= 1.9.1.7"

The update partially took because in %LOCALAPPDATA%\Mozilla\Firefox\Mozilla Firefox\updates directory the file update.version has 3.5.7 in it.
I will upload the update.log and update.manifest files.

Comment 8

[profklein]

Attachment: update.log for 3.5.7

Comment 9

[profklein]

Attachment: update.manifest for 3.5.7

Comment 10

[Robert Strong (they/them - no direct email)]

That definitely appears to be caused by Forcefield... all files were updated correctly according to the logs.

Comment 11

[profklein]

Attachment: update.version for 3.5.7

This bug may be OBE'ed since version 3.6 has been released.  I will uninstall 3.5 and install 3.6 and see what happens.

Comment 12

[Robert Strong (they/them - no direct email)]

I highly suspect that Forcefield will cause the same issue with all versions of Firefox including 3.6

Comment 13

[profklein]

I checked my settings in ZA Forcefield and I had virtualization turned off. I remember now that I turned it off because of one the problems mentioned in the article mentioned above. But that still does not mean that ZA Forcefield won't blow up Firefox.

This time I logged on as Administrator to install FF 3.6 with ZA Forcefield still on (virtualization turned off). Launched FF 3.6, browsed around a bit with no problems, logged off, logged back on as myself, launched FF 3.6 and KABOOM..it didn't have access to some dll. Unfortunately, I uninstalled it before writing it down and reinstalled it with my normal logon. However, it did send a bug report to CheckPoint.

But, if problems persist, I will turn ZA Forcefield completely off.

Comment 14

[Robert Strong (they/them - no direct email)]

Confirming based upon other bug reports and forum posts.

Comment 15

[Robert Strong (they/them - no direct email)]

We'll track the problem with upgrading with ZoneAlarm Forcefield in this bug

Comment 17

[Robert Strong (they/them - no direct email)]

Note: we've reached out to Checkpoint on this issue... no reply as of yet.

Comment 18

[Dr B W Darvell]

I have just updated ZA with zaSuiteSetup_91_507_000_en.exe and FF (3.6.3) failed to run, apparently as above.  Turning off ForceField was not available, switching off antiphishing had no effect, disabling the service wrecked ZA.  Uninstalling ZA has had no effect!  FF runs in SafeMode, but in normal mode.  I have reported it to ZA support, but nothing yet. Reinstalling FF also has had no effect.  3 days of rebooting and various attempts to work around and analyse has produced no clues, but at one point Windows Firewall was ON - which I have never done deliberately. Registry has been purged of as much ZA stuff as I can, but there remain entries I cannot delete. This is a real pain - I am having to use IE for this!

Comment 19

[Dr B W Darvell]

error: FF runs in SafeMode, but NOT in normal mode.

Comment 20

[Matthias Versen [:Matti]]

>error: FF runs in SafeMode, but NOT in normal mode.
If you mean the FF safemode and nor the windows one:
The Firefox safemode disables only installed addons and Themes. A difference between both options means that one of your installed addons is causing the issue. Disable all addons in Tools/addons/extensions.

Comment 21

[Dr B W Darvell]

I meant that FF runs in Windows Safemode, FF Safemode does not work either.  Sorry for the ambiguity.

Update: I created a new user ... Administrator ... FF does not run there either!
But, if I go back to my usual Admin account (rebooting, again), I can use "Run As" that new user to run FF from the Start menu shortcut with no problem (I am using it for this)- except that I do not have my bookmarks etc, of course.  There are no addons, of course, either.
If I cannot start FF in the account (i.e. as that user) with the problem, how can disable the addons???

Thanks.

Comment 22

[Dr B W Darvell]

Further update:
FF will not "Run As" me (original user) when the box "Protect my computer and data from unauthorized program activity" is unticked.

Comment 23

[Dr B W Darvell]

- or ticked.

Comment 24

[Dr B W Darvell]

Changing the folder name "extensions" under my profile to something odd has no effect.  I assume the addons would not be the problem, therefore.

Comment 25

[Dr B W Darvell]

Firefox -profilemanager will not "Run".

Comment 26

[Dr B W Darvell]

renaming my profile folder has no effect.
deleting the last traces of ZA / Checkpoint / ZA toolbar has no effect ... registry and folders.

Comment 27

[Dr B W Darvell]

Disabled all addons while in Windows Safe Mode (FF working fine there, bookmarks and all).  No-go in normal mode.
Reinstall FF ... does not launch from the installer.
:
Now this is bizarre... being left without a firewall, I installed first PCTools ThreatFire, then Comodo free firewall (max. protection option.)  Before I could reboot, ThreatFire automatically opened default-browser Firefox (for the tutorial)!  
I could open a second instance of FF, no problem.
Re-enable all addons, restart FF - OK.
Reboot ... nothing.  Completely blank screen - with a cursor.
Ctrl-Alt-Del brings up Task Manager, no Explorer ...  Damn
All down to updating ZA ... grrr

Comment 28

[Dr B W Darvell]

Well, after several more reboots, a BSOD, and some more pain, it now all appears to be working again.  FF is fine.  All add-ons enabled.  
Overall, I am convinced it was the ZA update that was the problem, but there is clearly something weird that needs to be reset to allow FF to run at all ... I have no idea what that is.  
It is the lack of a diagnostic that is the problem here, perhaps.
No immediate action required, but the sensitivity is perhaps a worry that needs investigating.  I have no hopes of CheckPoint being able to comment constructively.

Comment 30

[Robert Strong (they/them - no direct email)]

Closing old bugs as incomplete. If this is still an issue please file a new bug.