The Mozilla Maintenance Service updates Firefox in the background and saves its files initially in the updated folder, so this folder has a complete installation of Firefox once the update is fully downloaded and applied.

• https://support.mozilla.org/kb/what-mozilla-maintenance-service

This makes it possible to restart Firefox quickly without the need to update files when restarting, but merely replace all files which is a very quick process.
It sounds that your firewall is detecting the Firefox.exe program in the updated folder and not the Firefox.exe program in the main Firefox program folder after Firefox has been restarted.

Hi cor-el :)

Thanks for your interest and advice. Perhaps you can advise a workaround

I do not know how to stop my Comodo Firewall thinking this. I assume Comodo Firewall is fooled into replacing all my Aurora folder permissions with the Aurora\Updated\.. files and is unable to pick up the files being copied to the Aurora folder.

To be honest It seems to be an Aurora update quirk that fools Comodo FIrewall (a very respected and widely used Firewall) because ONLY Aurora (occasionally Beta) updates are challenged and no other update of my many apps.

Does this explain the Registry entry for "...\intellipoint\appspecific\.." I mentioned because I cannot see a connection between that and what Comodo Firewall thinks? as that entry changes when Aurora opens (if I have used Beta) immediately which suggets to me that Aurora changes it to the "Updated" path (and NOT Comodo Firewall)

ANYWAY cor-el I accept that the Maintenance service update is the issue and I agree with you. Thanks for pointing this out.

How can I work around this? Today I ran Aurora, went straight to the Help section and saw it was starting to auto-update so I immediately closed Aurora and downloaded the latest Aurora (GB version) from the website and installed it. No Firewall issues ensued.

Now what I wish to ask you please is: IF I reset Aurora update options from "automatically Install updates" to "Check for updates but let me choose when to install" When I elect to install an update would that then update as auto-update does (via an "Updated" folder) or would it do a new conventional full download and install direct to the main Aurora folder?

If your reply is it will still update via an "Updated" folder please can you advise how I can make settings to let me know when there is an update available BUT download the FULL update file currently "http://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-mozilla-aurora-l10n/firefox-29.0a2.en-GB.win32.installer.exe" so it will install directly over the existing files in the Aurora folder.

If that is not possible should I tick the "Never check for updates" which I am loathe to do for obvious reasons.

What is the "use a background service to install updates"? Is that the Maintenance Service?. If I UNTICK that but keep "TICKED ""Automatically Install updates" would Aurora do a normal FULL conventional (slightly slower) rather than using the Updated Folder method).

My apologies for the questions. I am not worried about an install taking slightly longer IF I no longer have my firewall thinking files are in the non existent "Updated" folder"

I hope I asked questions clearly cor-el and I am sorry if not.

Many thank cor-el

Dave

ps I must admit I am unsure why so many moan about the new Australis GUI. I like it very much. The ONLY small thing I did not like and have changed via an Stylish script add-on ' 'is to move the "Open Menu" Square button from Right to Left as BEING LEFT handed (and used to previous Firefox GUIs) I have got used to and like this being on the Left and open opening options on the left side.

If I was making an Aurora GUI suggestion I would suggest that the programmers give users an option to choose Right or Left (rather than needing a Stylish script) to do that.

Yes, "use a background service to install updates" is about using the Mozilla Maintenance Service to download and install updates, so removing the tick in that box might help or move the problem elsewhere as the files still need to be downloaded and saved.

Did you try to remove all Firefox (Aurora) rules in the Comodo firewall to see if letting Comodo create a new rule has any positive effect?

Hi cor-el,

Once again I thank you for you time and assistance and it is MUCH appreciated.

I have a couple of extra useful (I think) observations today.

1) Yesterday I DID decide to untick "use a background service to install updates" and I ticked "Check for updates, but let me choose whether to install them"

2) Today when I opened Aurora it dutifully advised me an update was available and asked if I wanted to update. Before I said Yes I clicked the on show more info link, which went to the Aurora download page (where I could have chosen to download the full upgrade) but I did not, as I wanted to see if the Updated folder method would be used with "use a background service to install updates" unticked.

3) I went back to the Aurora update window and updated via it. UNFORTUNATELY (for me) that DID install files to an "Updated" folder 'which I could see' via Windows Explorer.

4) I then went immediately into my Comodo Firewall and looked at the "Trusted Files" section (where all Firefox files rules go for release, beta or Aurora). NOW that WAS interesting because all the Aurora entries had now had their paths changed from "C:\Program Files (x86)\Aurora\" to "C:\Program Files (x86)\Aurora\Updated\".

5) I then opened Aurora and Comodo Firewall immediately challenged many it and several Aurora actions and files. I noted (via windows Explorer) that the Updated folder had now disappeared (no doubt because the Aurora updated all the "C:\Program Files (x86)\Aurora\.." files as needed and deleted the Updated folder afterwards.

6) I looked at Comodo Firewall and it STILL pointed to the "UPDATED" folder.

7) (To test what would happen) I then downloaded the full update from the Aurora Web page and installed it OVER the (just) updated version.

