Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Beta - Avast => Topic started by: Asyn on June 12, 2017, 03:43:24 PM

Title: [2299] New Beta
Post by: Asyn on June 12, 2017, 03:43:24 PM

Hi guys, seems we got a new beta (2299), no changelog yet...

Title: Re: [2299] New Beta
Post by: Zeniit on June 12, 2017, 03:51:33 PM

For me it's updated automatically in the background, and after a coffee break my windows pc welcomed me a blue screen :D

Event log show this: 0x0000007e (0xffffffffc0000005, 0xfffff880068c44dc, 0xfffff880035936d8, 0xfffff88003592f30).

Thanks,
Zeniit

Title: Re: [2299] New Beta
Post by: Asyn on June 12, 2017, 03:59:44 PM

Ups, bad luck. I updated via GUI and no issues so far.

Title: Re: [2299] New Beta
Post by: Be Secure on June 12, 2017, 04:01:31 PM

I updated via GUI and no issues so far. :D
They add "Ransomware Shield" in this beta... 8)

Title: Re: [2299] New Beta
Post by: Asyn on June 12, 2017, 04:12:40 PM

Quote from: Be Secure on June 12, 2017, 04:01:31 PM

They add "Ransomware Shield" in this beta... 8)

Yep, I already use it but will keep the details for the official thread. ;)

Title: Re: [2299] New Beta
Post by: Be Secure on June 12, 2017, 04:16:34 PM

Quote from: Asyn on June 12, 2017, 04:12:40 PM

Quote from: Be Secure on June 12, 2017, 04:01:31 PM

They add "Ransomware Shield" in this beta... 8)

Yep, I already use it but will keep the details for the official thread. ;)

I am also testing now but if the whole drive(C:,D:) is protected it would be great...... not only folders.;)

Title: Re: [2299] New Beta
Post by: DavidR on June 12, 2017, 05:58:28 PM

Quote from: Zeniit on June 12, 2017, 03:51:33 PM

For me it's updated automatically in the background, and after a coffee break my windows pc welcomed me a blue screen :D

Event log show this: 0x0000007e (0xffffffffc0000005, 0xfffff880068c44dc, 0xfffff880035936d8, 0xfffff88003592f30).
<snip>

Interesting, that is why I used my drive image backup on the 17.4.2298 BSOD error  0x0000007e, but the detail was different no ffffffff in the strings.
0x0000007e (0xC0000005, 0x0000001E, 0xF78D26B4, 0xF78D23B0).

This was on an XP system, which may account for the details being different. This happened on three reboots, before I restored my last drive image. I reported this in the 2298 beta topic but got no interest in the issue. I was kind of hoping this beta update may have resolved this, now I don't know.