I personally am having no\and have had no ‘UI failing to load’ issues and have the latest version installed on XP (Build 18.7.4041.389)
However, I have for some time now mentioned that the UI uses an extreme amount of resources to open and function on my low RAM XP
I have no answer for your specific issue
Well I just so happened to do a reinstall of avast free (2 days ago) on my XP Pro SP3 system. I downloaded the off-line installer and that indicated it was version 18.7.4041.0.
When I ran the off-line installer I ensured I was on-line (rather than off-line) and it installed just fine. But I didn’t notice any change of build number, however my build number is 18.7.4041.389. I just wonder if there hasn’t been a VPS update that has more than just virus definitions updates.
So far I know that this is not build version related issue. I have the latest Avast FREE version installed with correct build number xxx.389
As for the lack of operating memory - both of my WinXP SP3 machines have 3GB of ram installed and now both have same version/build of Avast. Still on machine gives this UI failed to load error.
I have never experienced UI failed to load on my XP SP3 system, but as you can see even on your two system there are differences.
It is very unusual that:
1st Windows XP SP3 box has build 18.7.4041.389 and is working perfectly
2nd Windows XP SP3 box has build 18.7.4041.0 and gives a constant error Failed to start UI.
Yet when the 2nd Windows XP SP3 box updated to build 18.7.4041.389 it still has the UI failed to start issue.
I believe the windows error 1053 (from an old windows error utility) is, “The service did not respond to the start or control request in a timely fashion.”
I just wonder if one of the required services hasn’t loaded when AvastSvc.exe is trying to load. You could try this, AvastUI > Settings > Troubleshooting and check/tick the ‘Load Avast services only after loading other system services’ option.
This doesn’t wait for all services to load, only system services.
DavidR, I can confirm build number went from 4041.0 to 4041.389 shortly after install while online from a streaming update, but a reboot was required to set that. (Win 10)
AvastUI > Settings > Troubleshooting and check/tick the ‘Load Avast services only after loading other system services’ tried this but changes won’t apply. When I reopen Troubleshooting section everything goes back to default and ‘Load Avast services only after loading other system services’ option stays unchecked.
I would agree with you that some of the required Windows XP services are not loading therefor AvastService times out after default 30s timeout period. I did some testing and expanded 30s default service timeout to 2min via registry. Then I started tool called ProcessMonitor and noticed that AvastService.exe gets stuck while calling Windows XP - Remote Procedure Call (RPC) service and stays at that point for whole 2 minutes and dies.
I didn’t have time to have a closer look to check what exact call AvastService is making and what response it’s expecting from RPC.
There have been many posts related to the avastUI not starting. If I recall the suggested action was to set the Remote Procedure Call (RPC) service starting to Automatic, if it wasn’t already set.
Mine is on Automatic and I can’t recall having to set it to Automatic.
Outside of this, if it doesn’t work we are going to need some avast team intervention.
Well 100% ending support. This doesn’t include UPDATES does it to the AV database? Another company had did this YEARS ago but allowed updates to the AV database. Otherwise it puts EVERYONE else at risk too. I am a part of a Nationwide Emergency Management system. We use durable equipment that REQUIRES XP or sooner. We have hundreds upon hundreds of thousands of dollars of equipment. Windows XP along with Avast is the heart of this system. This is part of the Volunteer system by federally licensed individuals in every state in the USA. We have people in DHS,DOD,FEMA,Red Cross & other various State and Federal Agencies in this Emergency Management System for deployment and assistance. Basically we are the ONLY one’s available for contacts in a emergency such as Loss of Power,Medical Emergencies, Tornadoes. Our equipment is not what some would see as ‘outdated’ by any means. Newer equipment does NOT meet standards and will fail under various conditions. Our devices are exposed to extreme temperatures, humidity, shock, eletro-static [Lightening]. These systems are in place and needs to equipment to be added. Being more is needed to make our grid have more redundancies. AVAST works the best AV out there and doesn;t interfere or slow down what we have to do. GREAT Losses to Security and potentially the lives of countless thousands. Would be at some stake if part of our system has no AVAST AV system. Not to mention the losses to Avast nationwide. If we can’t run our equipment based on these issues. The costs would be priceless. PLEASE do not blacklist XP. Windows 10 is NOT compatible with our systems nor is Windows 7. It took decades to have these systems in place. In this day & age we do NOT have the time to replace what would be MILLIONS of Dollars and man hours to TRY and keep volunteers. This change to AVAST would more than Jeopardize a major Emergency Management system.
XP and Vista still get virus definitions. So what is point of this thread? Only virus definitions are needed for protected system, no each month changed GUI or new bloatware.
Any new technology that would increase your protection which isn’t tied to streaming or VPS updates would not be available to these older systems mainly because these systems don’t have the capabilities of using this newer technology. Increasing protection isn’t tied to a database of known dangers. Currently, stopping new and unknown malware is done via other means. Artificial intelligence is only one of these newer methods.
VPS virus database files are like having a locked front door which will block bad files from entering. But malware now can enter through cracks in your wall, cracked open windows, and even through your basement. Some can even pick your lock. This is where new and modern up-to-date a/v solutions can protect your system beyond traditional protection means.
I’m new to this thread and want to update my old Avast 4.8 on WinXP/SP3. I understand XP will not be supported from December 2018, but I still want to get as up to date as possible.
Exactly what do I need to do? Do I uninstall v4.8 and then install something else? My PC runs slow so I don’t to add a heavy workload. Thank you for any help!
This is what my Avast says:
Avast! version 4.8 Home Edition - free antivirus, Build: Sep2009 (4.8.1.1368), Xtreme toolkit version 1.9.4.0
VPS file: compilation date 03-03-2017, File version 170303-1
Follow the Clean Install link and instructions in my signature.
Now is a great time since Avast just released the last version that can be used on XP.
Subsequent version updates will not work on anything older that Windows 7
I would advise that the new/er versions of Avast require significantly more resources to function as the software has added greatly improve security techniques and components that simply were not part of earlier (4.80) versions
In addition, if you decide to proceed, use the “Custom” install option (not defautl) so you can choose what component to Check (install) and what you want to Uncheck (not use).
More components more resources required to funciton
I would stay on ver4.8 if other versions are too heavy for my pc but the latest virus signature (fingerprint) file I get is out of date (March 2017). Can I somehow manually install a more recent signature file?
Alternatively, I could run a later version of Avast purely as a disk scanner and on-demand file scanner by disabling the interactive shield. I know this isn’t the best way to protect a pc but it may be all I can do. If I did this then which version of Avast would be advisable bearing in mind I don’t need the full set of bells and whistles - just a plain anti-virus?