This time there were NO Comodo Firewall challenges when I opened Aurora AND importantly the "Trusted Files" section of Comodo Firewall had now changed to the Normal path for Aurora "C:\Program Files (x86)\Aurora\"

CONCLUSION:

) You may not agree with me cor-e, but l believe the Aurora update method of using an Updated Folder is at fault and NOT Comodo Firewall'.

I think this because it appears the Aurora update is installing to the update folder which Comodo Firewall recognizes and as Mozilla is a Trusted supplier it accepts the new path and overwrites the original (this I believe is correct functioning by it). Unfortunately it does not know (and it is apparent the Aurora does not tell it when Aurora opens and completes the update) that all needed updated files have been copied to the main Aurora folder, the Updated and its contents all deleted and that the Firewall should revert to the main "C:\Program Files (x86)\Aurora\".

I feel the Update is at fault and should not mislead Comodo Firewall into thinking the Updated Folder is NOW the correct folder for Aurora. If the update cannot avoid this, then when Aurora opens after installation it should tell firewalls to overwrite the Aurora rules pointing to the Updated folder and replace them with the rules pointing to the Main Aurora folder

There is clearly something unique (and problematic) about the Maintenance Service method of updating via the updated folder that no other application or Windows updates on my PC use as NONE of them trigger Comodo Firewall challenges after updates.

You asked "Did you try to remove all Firefox (Aurora) rules in the Comodo firewall to see if letting Comodo create a new rule has any positive effect?:

Yes I had tried that days ago and I think by my above info that the Maintenance update method is causing Comodo Firewall path changes (and not Comodo having incorrect path initially.

I feel this is a Maintenance Update Bug to be honest cor-el as it should AVOID triggering a (Comodo) Firewall into think the Updated Folder is the new path for Aurora.

Any views or suggestions cor-el Kindest Regards Dave

PS I am not alone JUST found this from Aug 2012 when doing Google search for Comodo Firewall and Aurora http://forums.mozillazine.org/viewtopic.php?f=23&t=2521703

The Firefox program as present in the updated folder has and will never run, so there shouldn't be any requirement to create a rule for the exe files in that folder. Comodo should wait before a program is actually started before creating a allow or accept rule for a specific program.

Does this happen with the beta release as well?

• https://ftp.mozilla.org/pub/mozilla.org/firefox/releases/

Hi YES it does, HOWEVER in the past Most (not all) Beta auto updates did not trigger Comodo Firewall problem (BUT occasionally did) and I resolved the same way (namely uninstalling and installing a full install.

I do not know if having Aurora AND BETA both installed causes any conflicts regarding this issue

I am NOW going to uninstall Maintenance service, Beta and Aurora retaining only my add-on and preferences. I will delete all Comodo rules for them Then I will download an older update of both Beta and Aurora and see what happens

Will report back in 30 mins

OK reporting back as promised.

Firstly on looking closer at Comodo Firewall "Trusted Files" (which I do not set for Aurora or Firefox are created when these browsers are installed) I realize the (updated folder) for each does not replace the main folder but are there AS WELL.

I am NOW thinking that Comodo is NOT challenging the updated Firefox b'ecause it has rules for both main and updated folder (until I purge). The reason it is being triggered is because the Comodo Firewall knows that the the updated aurora upon opening seem to reference the non existent Updated folder and file within that do not exist.

To be honest I am confused what the source cause is cor-el and have no idea to resolve this rather than the workaround I use (unsatisfactory but much better than having to keep answering multiple Comodo Firewall alerts after every update.

For me it IS the Firefox Update (via Updated folder) method used by Beta and Aurora (probably Release as well but I never use Release) and NOT anything to do with Comodo Firewall

BECAUSE

Doing a full update version install for Beta or Aurora OVER the existing version results in NO ISSUES.

AND

All other app installs and updates work on my PC with Comodo Firewall perfectly

AND

the Firefox Update (via Updated folder) uses a special update method then it seems "all road lead to Rome" as they say.

Regards, Dave

Hi cor-el  :),

I think you have moved on to other issues, however I've found a good workaround that works (for me at least) and that that has invisibly worked with the last 3 daily updates without my manual intervention.

I originally tried unticking the "use a background service to install updates" but that did not work out as you know. What does seem to have worked was: 1) uninstalling completely the "Mozilla Maintenance Service" (via Control Panel > Programs & features). 2) I then did a full update of the latest Aurora update at the time (ensuring the Mozilla Maintenance Service was not reinstalled - which I was not) AND I noted the "use a background service to install updates" option was no longer visible or offered in the Update Options.

I kept the update set to automatically update and as I said in the first sentence I have now had 3 Aurora updates without any Comodo Firewall Alerts  :)

I have updated this post as you have kindly bothered to try and help (AND DID) by pointing me to the "Mozilla Maintenance Service" and in case others experience the same issues (be they with Release, Beta or Aurora) as they will now be able to see what hopefully may work for them, as it has for me (  ;) so far )

Kind Regards Dave