New Beta version 18.5.2339

[Csicso]

yeah...we will soon announce end of support of these OS..

Large numbers of Avast users use XP -see other forums. https://forum.avast.com/index.php?board=2.0.. We use it precisely to avoid all the bizarre issues that show up on later versions of Windows (maybe not Win7). Personally, I use it as a VM on my Mac, running flawlessly under Parallels, for all non-internet work, but need antivirus since XP files are accessible when shared with the Mac OS. The 18.4 version of the Avast Free Antivirus program introduced something that does not work with most installations of XP.  I reverted to the 18.3 version, which works fine. Presumably we will still be able to use updated virus definitions, running on 18.3  Nevertheless it would be nice if Avast would fix the problem introduced in 18.4  I have not tried the new beta, and will not until someone posts that it fixes the problem.


compatibility with Xp can hinder development. Makes development difficult. I belive.

[Csicso]

I still use my XP OS for in house tasks. Certainly not situations that require 'constant' internet connection.
XP is not a secure OS for a huge number of reasons beyond Anti Virus protection.
Anyway, nothing lasts forever, eventually all XP systems will cease to exist.

Use it Windows 95,  they do not even write a vírus. I do not really understand what people think Will support be up to the end of time?


USE   L I N U X!

[bruce_b]

A lot of us still use XP .. I use XP PRO SP3 on my old Dell Dimension 8200 P4 1.8Ghz 2GB RAM machine. It is a fully legit version of XP that is installed. As to Avast discontinuing support of XP, I use only the basics from Avast Free (File Shield, Web Shield, Behavior Shield) .. It has the latest stable release on it and is working fine. I would like to know how long we will still be able to auto update virus definitions after support for XP ends. Will the entire Avast Free stop installing on XP or only certain components of it, that a lot of us do not use ? ? ? What about AVG ? ? ? Will that work on XP ? ? ? Or does anyone have a good replacement that does not hog or slow down the computer if it is needed ? ? ?

[Asyn]

Guys, the XP discussion is OT in this beta thread..!!
-> https://forum.avast.com/index.php?topic=219361.0

[aharris2]

Guys, the XP discussion is OT in this beta thread..!!
-> https://forum.avast.com/index.php?topic=219361.0

OK, I will make it on topic. This beta is supposed to fix the UI not loading problem on many/most XP machines. Can anyone tell me if this beta 18.5 fixes the problem - that is, if 18.4 had the problem on your machine, does 18.5 beta fix it?

[bruce_b]

The current stable release works fine on my old Dell Dimension 8200 with a P4 at 1.8Ghz and 2GB RAM .. it is running XP PRO SP3 ... I do not know why some have issues and some do not. Sometimes a clean install of the antivirus is best. Also clear out your temporary files and run disk defragmenter.

[Csicso]

A lot of us still use XP .. I use XP PRO SP3 on my old Dell Dimension 8200 P4 1.8Ghz 2GB RAM machine. It is a fully legit version of XP that is installed. As to Avast discontinuing support of XP, I use only the basics from Avast Free (File Shield, Web Shield, Behavior Shield) .. It has the latest stable release on it and is working fine. I would like to know how long we will still be able to auto update virus definitions after support for XP ends. Will the entire Avast Free stop installing on XP or only certain components of it, that a lot of us do not use ? ? ? What about AVG ? ? ? Will that work on XP ? ? ? Or does anyone have a good replacement that does not hog or slow down the computer if it is needed ? ? ?

A lot of us still use XP - changed windows 10 or LINUX.  DELL Dimension 8200 15 years old machine (i found it) Wonder how it works


Sorry for lots OFF.

[bruce_b]

For it's age what I use it for (mainly Firefox 52.8.0ESR) and Office XP (word, excel) it does fine. It did need a new Nvidia Video card about 3 years ago when the one I ordered it with called it quits (my Dell (sony style) CRT monitor died about 3 weeks after the video card (that was replaced with a Dell S2340M monitor for $130) 

[bob3160]

Time to get back on topic.

[av20]

Another XP user here and the beta is working OK.

[aharris2]

thanks -  was 18.4 not working for you?

[av20]

thanks -  was 18.4 not working for you?

I remember reporting a bug in one of the betas that was related to a change in WiFi inspector.  It was fixed shortly afterward.

[REDACTED]

Hi,
The Beta version has the same problems as 18.4 version on my Windows XP SP3:

- when starting UI -> error "UI Failed to load"
- when starting definitions/program update -> error "RPC server not available"
- Avast Antivirus service not starting automatically,
            when trying to start it -> error 1053 "service does not replay to signal..."

Windows system services seem to work OK.
What else can I check?

[bruce_b]

That sure sounds like a corrupt install. I would run Avast Clear to uninstall Avast (first backup your exclusions list), then be sure all program folders from Avast (including in the Docs & Settings folders) are removed. You may want to run a Registry Cleaner to be sure all old Avast Registry keys are gone. Then reboot and run the Full Off Line Installer of Avast  .. reboot again and see if all is good.

[aharris2]

I did all those things and more for 18.4 without effect (see previous posts).

"Using XP SP3 - no problems for many years with Avast Free Antivirus until this latest - UI does not load. Some postings indicate that fixes have been made, at least for Win10. However, on XP (SP3), version 18.4.3895.0 still has the problem. I have uninstalled, reinstalled, rebooted, and repaired. I have made all the suggested tweaks to "Services" (background intelligent transfer service; terminal services; remote desktop service), but the problem remains."

My XP works flawlessly in all other programs, and has worked on all previous versions of Avast through 18.3.

This is seems to be an issue introduced with 18.4 and has not been addressed in the beta 18.5. As others have noted, it apparently does not occur in some XP installations, but affects others. Probably some minor registry setting?