Since FF version 50 was released, I have been experiencing periodic corrupted profile notices from the AVG security suite for downloads via the browser. This has occurre… (read more)
Since FF version 50 was released, I have been experiencing periodic corrupted profile notices from the AVG security suite for downloads via the browser. This has occurred for all downloads since December 2016 from various software vendors eg, Corel, AVG and Adobe, supplying their code via compressed exe files. Downloads from those sites using specialist stub installers did not have this issue. I attach a screen shot of that latest notice regarding an Adobe flashplayer update yesterday
One of the notices was about an AVG download. so, I've referred that AVG notice to AVG and they confirmed that there was no corruption in the related file, and there's been no evidence of any mal-operation for the other items affected over the last 4 months. So it seems clear that the profile stored in the FF browser folder (see image) is the one which has the broken signature.
In January when this issue was really noticeable, I found a discussion regarding a changed method of computing the digital signature in FF version 51 - coinciding with these events. Unfortunately, that discussion thread has been removed or otherwise lost in the changes to the website, because I cannot find it now.
Looking for that discussion page, I've just noticed that there is a 64bit version of FF available. And (since I ran 32bit FF for years before upgrading to a 64bit motherboard, and after the upgrade just restored the various files from backup), the code differences arising from running a 32bit version of FF (now 52.0.2) on a 64bit cpu might be the cause of this.
So, before I lodge an issue regarding this tell me how I upgrade the 32bit version of FF to a 64bit version without a complete re-installation and all the pain re user interfaces that entails