Avast BLOCKS Hardware-Assisted Virtualization !!! Yes it does !!!

[glnz]

pk:  Thanks again for your attention. 

If there can be only one virtualization at a time, then Avast should make it crystal clear that Avast is using EHAV all the time, and that other tools will report that HAV is not enabled.  I spent two weeks trying to figure out why I was getting a negative result with havdetectiontool - there was no clue anywhere until I remembered that I had not yet installed Avast in my latest Win 8 (no issue) and had the negative result only in Win 7 (with Avast) and then looked for a connection and found some blog posts by gamers who had manually turned off Avast's EHAV.

When I wrote "threads". I meant blog posts, not processor threads.  If you google for the problem with respect to gamers and Avast's "Enable hardware-assisted virtualization", you might find them. 

► Note that  the gamers had to turn off your EHAV - it wasn't turning off by itself and it was blocking their games.  Also, some of the folks commenting in this thread have the same problem as I and had to turn off EHAV manually - it is not turning itself off◄

I still think this is not correct and that Avast should fix.  Thanks.

[glnz]

Spec8472 - your technical knowledge is way above my non-tech ability to follow.

But my CPU is genuine quad-core.  From your post, I should not have had the problem?

Anyway, please see my immediately preceding reply to pk - Avast should fix this.

[pk]

The fix would be great, I agree, but we can't do that, because then vmware/virtualbox/hyper-v would blue screen your computer. So what's better now...

[KevTech]

Can you please provide some details? CPU, Game title, a crack used?

I don't use cracks.

One title is Bioshock retail version not steam version although I have heard it happens with steam version as well.

I have a AMD Phenom II X4 980 CPU.

I have dual boot system and it happens on Win 7 64 and Win 8.1 64 and even on the XP image I have.

I also had a error from securerom saying I was trying to run the game virtual so would not launch but once Avast turned off all is fine.

This is without NG installed.

[KevTech]

The fix would be great, I agree, but we can't do that, because then vmware/virtualbox/hyper-v would blue screen your computer. So what's better now...

None of these in Win 7 by default.

[glnz]

KevTech - do you mean Avast's EHAV should be UNchecked in Win 7 by default?

[KevTech]

KevTech - do you mean Avast's EHAV UNchecked in Win 7 by default?

No, what I meant was that win 7 does not come with vmware, virtualbox or hyper-v.

Win 8 comes with hyper-v.

[glnz]

I still think Avast should fix this issue.  EHAV on in Avast should NOT prevent HAV in other apps, nor should it cause a bad result in the havdetectiontool.

Can the Avast tech folks advise?

Thanks,

[glnz]

Bump.  This is bugging me.

It means that Avast must be partially disabled for hardware-assisted virtualization to work on the OS.

Why hasn't Avast fixed this?

[bob3160]

Bump.  This is bugging me.

It means that Avast must be partially disabled for hardware-assisted virtualization to work on the OS.

Why hasn't Avast fixed this?

See if this fixes your concern:
https://forum.avast.com/index.php?topic=166883.msg1187702#msg1187702

[glnz]

Bob - Thanks for note.  I'm not a beta kind of guy, but I'll test the effect of Avast's EHAV setting when this new version is actually released.  (Not yet through Update Program.  My Win 7 Pro 64-bit machine is sticking with version 2015.10.0.2208.)

However, the notes for this new version at the top of your link do NOT indicate that Avast addressed my issue, just that NG will now work on non-HAV x86 machines, where my issue is the opposite.

By the way, why was Minh6's post here yesterday deleted?  He posted here "Man, I have the exact same problem and your solution helped me perfectly. I couldn't expect such an ironic uncheck in avast could solve it hahaha."

[bob3160]

@ glnz,
Can't answer your question about Minh6 since I never saw his post.

[glnz]

pk and Spec8472 -- My Win 7 Pro 64-bit machine has just updated to Avast 2015.10.2.2214.  I re-enabled EHAV, rebooted and then ran havdetectiontool.exe, and now this PC now REMAINS enabled for HAV.

So - please advise - did you fix the problem, or is this coming from something else?

It might be something else because, while I had Avast's EHAV disabled these weeks, I installed and ran XP Mode + MS Virtual PC on this Win 7 machine.  From your earlier posts, maybe this somehow prevented Avast from re-grabbing and monopolizing HAV.  So it's not clear whether the good results just now are because you fixed or because the old problem can no longer come back due to XP Mode+Virtual PC having been installed while your EHAV was off.

Important to know before I update my other Win 7 PCs and consider whether to put Avast on the Win 8.1 Pro 64-bit dual-boot portion of this initial Win 7 machine.

Please advise and maybe explain a bit to the audience here (my noob self).  In any case, I'm happy with these good results (so far).  Thanks.

[merckxist]

@glnz
I doubt you are still waiting to proceed with your planned updates, but I have noticed that the havdetectiontool behaved in the same way for me, but only for the first reboot. On a subsequent reboot, the tool went back to reporting that HAV was NOT active on the computer as long as I (still) had the Avast HAV setting enabled. My tested system is Win7 64, avast 2015.10.2.2214. Unlike you, I had no intervening installation of virtual systems. I'm NOT running the avast NG option, only toggling the avast EHAV switch.

Since I have no immediate need for other virtual software, I will probably go back to enabling avast HAV for troubleshooting, but will wait for another release cycle for NG due to some of the other reported issues with disk utilization, bloated backups, etc.

If someone knows of a FAQ for the NG feature that has system requirements, impacts, tradeoffs, etc., I'd appreciate a link. The support FAQ only says it runs processes virtually and improves DeepScreen scanning. Does that mean some behavior analysis occurs that recognizes and interrupts the virtual evil doings before actual damage is done, or something less magical than that? There's just not much info I've run across about how NG is supposed to work, even at a relatively high level.

[REDACTED]

Is there a reason you could not use normal size fonts? May I suggest that this bug ridden beta has blocked or stopped him from adjusting the size?