I've said this before but it bears repeating : when Chrome updates to a new version it installs a complete new set of files in a folder in Program FIles whose name is the current Chrome version, and a new instance of chrome.exe; the previous version gets renamed (I believe) to "old_chrome.exe". The last-but-one version's files are deleted, so you always have the current version+executable and a fallback version+executable in case there's a major problem in the new release and it won't run on your system.
Because the .exe changes (different file size and/or file hash) McAfee sees it as a new program requiring firewall permissions to be set as if for the first time. That's why you get the McAfee pop-up, that's why the default keeps getting reset to 'Outgoing'.
I also get the same problem a few weeks before. That is why I changed my AV for the meantime and will just switch back when this case has been resolved.
thank you for the detailed descirption of the problem.
however, the question remains; how do we fix this
As a few of the people have commented, it's easier to switch firewall software, than a browser you like & have set up.
Please let us know when this can be fixed - so we can go back to McAfee eventually.
Look forward to any resoluition.
I have the same problem.
I have to go to Firewall program access settings to re-open FULL access for Chrome. But McAfee keeps on re-setting to OUTGOING only. Extremely annoying.
I have added this back on our call agenda for Monday. Will posts what teh techs say.
Google Chrome had updated yesterday and I did get the McAfee new programme pop-up and clicked to allow, but it still only allowed Outgoing and blocked Chrome!
Yet again I had to change it back to Full.. Odd thing is that it does not block it immediately, it can be a couple of hours before Chrome stops working.
I also use Firefox and that was updated this week without problem, McAfee left access to Full.
About time this was fixed!!
Message was edited by: martin788 on 10/03/12 11:34:07 CST
I have a quick update to what Hayton mentioned here , so it’s clear that the update to Chrome is what triggers this issue which is not caused by McAfee .Moreover , Google Chrome performs their update more often so we have our back end team alerted on this and they are doing the best to contain this problem .
I shall update you once I have more info on the same . , Thanks for our co-operation
This may help;
I also use Firefox (latest ver.) with latest ver. of chrome.
I also use (HHS) Hotspot Sheild - http://hotspotshield.com/
which is a VPN tool to protect your data at hotspot wifi's.
I was able to track that down as the source of problem for chrome.
I installed HSS FireFox first, as firefox also had a cool ext. that automatically removed the banner ads that HSS forced.
Once I removed HSS - my chrome problem went away.
Firefox worked fine with McAfee both before and after HSS.
Hope this helps for users of HSS.
If anyone knows of a better - free - VPN tool on wifi's - that's fast - please let me know?
I am having this same issue and I find it occurs both when Chrome updates and after McAfee runs my weekly scan (I always have to change the Chrome Settings back to Full access afterwards). I would very much like to see this issue solved permanently so that I do not have to keep changing the access. Please keep us updated. Thank you.