Avast WEBforum
Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Unknown Crewman on September 20, 2016, 06:16:30 PM
-
Hi,
after upgrading the virus definitions to 160920-0, during an avast 12.3.2280 smart scan on Windows 7 64 bit, I encountered the unsigned driver issue shown by the screenshot.
Regards,
Ralf
-
The problem is likely running Windows in a VM.
-
The problem is running Windows and/or in a VM.
The problem is not with avast as it installs without a problem on Windows 7.
This issue didn't happen before, on the same Windows 7 guest, with the same avast 12.3.2280 install. The only change done by me, was upgrading the virus definitions. IOW it already was installed and even now it runs as usual, I just got this unusual message for the very first time.
-
Same issue here. Never seen this message before, but I also got told about an unsigned driver today after booting (and presumedly Avast updating definitions to 160920-0). Also running Win 7 64bit.
-
I have received the same warning on two computers, 1 Win 7 pro 64bit & 1 Win 7 home 64bit. I couldn't find anything about this at avast support.
-
This seems to work > http://windows7themes.net/en-us/windows-requires-a-digitally-signed-driver/
eddit:
I just heard from others that they have the same problem.
Looks like there is a problem with the latest VPS update.
The above link can be used as a temporary workaround.
-
This message popped up on two of my machines within a couple of minutes. It looks like an error in the latest update - I'm concerned that it means avast is no longer working????
-
I've got the same notification. Win7 x64, Avast build 12.3.3154.6, signature 160920-1
-
If you go to C:\Program Files\AVAST Software\Avast\defs\16092001, rightclick on aswHdsKe.sys, switch to the "Digital Signatures" tab, select the "AVAST Software s.r.o" line and click Details, what do you get?
-
same error for me too, but I'm not using Win7 in VM
-
Do as igor asked.
-
Hi, I got the same popup just now. I'm on Windows 7 Enterprise (64-bit).
If you go to C:\Program Files\AVAST Software\Avast\defs\16092001, rightclick on aswHdsKe.sys, switch to the "Digital Signatures" tab, select the "AVAST Software s.r.o" line and click Details, what do you get?
I did that and I got a new window for "Digital Signature Details". There's a lot of info there. What, specifically do you want to know? One of the first lines is "This digital signature is OK." The Email field says "Not available".. Signing time September 15
See picture http://i.imgur.com/Q0bewrR.png
-
What does it say under "details" ?
-
What does it say under "details" ?
Ok, so first I went to: C:\Program Files\AVAST Software\Avast\defs\16092001
Then selected the file aswHdsKe.sys and I right-clicked, and choose "properties". (A window comes up)
Then I chose the tab "Digital Signatures".
Then I selected AVAST Software s.r.o and clicked Details (A second window comes up)
My previous screenshot (http://i.imgur.com/Q0bewrR.png) was from the above step (in Details).
If I go further to "Countersignatures" and select the only line there, and then click Details (second time). (A third window comes up). I get a similar screen as the last but where the signer name is "DigiCert SHA2 Timestamp Responder".
Screenshot of last step: http://i.imgur.com/eEhOeTF.png
-
What I notice is that the signature date is 5 days ago.
My guess is that is what could be causing the problem.
-
What I notice is that the signature date is 5 days ago.
My guess is that is what could be causing the problem.
Yeah, maybe. Time for me to sleep now, so no more responses from me for a while. Thanks for the help so far. I hope someone figures it out.
-
I'm sure avast will figure it out.
Have a good nights rest.
-
Hello guys, do you have windows 7 with SP1 or without? Thank you! Lukas.
-
Lukor, could it be the signing date that is causing the problem ?
-
Hi, it is most probably related to the fact, that the driver is signed with sha256 code signing algorithm, which is supported by windows 7, but only with this update/patch installed: https://technet.microsoft.com/en-us/library/security/3033929
We are going to release and re-signed binary (with both SHA256 and SHA1) asap with the VPS update.
Thanks all for reporting this to us -- we are now going to add new set of test machines with Windows 7 plain installs (currently we test with Windows versions with all updates installed).
Lukas.
-
Just a quick question
Am I still protected until update happens? Or will Avast run as normal? Do I need to do anything?
-
Just got that message on my Vista machine. What does this mean for my protection?
Thanks.
-
I am not running Win7. I came in from dinner tonight, after avast had updated, and found the same message. This is what I got when I went to C:\Program Files\AVAST Software\Avast\defs\16092001, right-clicked on aswHdsKe.sys, switched to the "Digital Signatures" tab, selected the "AVAST Software s.r.o" line and clicked Details. Any ideas?
http://i.imgur.com/gFwnNZ9.jpg (http://i.imgur.com/gFwnNZ9.jpg)
-
Hi, windows xp, Vista a old windows 7 without the update mentioned above will be affected.
This particular file is a tool that makes network operations inside home network scan faster (roughly 10 times faster). When not used everything works correctly, just a little slower (and on small networks you might not even notice the slowdown)
No action is needed on your side, just click the dialog to make it go away, we are releasing re-signed versions today with the vps update.
Thanks. Lukas
-
Hello guys, do you have windows 7 with SP1 or without? Thank you! Lukas.
My Windows 7 is without SP1. (For anyone wondering how to look it up, it's easy: http://pcsupport.about.com/od/windows7/ht/windows-7-service-pack.htm)
-
Thanks for letting us know, lukor.
-
Hello everyone,
The issue with driver signature has been resolved.
Fix will be released with next VPS update.
Thank you for your patience,
Filip
-
Service Pack 1 is installed on my Windows 7, so a missing service pack shouldn't be the culprit. I don't update this Windows install for good reasons, so since Windows 7 service pack 1 is affected, the missing update seemingly is the culprit. Current virus definitions are 160921-4 and the message didn't appear again.
-
Could be another update that you don't have installed.