Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Rickajho on March 12, 2019, 06:51:42 PM
-
Don't be hatin' - in this case it's Avast 8.0.1506
This is regarding the free, extended registration key provided for older Avast Free versions. Here:
https://www.avast.com/en-us/registration-free-antivirus (https://www.avast.com/en-us/registration-free-antivirus)
I updated my virus definitions this morning. Just for 'maintenance' I decided to reboot the computer and that's when the problem appeared.
Avast is loading, but all the Shields are disabled. Won't even allow me to check for virus definition updates now. WTH!?!? Reboot - problem still there.
I look at my Registration info screen and I find this:
(https://images2.imgbox.com/0b/48/ashHRMeV_o.jpg)
So I'm either not registered. Or I'm good until some time in 2038. :o
Uninstalled Avast and reinstalled. It's working again under the "30 day free trial" option from a fresh install.
Reenter the registration key from the above linked page and I'm right back to the problem. I'm assuming there is something wrong with that registration key at this point, regarding the software having mixed messages about what date the registration key is good through.
Help! Can someone from Avast look into this?
-
I have the same problem with Avast Pro 8.0.1497.
After today's virus database update, the cheerful message: "Your license has expired." Only the validity of my license file is until 21/12/2019. The usual uninstall from safe mode and the new program installation will not help, after the virus database update I am back at the beginning - without a PAYED license.
-
I am having the same problem with v8 on ALL om my machines after last definition update.
I just tried a clean install on a clean VM (never has Avast installed). I didn't even register it, just ran it as a 30 day unregistered license and after update same thing!
-
I've reported this to the developers.
-
Thank you @bob3160
For what it's worth: I just did a 'manual' definitions update with the most recent vpsupd.exe. (Newer than the update from this morning.) And although that installed ok it didn't unscrewup the problem either. :(
Curious to know though, how a virus definition update could screw up registration information. ???
-
Thank you @bob3160
For what it's worth: I just did a 'manual' definitions update with the most recent vpsupd.exe. (Newer than the update from this morning.) And although that installed ok it didn't unscrewup the problem either. :(
Curious to know though, how a virus definition update could screw up registration information. ???
VPS updates can do a lot more than just update virus definitions. :)
-
I'm having what I really hope is the same problem with 8.0.1497 too after switching on the PC this morning which I use that version on I'm getting a message that the aswRundDll.exe has stopped working.
Avast is the only program I use which is set to auto-update definitions and it does that at startup so my immediate suspicion was that the update is what has caused the problem
AVAST says it is now off and my system unprotected. It will not start using the Start button, Resolve All does not work and neither did Repair. This is concerning to say the least as I have not had any problem with AVAST that has caused it not to work at all in a very long time.
I tried Windows System Restore which should have been no trouble but it is refusing to work and suggests that an anti-virus program ie. AVAST is what is preventing it and should be turned off to try again. Nothing like that has ever happened before, I've not had any problems using System Restore with this version of AVAST ie. never had to use Safe Mode.
My AVAST Free is registered correctly of course.
-
Hi guys, thank you for reporting. The issue is fixed in new VPS 19031302, we are very sorry for this. The avast installation should download the new version automatically, but if not you can uninstall and install again. Thank you.
-
Just restarted my PC (BTW after risking installing the Windows Monthly Updates) and initially on restart I still had the error message about the AVAST aswRun.dll but I'm guessing that the AVAST VPS update was downloading/installing at the same time.
However when I closed the error message box I immediately saw the red cross had gone from my AVAST tray icon and it is shown now as working.
Phew, glad the issue is apparently sorted as that had me really worried.
Thanks for the exceptionally quick solution.
-
The new VPS update fixed the problem thank you.
FYI for anyone having the problem - The auto update wouldn't work with the bad VPS files from yesterday. I download the manual update https://www.avast.com/en-us/download-thank-you.php?product=VPS5&locale=en-us (https://www.avast.com/en-us/download-thank-you.php?product=VPS5&locale=en-us), ran it and rebooted. All good now :)
-
@ Cluster-Lizard2014
System Restore (especially in older OS versions) has never been bullet proof and it was recommended to disable the Avast self-defence module. As that would still be protecting Avast even if you disabled Avast.
Windows System doesn't cover everything as far as Programs goes (including other programs). It is more for resolving System problems than individual program issues. This is why I have always relied on hard drive imaging software for Backup and recovery. I feel this is even more essential for older systems and programs are concerned as it can be harder to find system/program updates.
Fortunately a fix by Avast has resolved this and I don't believe a system restore would have resolved this.
EDIT: Typo
-
As I said I've never had a problem with using System Restore before today ie. their use being blocked by AVAST.
I've not needed to use System Restore that often ever but occasionally it is far easier and quicker than any other method of restoring a PC to its previous state when some newly installed program or changes causes a problem.
I always put in a restore point before installing new software and as part of my weekly maintenance regime. Windows Updates and many other programs, particularly uninstallers like Revo do the same. I hate anything that interferes with their use and I am well aware of AVAST's reported inclination to do so but had not experienced it myself until today.
I hope this was a consequence of the faulty update causing whatever elements of AVAST that were working on my PC to misbehave and not some unwanted new feature. Time will tell on that.
However I agree that, in retrospect, using a Restore Point in this case, now we know the cause, would not have helped fix the problem. Even if it did I'm almost certain it would have returned as soon as the computer rebooted unless I'd turned off AVAST's definitions etc auto-updates.
-
System Restore (especially in older OS versions) has never been bullet proof
I agree, and never counted on such Microsoft functions.
I prefer system images from the OS & application partition; costs me 20 minutes every 2..3 months and helps against all troubles ;)
-
As I said I've never had a problem with using System Restore before today ie. their use being blocked by AVAST.
<snip>
I have always recommended disabling the avast self-defence prior to using System Restore if that restore is likely to impact on Avast protected areas/files.
I too have never had a problem with windows restore, mainly because I never used it (I saw the potential failings as it doesn't/didn't cover everything) as I have used drive imaging software certainly as far back as win98 :)
That said I use the Windows 10 Backup it is a little more flexible and more comprehensive. I create a system image and backup to an external drive. I also periodically create a system repair disc, normally after a new OS update.
-
Since january I use Macrium Reflect free. Looks good and creates an image under Windows.
Before i used Clonezilla, comlicated to handle.
-
I use EaseUS Todo myself but I simply don't have enough storage space or inclination to create a system image each time I install a new program or update. You can create a restore point in a few seconds, at least you can with a desktop shortcut.
CCleaner also makes deletion of redundant restore points very easy for freeing up space or as part of a regular maintenance regime.
Its a basic first level safety net and whilst there is always criticism of it found on various forums until this particular AVAST issue it had never failed to work on this PC which is now 3+ years old. In the past more often than not I've found it fixed the sort of problems I've had which restoring a computer to an earlier point could fix when I've needed it too. In other words: I've always found it reliable
-
Don't be hatin' - in this case it's Avast 8.0.1506
This is regarding the free, extended registration key provided for older Avast Free versions. Here:
https://www.avast.com/en-us/registration-free-antivirus (https://www.avast.com/en-us/registration-free-antivirus)
I updated my virus definitions this morning. Just for 'maintenance' I decided to reboot the computer and that's when the problem appeared.
Avast is loading, but all the Shields are disabled. Won't even allow me to check for virus definition updates now. WTH!?!? Reboot - problem still there.
I look at my Registration info screen and I find this:
(https://images2.imgbox.com/0b/48/ashHRMeV_o.jpg)
So I'm either not registered. Or I'm good until some time in 2038. :o
Uninstalled Avast and reinstalled. It's working again under the "30 day free trial" option from a fresh install.
Reenter the registration key from the above linked page and I'm right back to the problem. I'm assuming there is something wrong with that registration key at this point, regarding the software having mixed messages about what date the registration key is good through.
Help! Can someone from Avast look into this?
I have the same problem with avast-Free 8.0.1497 on my W2000-PC!!!
After manual VPS-Updating and after automatic VPS-Updating to 190313-4 all seems good, but after a reboot the red cross appears again!!!
What can I do???
I made several reboots but the red cross is still there and the programm says "Der Avast-Dienst wird nicht ausgeführt"!!!
-
A fix in the offline-Updates would be great for Windows 2000 here:
https://www.avast.com/de-de/download-update
-
I have the same problem with avast-Free 8.0.1497 on my W2000-PC!!!
After manual VPS-Updating and after automatic VPS-Updating to 190313-4 all seems good, but after a reboot the red cross appears again!!!
What can I do???
I made several reboots but the red cross is still there and the programm says "Der Avast-Dienst wird nicht ausgeführt"!!!
@jaroslav.nix It didn't work here either. >:(
Apparently I had already done the 190312 update before it was announced here. Avast was still disabled. (I mentioned doing an AVSUPD.exe earlier in this thread.) Saw the announcement about the fix - oh joy!. Downloaded the recent AVSUPD.exe and ran it:
(https://images2.imgbox.com/f0/62/jxGNh3HA_o.jpg)
Still not working. Same problem I started this thread with.
Not much else to do so I:
Uninstalled Avast. Ok
Reinstalled Avast 8.0.1497. Ok
After installation it automatically did a Virus and definitions update. Ok - for now.
Program updated from 8.0.1497 to 8.0.1506. Error message at the end of the update:
(https://images2.imgbox.com/9e/ee/BEUP3J3S_o.jpg)
Don't know what that means! Better reboot and - right back to the problem as I first reported it.
I saved the DMP file from that error if someone wants to look at it.
Try to update via Avast and I get:
(https://images2.imgbox.com/45/ee/u8J2PbiR_o.jpg)
Has anyone else who reported this fix worked actually rebooted their computer to see if it's still working?
-
Yes, the Problem beginns AFTER THE REBOOT!!! :(
-
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?
-
@bob3160 thanks for the update! :)
@avast thanks... 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, when avast have found a solution
for our problem here!!!
-
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. :(
-
@jaroslav.nix,
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!
-
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.
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
-
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?
Windows 2000: Last Version for this OS was avast Free Version 8 !
-
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?
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.
-
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...
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
-
@INGBEAN
Thank you so much!!! :-*
(mein Seelenverwandter ;))
Best regards!
Sky
-
It is also available here:
https://forum.avast.com/index.php?topic=164936.msg1322691#msg1322691
-
This problem still persists as of the 19031404 vpsupd
I use Win2K and v8.0.1506
This was on 3/14 :
I tried the 3/10 vpsupd followed by online update. After the 3/10 vpsupd, everything was fine. After the online update it seemed sorta OK. (Actually, after the update I noticed AvastSvc was running more than it should). Then on reboot, Avast wouldn't start, online update info reported 'unknown'
I restored a backup build. Then I tried the 3/14 vpsupd directly. Seemed fine until the reboot, then Avast wouldn't start, online update info reported 'unknown'
Vpsupd is important for Win2K because I've noticed if you haven't done an online update for a while, it will fail with a 'not enough storage' error. Then your only option is vpsupd, or a clean install.
I also use Avast5 and Avast7 on some of my Win2K builds. Updates failed here too.
-
Vpsupd is important for Win2K because I've noticed if you haven't done an online update for a while, it will fail with a 'not enough storage' error. Then your only option is vpsupd, or a clean install.
+1
Sky
-
The second issue with sse2 instructions should be also fixed now, please try to update VPS to version 190315-00 and let us know, thank you.
-
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.
I think isn't because, I've 2 XP SP3 machines and another with Windows 7. Avast 5 works fine on Windows 7. A Windows XP machine has SSE2 and the other one haven't, and both have the proble reported. So I think SSE2 isn't the problem.
So, it's a problem with the VPS after March 11th to fail on machines before Windows 7.
With Windows XP SP3 works fine if they have not updated after that date, else after the reebot the red cross appears and Avast service does not works :(
-
Can you please retest one more, with VPS 190315-00? Thank you.
-
Can you please retest one more, with VPS 190315-00? Thank you.
Checked on the non-SSE2 Windows XP machine, it seems the VPS 190315-00 works fine.
I'll try on the other (SSE2 compliant) Windows XP later...
Thank you very much.
PD: What was the problem?? :?
-
Thank you for confirmation. The problem was one of the binaries (namely algo.dll) and the mistake in build servers configurations (the sse2 instructions were used because of some other and apparently unrelated option for Spectre mitigation).
-
Hello Avast-Team,
it seems, it works now on my Windows 2000-PC with avast!-Free AV 8.0.1497!!! :-* :-* :-*
I had nothing to do.
I started my PC today with the red Cross on the avast-symbol.
After a while the Online-VPS-Updates came in (190315-2) and now everything seems to be o.k.!!!
Registration till 2038 is o.k. again!!! :)
Thaaaaaaaaaaaaaank you very much!!! :-* :-* :-*
-
Yes, on my other Windows XP SP3 PC (SSE2 compliant) now it's working perfectly.
Booth Windows XP machines working fine with VPS 190315-02 and registered until 2038.
Thank you very much.
-
OK here too on a Win2k sp4 machine. ;D Only a PIII cpu so no SSE2 here.
Started with 190315-2 on a clean Avast install. Then updated to 190315-4 and it's still working!
(Who puts that SOLVED thingy in the thread subject line? Me?)
-
@ Rickajho
As you are the topic starter, you can 'modify' the first post in the topic and add [Solved] or [Resolved] to the topics Subject.
As I have in the attached image, but that only changes my post. Yours would change the Subject displayed in the list of topics.
-
@INGBEAN
Thank you so much!!! :-*
(mein Seelenverwandter ;))
Hello =SKY=!
No Problem, you're welcome. :-*
Have a nice weekend!
INGBEAN
-
Hello!
A summary:
Can you please retest one more, with VPS 190315-00? Thank you.
Checked on the non-SSE2 Windows XP machine, it seems the VPS 190315-00 works fine.
it seems, it works now on my Windows 2000-PC with avast!-Free AV 8.0.1497!!! :-* :-* :-*
After a while the Online-VPS-Updates came in (190315-2) and now everything seems to be o.k.!!!
Registration till 2038 is o.k. again!!! :)
Yes, on my other Windows XP SP3 PC (SSE2 compliant) now it's working perfectly.
Booth Windows XP machines working fine with VPS 190315-02 and registered until 2018.
OK here too on a Win2k sp4 machine. ;D Only a PIII cpu so no SSE2 here.
Started with 190315-2 on a clean Avast install. Then updated to 190315-4 and it's still working!
In everyone's interest, I want to declare a big THANK YOU to Avast (service and development) team!
It wasn't a given that support for "old" software versions or operating systems is assured by companies.
Such cases are superb examples for service-oriented enterprises.
Keep it up! 8)
Best regards from Austria!
INGBEAN
-
...
In everyone's interest, I want to declare a big THANK YOU to Avast (service and development) team!
It wasn't a given that support for "old" software versions or operating systems is assured by companies.
Such cases are superb examples for service-oriented enterprises.
Keep it up! 8)
+1 :) :) :)
Sky
-
Yes, thanks to Avast for continuing to help the legacy OS users!
Theoretically, Avast 8.0.1506 and above is supported. I was kinda surprised how many Avast8 users chimed-in when the update system went buggy.
BTW, the fix worked for Avast5 and Avast7 also. These I still use with some builds on my Win2K Pentium 3 machine as they tend to use the OS resources less: Every bit helps when the machine is 550Mhz and limited to 256MB RAM
-
BTW, the fix worked for Avast5 and Avast7 also. These I still use with some builds on my Win2K Pentium 3 machine as they tend to use the OS resources less: Every bit helps when the machine is 550Mhz and limited to 256MB RAM
Ouch! And I thought I was hurting running w2k at 800 Mhz with 512MB RAM. ;D