41

Have you a beta tester?

42

May I ask, when did the update that caused this begin as it was fine yesterday evening?

43

Sticky post with latest updates: https://forum.avast.com/index.php?topic=199176.0

@nightshade:
It was caused by a virus definition update, which was released this morning.

44

@petr.chytil
Thanks for confirming.

45

Thanks for the detail Petr!

46

For those of you with Avast Business - go into your web panel → Network → Settings → Go to the Template → Turn off components

This has resolved it across the board for me. I was on fire, the fire is put out for now. I plan to re-enable the shields after I confirm the update is applied.

47

I just wanted to confirm we are seeing this issue on 64-bit Windows 7 machines as well. I do not believe this to be exclusive to 32-bit platforms.

48

+1 I am as well. I am not seeing this on any Windows 10 workstations.

49

Running Win 7 Pro SP1, this machine was just powered up about 50 minutes ago. No BSOD yet. And, VPS 170320-01 has been released just now.

50

Seems you’re lucky. 8)

51

Are you saying you’ve updated to the latest definition and you’re still receiving the BSOD?

52

Nope, he says the opposite.

53

Virus definition version 170320-1 has not been released yet.

54

Erm, @Gopher… ??? :-\

55

5pm is quoted, which timezone would this be referring to?

56

CET

57

It’s on my machine, with 4 definitions in it’s folder. How is this explained, if it wasn’t released?

I see, that’s only the stream. Sorry.

58

Should be officially released then in just over 30 mins.

59

I’ve uninstalled avast and installed avg and I’m still getting the crashes :-\

60

They both use the same VPS.