Beta 17.1.2282

Its basically Software Updater on a new name.

Okay, so then when the final release comes out, I can turn that OFF … I do my own checking for when software needs to be updated. And some programs I never update, but Flash, Shockwave and Java do get checked every couple of weeks or so.

Actually it’s former AVG IDP. Behaviour blocker :slight_smile:

No more Software Analyzer listed under the UI now for me, its back to Software Updater now.

HitMan Pro and VirusTotal

http://i.imgur.com/b9saijR.png

http://i.imgur.com/CJGuYQI.png

Looks like a FP.

I would agree with that, not to mention I wouldn’t recommend the use of HitMan Pro.

Not to mention 5 of the hits on the VT image are all bitdefender signatures and all 7 of 56 are heuristic detections.

I can’t shut down my PC (Win 10 Home Version 1607 OS-version 14393.576) after installing the latest beta (17.1.2282 Build 17.1.3336.0) of Avast Internet Security. I have submited a ticket and a package file. When I try to shut down my PC, it’s just restarts.

Installed on a test machine with win8.Seems to run fine.The installer was lot slower than usual not sure if this is intended behaviour but nevertheless its working fine just the issue with the shutdown windows seems to be having a gripe with avast on shutdown not shutting down properly.

I had that problem till I did a clean install of Windows 10.
Now I’m running the beta of Avast on Windows 10 Pro v. 1607 without the shut down problem. ???

@Bluesman + @TI199 + all others who cannot shut down (and possibly hibernate) PC with Avast installed - does disabling the FileShield from Settings help?

Yes it helped.FileShield is causing this issue.Pls fix this quickly.

Missing pause button for virus scan pls add this and what is “NaN%”?

HIPS settings seems to be gone.Why?

IDP from AVG will be integrated with the next beta.

I tried hibernating worked fine.And I have tried shutting down the file shield for a while seems to fix the issue.Not sure if this is the main cause.

Thanks
True Indian

Yes, disabling the FileShield worked for me. I disabled the FileShield, and now I could shut down my computer.

Well then I am not alone.Surely must be something associated with file shield.Ironically only experiencing the issue on win10 :slight_smile:

Just a thought, but Windows 10 is somewhat picky about program access levels. Try setting Avast to “run as administrator” and see if that fixes the problem.

I would have thought that AvastSvc.exe (avast service) is running at a higher level (System) and that is the file that controls the various scanning engines.