Avast is aware that some users are still having the problem and are looking into it.
I confirm that after a new installation of avast, everything looks fine, but only until the first restart. Then the license will be reduced to zero again. The fix did not solve anything.
@bob3160 thanks for the update! 
@avast thanks for the update! … not so much. 
Why you do what you did?
You’re welcome.
I can assure you if Avast kew what caused this, it would not have happened.
All I can report is that my v8.0.1487 installation was not working yesterday as I posted. For me I was getting an error message about the aswRun.Dll.exe not working with the fault (“Fault Module”) being connected with another DLL: mscvr90.dll.
After the quick VPS update later in the day the red cross disappeared and AVAST v8.0.1487 started working again as before. I was worried it would reappear on reboot but I’ve completely shutdown and restarted the PC twice since then and all is still good 24hrs on.
No settings were changed as far as I can see; today’s (190314-0) definitions (auto) update has been installed and the perpetual ‘free’ licence code did not need to be re-entered; it is still showing the 2038 expiry date.
Looking at the different error messages and descriptions of the problem other users are having I’m wondering if there is more than one issue here (Windows OS version?). For me although some elements of AVAST were still accessible and the GUI functional for navigation it was not functional in most other ways. That aswRun.Dll.exe not working, obviously a key AVAST component, was the major problem.
Have any of the others here for whom the VPS update has not worked ever had a Windows error message like the one I did (see below) or checked their Event Viewer for more details about the problem?
One problem is, that avast doesn’t update the VPS-Definitions, when the red cross is shown an the programm is “off”!!!
The automatic VPS-Update doesn’t work in this case and same with the Offline VPS-Updates… >:(
I made a backup from my system in January, weeks before our problem here.
The only way for me is to restore my system to this point in January and after that making the VPS-Updates, [b]when avast have found a solution
for our problem here!!![/b]
Hi guys, we fixed the original reported issue yesterday (in VPS 19031302), the problem was affecting only some older versions of Avast 8.
We decided to changed the format of VPS (virus database) and synchronize it with latest versions of Avast. The Avast 8 is now getting the same version of VPS as any other (newer) Avast products (including Avast 19). Unfortunately we haven’t seen those issues (with license and not running service) on latest Avast 8 builds (used e.g. in business installations), so the older versions stop working and we haven’t noticed. Sorry about that. On the other hand, this is fixed by changes in yesterday VPS (we basically revert the way how to sign the VPS for Avast 8 installations, because those old builds are not compatible with new way of signing). So as of now, Avast 8 contains newest version of VPS, just the digital signature stay older one.
Unfortunately we are not able to reproduce issues any more. We did try several builds on several OS versions (including Windows 2000) and it works fine now. So if you can share with us the exact steps how to reproduce, it would be very helpful. If possible, please share also the exact avast build (installer) you use, license number and anything what can help us to reproduce in house.
Thank you.
I’m too, using a Windows 7 SP1 and two Windows XP SP3 machines whit avast 5.
After the monday march 12th update, both Windows XP PCs do not starts Avast service and the Avast icon have the red cross over by saying the program is not working. They was updated to avast 7 and avast 8, but the same problem appears. They works properly until they’re updated.
I’ve a VPS offline donwloaded 2018 update and it works great, but when they’re updated, after restart the system, the red cross appears and Avast does not works.
On Windows 7 seems to work fine, but not on Windows XP after the March 11th update.
please can you post download links to different avast Free 8 versions for the case, that the actually installed versions doesn’t work with your solution?!
For example, I haven’t the setup-file of my avast Free V.8.0.1497, but I don’t want to download it from “unknown”/unsecure websites…
Thank you!
Are we to assume at this point that a current version of vpsupd.exe does not fix any problems created by an update that had an incorrect digital signature?
Honestly, I don’t know whether we (as avast) have such an old product available on our web pages somewhere, but we definitely have some older builds on internal storage. I can’t share those, but I will try to ask some other guys for help and let you know.
Is there please a reason why you can’t use some newer version, e.g. latest build Avast 19.3. or latest “XP compatible” Avast 18.8?
Btw, some older version of business editions are available (on the bottom of page): https://www.avast.com/cs-cz/download-software
I tried it with ALL THESE versions, downloaded from avast.com when released.
https://mega.nz/#F!cU0ixA4a!mfJYgYLkNAji2GbLrXvu0Q
Thanks
Windows 2000: Last Version for this OS was avast Free Version 8 !
Because the LAST NOT SSE2 compatible version is 10.4.2233.1299, and i haven’t it
Thank you guys, yes, non-see processors and win2k is expected and valid reason.
I try today once again on my Windows 2000-PC without success!!! (avast! Free AV 8.0.1497)
My steps:
1.
I restore my system to the date of January 11th 2019 with the VPS-Defnitions from this day
=> Wonderful, NO red Cross and avast! Antivirus-Service is started!!!
2.
AUTOMATIC VPS-Updates came in, Version 190314-2
=> Wonderful, NO red Cross and avast! Antivirus-Service is started!!!
3.
Reboot/Restart my system
=> SH*T!!! - RED CROSS APPEARS and avast! Antivirus-Service is NOT STARTED!!!
VPS-Updates till 190314-2 don’t fix the problem!!!
Something happens during/after the Reboot, that stopps the avast! Antivirus-Service!!!
Thank you guys for all the information you provides. We probably find the source of the issue, it’s (very probably) connected to sse2 instructions, we do work on a fix and hope to have it ready for release tomorrow. I am sorry for the delay and once more thank you all for the help.
Would it help if I posted the Setup.log files? Both right after a clean install and right after a vpsupd.exe that causes the problem? There are definitely error messages in Setup.log once a problematic update is done.
Hello =SKY=!
You can download avast! Free V.8.0.1497 from http://orbitaldownloads.com/download/4460c6e048ef955c9cdf19458aff98a8/ (is OK, I have tested and compared binary file with my original installer from 2013).
MD5 Hash can be found on http://orbitaldownloads.com/avast-antivirus_8.0.1497/info/ page.
And file size is 131.918.888 bytes.
By the way: my “Notebook C” (Win 7 Pro SP1, see signature) is working fine (VPS 190313-4).
Just to be on the safe side, now I have set updates to “manual” temporarily.
It seems that only “old” OS (XP and Win 2000) are affected → currently I don’t find a Vista feedback.
Best regards!
INGBEAN