I’m running Avast Internet Security on Win 7 SP 1. On a clean install of AIS 2015 10.0.2208 on my Leveno Thinkpad with processor AMD A6-5350M with Virtualization enabled in the bios, NG is not offered as an install option. When I ran Securable from GRC, it indicated that virtualization was enabled and available.
Have you checked at the installed components?
Is NG installed according to them?
Laptops are not known for having a large drive, could be that NG didn’t installed because of lack of space.
No, NG did not install as it wasn’t offered as a option. The hard drive is 1 terabyte, with 95% free. The machine is about 2 months old.
I don’t want this thread to die without a solution.
Is there a more definitive utility that can verify whether hardware virtualization is available and truly enabled on this machine?
I downloaded CoreInfo as mentioned in the post above. The results on the Lenovo AMD is
AMD A6-5350M APU with Radeon™ HD Graphics
AMD64 Family 21 Model 19 Stepping 1, AuthenticAMD
HYPERVISOR - Hypervisor is present
SVM * Supports AMD hardware-assisted virtualization
NP * Supports AMD nested page tables (SLAT)
I did already do an Avast Repair via Control Panel | Remove a program | Repair which didn’t work. I also uninstalled Avast, rebooted and ran AvastClear which entered Safe Mode, rebooted and then reinstalled AIS. There was no option for installing NG, which indicates for some reason the AIS install doesn’t think virtualization is available on this machine.
However, Speccy from Piriform shows AMD virtualization available and enabled. That’s 3 utilities that show virtualization enabled. Why does Avast not consider it available?
Have you checked at the installed components?
Is NG installed according to them?
After Avast is installed…Have you tried change instead of repair?
NG is NOT installed, as it is not even offered on the list of components during a custom install. The NG folder doesn’t exist in C:\Program Files\Avast Software\Avast.
I did also select Change, but even there NG is not offered as an option. NG has never been offered as an option on this machine.
That is strange as it seems your system does support it.
What motherboard do you have?
Perhaps that gives a clue about what is going on.
The motherboard is LENOVO 20B20011US (Socket FS1r2).
CPU info…
CPU
AMD A4/A6/A8/A10
Cores 2
Threads 2
Name AMD A4/A6/A8/A10
Code Name Richland
Package Socket FP2 (904)
Technology 32nm
Specification AMD A6-5350M APU with Radeon HD Graphics
Family F
Extended Family 15
Model 3
Extended Model 13
Stepping 1
Revision RL-A1
Instructions MMX (+), SSE, SSE2, SSE3, SSSE3, SSE4.1, SSE4.2, SSE4A, AMD 64, NX, VMX, AES, AVX, FMA3, FMA4
Virtualization Supported, Enabled
Hyperthreading Not supported
Bus Speed 100.9 MHz
Stock Core Speed 2900 MHz
Stock Bus Speed 100 MHz
Average Temperature 85 °C
Caches
L1 Data Cache Size 2 x 16 KBytes
L1 Instructions Cache Size 64 KBytes
L2 Unified Cache Size 1024 KBytes
Cores
Core 0
Core Speed 1412.7 MHz
Multiplier x 14.0
Bus Speed 100.9 MHz
Temperature 84 °C
Threads APIC ID: 0
Core 1
Core Speed 1412.7 MHz
Multiplier x 14.0
Bus Speed 100.9 MHz
Temperature 85 °C
Threads APIC ID: 1
This is strange as your processor shows it has the virtualization technology.
What does the setup log show?
Will be in: ProgramData\AVAST Software\Persistent Data\Avast\Logs
edit: look for IsNgSupported in the log.
Indeed strange as it also shows it is enabled.
Perhaps something to try.
1] Remove avast (use also the removal tool)
2] Reboot
3] Reboot and enter the bios
4] Disable the hardware virtualization there
5] Boot in normal mode
6] Reboot and enter the bios
7] Enable virtualization
8] Boot
9 Install avast (custom install)
I quote one line.
[19:14:14] [info ] [productcond ] [ 5076: 5096] IsNgSupported: virtualization technology is probably disabled in BIOS
This is not true. Virtualization is obviously enabled in the bios, and 3 utilities confirm it.
I’ll try this as a last resort. I want to see if anyone sees something in the setup log that may shed light on this. Obviously, Avast is not correct. I would have thought that the clean reinstall would have done the trick after verifying that virtualization was enabled.