BLUE SCREEN WINDOWS 8.1

[REDACTED]

Did You read my reply #69 ? This is what You have to do. Than everything works fine.

[REDACTED]

Yup, you bet.

But let's be honest. There is NO way ever that I would download a component of an AV program from a site other than the direct programmer. Don't get me wrong, I appreciate the effort. but until it is listed or comes from the avast site itself, or through an avast mirror to our AEC, I will no be adding or changing any files. Sorry.

From our AEC When trying to update from the add remove programs set we see this. Anyone else see the older release?
Downloads and updates the latest version of all avast! components.

Current version:
 - program: 8.0.378
 - setup: 8.0.378

Latest version available:
 - program: 8.0.369
 - setup: 8.0.369
Publishing date: Apr 04, 2014

We downloaded and upgraded the AEC about a week ago to deploy the AV to windows 10 systems. So I figure its on the latest...?

[REDACTED]

So far, one of the PC's was updated yesterday to 160210-0 and the driver file was NOT updated. The 2 other PC's we updated today were updated to 160211-1 and the drivers were NOT updated as well.   

I have yet to see any systems update with the changes to the .sys file. We are currently updated to 160301-0 (on 1606) with no changes.

[REDACTED]

Hello All,

We will have a new program update in the next few weeks to resolve the problem.  We tried  to resolve the issue with an EM update and for many it worked, but it did not resolve the issue for all. 

This update will also include the console's as well.  In the new program update, the new aswvmm.sys file will be included, the update will remove the old driver in place for the new file.  Currently we are also working on resolving some other minor bugs as well.

Our apologies for the delay but a fix is on it's way.  We continue to appreciate your support and patience.  If you have any other issues please contact us at absfeedback@avast.com and we will return your mail within 24 hours.

Kind Regards
Che

[REDACTED]

Hello All,

We will have a new program update in the next few weeks to resolve the problem.  We tried  to resolve the issue with an EM update and for many it worked, but it did not resolve the issue for all. 

This update will also include the console's as well.  In the new program update, the new aswvmm.sys file will be included, the update will remove the old driver in place for the new file.  Currently we are also working on resolving some other minor bugs as well.

Our apologies for the delay but a fix is on it's way.  We continue to appreciate your support and patience.  If you have any other issues please contact us at absfeedback@avast.com and we will return your mail within 24 hours.

Kind Regards
Che

Hello,
will you fix this bug in this update too?
https://forum.avast.com/index.php?topic=180431.0

Kind Regards
IT-KAV

[REDACTED]

Yes, but this should be already taken care of on any clean installation, the WAC issue should only affect clients that migrated from .1603 to .1606.

[REDACTED]

Yes, thank you.
It certainly is fixed with clean installation, but when you have few hundred computers across multiple factories, you need to push update through console. We don't have spare people to do it manually.

[REDACTED]

Hello All,

We will have a new program update in the next few weeks to resolve the problem.  We tried  to resolve the issue with an EM update and for many it worked, but it did not resolve the issue for all. 

This update will also include the console's as well.  In the new program update, the new aswvmm.sys file will be included, the update will remove the old driver in place for the new file.  Currently we are also working on resolving some other minor bugs as well.

Our apologies for the delay but a fix is on it's way.  We continue to appreciate your support and patience.  If you have any other issues please contact us at absfeedback@avast.com and we will return your mail within 24 hours.

Kind Regards
Che

Hey Che, We got an update pushed ( I have not updated the console yet) we looked to be resolved with the issues doing a safemode boot and replacing the ASWupdater. As of today I have BSOD' again on both win 10 and 8.1 with an ASWupdater dated for 3/17/16. Is a console update going to ratify this or are we looking at a different system problem with avast?

[REDACTED]

Hi,

We face the BSOD problem again. Do you know when the fix will be published ?

[REDACTED]

4 months on and we are still having BSOD issues with no end in sight and no more info from Avast??

[hillen]

Nail is finally in the coffin for our continuing to use Avast.

Just got off the phone with the company President and guess what Avast -- his Windows 8.1 is now blue screening about every 2 hrs. and HE HAS TO GO ON A FRICK'IN BUSINESS TRIP TOMORROW and he requires access to his machine.

THE ONLY METHOD TO SUCCESSFULLY STOP THE BSOD IS TO GO TO WINDOWS 10! What continues to amaze me is the fact your company is absolutely silent - WOW, just freak'in WOW!

Have already started to process to test replacements for when our license is up but guess what -- now that the President has been affected that time line will move up RAPIDLY!

[REDACTED]

This is what I'm going to do now on Windows 8.1 boxes getting the BSOD because of corrupt "aswvmm.sys":

Replace any older "aswvmm.sys" exisiting on the system with a copy of the newer (patched) "aswvmm.sys" at this locations on the system:

C:\Program Files\AVAST Software\Avast Business\Setup\INF (for 32-bit systems)
C:\Program Files\AVAST Software\Avast Business\Setup\INF\x64 (for 64-bit systems)
C:\Windows\System32\drivers\ (for both 32 and 64 bit systems)

I'll keep you posted with updates.

Hi SomDev2004,

I am trying to deploy this fix with a GPO but im getting an access denied error when trying to replace the file. How did you get around this?

[_George_]

New Endpoint Protection Release

Avast currently releasing a new version of the Endpoint Protection products, this version will fix two bugs:

- Win 8.1 BSOD
- Mapped drive issue

Versions:
AEA (ver.8.0.405)
SOA (ver.1.3.3.112)
Managed EP clients (Stand Alone) (ver.8.0.1607.557)
Email and File server security (ver. 8.0.1607.557)

Standard upgrade procedure applies. New installers should be available for download in the next 24h. - Try in Monday.

[REDACTED]

Will the new version fix Windows 10, George?

[_George_]

JR, my greetings!

As you can see - no words about win10.