New windows client version: 12.1.2512 Nitro update

[misak]

Hi all,

today we released client version 12.1.2512 Nitro update (build 12.1.3076.0). The new version is available on all our update servers. The update brings the latest engine known from consumer AV product. For more details about technology please follow posts on our blog

https://blog.avast.com/what-is-nitro-our-newest-high-speed-version-of-avast-antivirus
https://blog.avast.com/cybercapture-protection-against-zero-second-attacks

Whats new?

• Lower system impact - faster boot time, less space taken on disk
• CyberCapture - better detection of unknown and unique files via our cloud technology
• Regular monthly program updates - automatic and silent, configurable via Settings
• New Bank mode in SafeZone browser (paid users)
• Faster SecureLine connection
• Removed hardware virtualization (NG) - replaced with CyberCapture,that has much lower impact on system resources

Update of management console will follow in few hours.

[Manley]

Cool, sounds like a good performance update.

[PetrP]

We are having problem with the Avast program update 12.1.2512.  Once the Avast have this as the current version program, and restart was done. The PC workstation would not boot up. We have done system restore on affected PCs.. But aside from this any resolution to this one?


The previous Program Version 11.2.2511 did not provide us this problem.

Hello,

please can you be more specific what exactly is happening during boot? Also what OS is on affected computers or any other specific SW or HW you think we should know about. It's hard to make any assumptions, we need to reproduce it or have logs/memory dump.

Thank you!

Petr

[REDACTED]

We are also having issues with the 12.1.2512 update. Below is the mini dump. This only seems to be happening on Win 7 machines (All so far are x86). We are able to access the OS through Safe mode and Uninstall Avast! and the computer will resume normal boot operations. We have rolled back with a manual install to 11.2.2511 and the computer continue operate normally. Updated back to 12.1.2512 and computer restarts the BSOD loop.

[ClayL]

Hey guys, If you have an issue with the latest release, please contact us @ support.business.avast.com In the subject line, please post "Issue w/12.1.2512 Nitro update. Also provide OS version 32/64bit ram, etc... and if you can provide a minidump and logs that would be great!. Run this support tool http://utils.support.tools.avast.com/tools/support/utils/avastsupport.exe  DONOT upload it, please attach to email or share.

Thanks Clay

[REDACTED]

https://blog.avast.com/what-is-nitro-our-newest-high-speed-version-of-avast-antivirus
https://blog.avast.com/cybercapture-protection-against-zero-second-attacks
[CyberCapture - better detection of unknown and unique files via our cloud technology

What are the impacts on internet traffic with CyberCapture?  These links don't tell you much on a technical level, but from what I understand, "unknown" files are sent to the cloud for analysis which has a potential to increase WAN traffic.

• What file types are sent?  Just .exe ? 
  
• Are files over a certain size excluded?
  
• If I want to deploy a very large file to my organization that is unrecognized, how soon before the cloud "recognises" it so the same file is not uploaded by 10 PCs?
  
• What about privacy?  How long is the file stored on the cloud; What if my file has sensitive information that i don't want the cloud to store?

[REDACTED]

Have there been any new developments to this BSOD issue on Windows 7 x86 and Windows 10 x86 after upgrading to 12.1.2512.  We are currently experiencing the exact same problem.  We need to boot into safe mode and uninstall Avast to get the workstation/laptop functional again.

[REDACTED]

We are also having start up and login issues after this update was installed. We need this fixed ASAP.

[REDACTED]

I disabled the CyberCapture and DeepScreen modules in the Avast! Business console and that seems to have helped alleviate most of the boot time and login lockups. Will keep monitoring the systems here.

[REDACTED]

Still having some issues with random lockups when  trying to log in. All computers now get to the log in screen now.