Searched everywhere for a solution without success.
Avast blocks/uses Intel Virtualization, when I use other softwares (MEmu for instance) that use it they say it is not enabled on the system, although it is enabled in the BIOS.
When I uninstall avast, everything works fine. after installing Avast the problem emerges again. Now i’m forced to use AVG, which I don’t like, I’ve been using Avast for many many years now.
Any solutions anyone ? Thanks.
PS: Using the latest Avast Nitro and Windows 10 Entreprise full updated.
When I asked about Intel virtualization matters a few weeks ago I was given the advice to go to AVAST Settings > Troubleshooting and untick “Enable Hardware Assisted Virtualization”.
Unfortunately I have not gone any further with this I’ve been bogged down trying to get Windows 7 Updates to work properly for the last week, a problem not caused by but added to by AVAST which I won’t detail here. But the info on the virtualization issues came from an impeccable source.
@gennoken: thanks for info, we’ll support MEme in next avast version; right now, the only way is to disable “Enable Hardware Assisted Virtualization” in Troubleshooting, because two applications cannost share VT-x.
I see it was removed unintentionally :-[ – as a workaround, you can disable ‘self protection’ (in troubleshooting), run regedit.exe and set Start=4 in HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\aswvmm.
That rather depends on if you having a virtualization problem ?
If you have the recommendation was to disable the “Enable Hardware Assisted Virtualization” option in the avastUI - because that option isn’t present in the current avastUI ‘pk’ was giving a way to disable it with a registry modification.
My problem was, I cant run any android emulator (nox/MEmu (my pc always hang when startup))and (detected by LeoMoon my vt is disabled), but when I tried that regedit solution, its run normally and great, I was just curious if I changed that aswvmm, something bad will happen to my pc? sorry noob question lol
That change only disables the avast hardware virtualisation, this should allow other hardware virtualization to run. Just follow pk’s (avast team member) post in Reply #7 above. It is also possible to save (backup) that registry key prior to making the change.
That said I don’t know if your android emulation uses hardware virtualization, presumable it does.
“I see it was removed unintentionally :-[ – as a workaround, you can disable ‘self protection’ (in troubleshooting), run regedit.exe and set Start=4 in HKEY_LOCAL_MACHINE\System\CurrentControlSet\services\aswvmm.”
sorry im new here and im not an expert too, and im also trying to do this fix for my emulator as well. but when i go into regedit.exe with the address above, i can’t modify the values of “Start” into “4”. there is an error saying i cannot write new values on it. what should I do?
Additional information, not necessarily relevant to the most recent posts here but possibly useful as regards the general subject.
I gave up trying to get a W7/XP dual boot to work without XP deleting W7 restore points: believe me I’ve tried almost every method I found suggested for hiding the drives from each other including two registry edits.
Restore points, Windows’ built in safety net, I hate anything that messes with them. As a result I decided instead to settle on using Windows 7 Pro’s XP Mode which requires the use a VM. The standard recommendation is to use MS Windows Virtual PC. No XP driver troubles and no restore point problems I hoped and that proved to be the case. Everything else went well too until after I’d installed AVAST on the ‘guest’ XP system.
The virtualization option was unticked in Troubleshooting just as done for the host W7 system but after reboot I noticed all sorts of trouble I hadn’t had before. I couldn’t cut and paste without crashing the VM and the same happened every time I even tried to access a shared drive or volume. Unacceptable.
Internet research on a number of PC help forums/web sites and from a number of different users laid the blame for exactly the same issues I was having on using AVAST.
Whether it was the cause or not I could not be bothered with the hassle of an AVAST uninstall and re-install so I scrapped the whole Windows Virtual PC installation and started from scratch using VMWare Player instead of Windows Virtual PC just to remove that variable too. But this time I eschewed AVAST for the guest XP mode system and went for another lighter weight AV alongside my usual anti-malware programs.
All has being going well since - no problems.
Conclusion: in these specific circumstance ie. when using a VM the evidence suggests it would be prudent advice not to use AVAST as the AV program on the guest system.
Noob here! Cant find anything that says “Start”
I have “ControlSet001” “ControlSet002” and “ControlSetCurrent”
In there i have
aswVmm and in those i have “Enum” with the lines “Standard” “0” “Count” “NextInstance”.
I also have “Parameters” with “Standard” within aswVmm.