Is Windows XP SP2 the 32-bit version which was followed by Windows XP SP3 or is it the 64-bit Windows XP SP2? I would guess this would refer to the 64-bit Windows XP and, if that is the case, there is no need for me to rush to update Avast.
Thanks David. Am I pleased to read that! I’ve just got home after driving on an 80 mile round trip to install AVAST 2015 R3 (2015.10.3.2223) on a friend’s Windows XP SP3 system.
It’s hard to believe that there are still Windows XP 32-bit SP2 systems extant. Do the POSReady updates work on SP2?
I honestly don’t know - the point was that this takes XP beyond SP3 - so there is no way of telling if being up to date (SP3) would be a prerequisite or not.
AS far as I’m aware the SP3 update should still be downloadable and that is what I would suggest as a start point for those still using XP SP2. Then they would be able to take advantage of the additional functionality in avast 2015 R3 SP1.
Personally I haven’t gone for the workaround of POS Updates, A.K.A XP SP4.
@ zgy3073
Changing the Topic subject shouldn’t be done as anyone responding to your post would end up with that the subject and would confuse the topic.
I have no doubt that this topic will grow and very soon your post would become buried, I would suggest creating your own new topic and post a link to it in your current post.
Intel 925 duo core vista 32bit with 2GB ram. having lockups where the computer just stops responding while browsing, no HDD activity, the keyboard and mouse no longer responding, whatever is on the display remains, and clock stops indicating time advancing. Have given computer up to 30 minutes and it never came back without power boot. The lockups are not consistent, they occur sometimes after only a few minutes of operation to 10 hours later but always while browsing. I have disabled Secure Virtual Machine. I will know more after a few days of operation whether this is a fix.
Updated to 2015 R3 SP1 from 2015.10.2.2218 using clean install with avastclear.exe.
No issues to report at all on Win 7 Home Premium 64-bit, other than a issue where an old expired license (2014) was available and inserted, which of course failed to take. Found a spare copy of 2015 license and good to go. In defense, it was not obvious this was an old license until explorer settings were changed to “Details”.
Only one setting change from .2218 version: Settings>WebShield>Main Settings>“Do not scan trusted sites” was ticked on by default, unticked that because all sites should be scanned when opened. Does affect browser navigation speed (slows it down) but any site can be clean one moment and dirty the next.
Updated fine from within the GUI from 2223 to 2225 … all ok … only thing, Avast coders should fix the installer, so it cleans up the leftover update folders from the computer. Just about all of them are empty and they just take up space for no reason.
I’ve been using Avast successfully for many years. Normally it’s excellent! But I installed vers. 10.3.2225 yesterday and it has corrupted my old XP workhorse. The symptoms are: (1) Avast states some shields are inactive; (2) the webshield is inactive but cannot be acivated as setting it ON is ignored; (3) eventually (and usually when starting a browser - say chrome) the PC hard stops (mouse & keyboard don’t work) leaving only power off as a procedure.
I have no ideas of a workaround for this except removing Avast clears this bug (as proven three times).
I am having no trouble with my Windows 7 PC & Notebook and this version of AVAST.
Just to confirm that I too, amongst the many it seems, have to keep XP running for legacy systems that do not work correctly in Windows 7. Whether they work in W8/8.1 or 10 is immaterial. I hope that Avast can solve this issue and continue to support us XP users into the future.
Hi busp1,
I have the exact same problem with my Vista machine. I believe that my random lockups started after the last round of Windows updates on 7/14.
So far I have rolled my Firefox browser back to version 37 and uninstalled then reinstalled Flash Player. Now I am running with Flash disabled, but I still get the random freeze/lockup.
I have just uninstalled all of the Windows updates from the 14th. Now I am waiting to see if the lockup returns. I don’t think this is an Avast problem.
Update:
I got another freeze/lockup, so now I have uninstalled my Avast Free and reinstalled it from a fresh download. Currently waiting too see if this fixes the problem.
Update #2:
Still got a freeze/lockup. I made it 2 days before the lockup. Now I have rolled back to Avast Free 2015.10.2.2215. Let the test begin again.
Updated version .2224 from GUI to version .2225. Update for win7 and win10 was smooth, reboot and subsequent operation were uneventful.
For my systems just perfect! 8)
With regard to Troika’s post: ‘Vers. 10.3.2225 corrupts my 32 bit XP’
I had problems getting 10.3.2223 to work with Windows XP SP3 when OnlineArmor was installed. I found that Avast 10.3.2223 was in conflict with OnlineArmor. Removing OnlineArmor cured the problem and Avast is presently running nicely with Agnitum Outpost Firewall free 2009.
I also found that 2218 would not run at all with Windows XP SP3 so had to stick with 2215 until 2223 became available. This issue had nothing to do with OnlineArmor because it occurred on systems on which OnlineArmor was not installed.
Thankyou “hake” for your response that proves perhaps how complex this issue maybe.
Firstly I confirm I am running XP SP3 with Private Firewall 7.
After my posting about 2225 I installed 2223 and got the same issues.
I have just now installed 2218 and Avast is causing no problems - the issues I mentioned with 2223/5 are no longer.
Whether there is some conflict with Private Firewall 7 I do not know, and I am reluctant to remove it to test as it has taken long enough to enter my array of trusted IP addresses for my nets. However turning the firewall OFF was of no help. I moved to PF7 from ZA as that became bloatware in my opinion and reduced my PCs (especially the XP) to a snail’s speed without the urgency.
I hope both your’s and my experiences with the latest AVAST releases might give some clue(s) as to the fundamentals of these issues.
Hi. I’ve updated my Avast to 10.3.2225 BUT my troubles with Avast blocking https pages to be opened has NOT been fixed.
I’ve got Windows XP Home Edition SP2 – I know it’s obsolete, but I had several troubles in downloading the SP3, so I gave up.
What can I do to fix my problem? Deactivating http checking can lead to serious attacking troubles?
I don’t know how you are still getting https blocking with avast 10.3.2225. Chan you post some screenshots of the error you are getting.
Essentially there is nothing you can do or should do with win XP SP2, the HTTPS scanning isn’t possible, versions after 2223 will automatically detect you have SP2 and not try to scan HTTPS pages. Avast versions prior to 2223 with XP SP2, didn’t scan HTTPS.
There was also a hotfix that came with a VPS and engine update to disable https scanning in the web shield and XP SP2.
I have XP SP3. HTTPS scanning was working, but it slowed down the browser experience so much,
I uninstalled 2223 and reverted back to 2218. I have not given 2225 a try yet.
I don’t run any of avast “extras” only the shields. It’s not clear if there is anything to gain
for XP users (except for HTTPs scanning, which I’m not interested in anyway).