Virtualization technology could improve the performance of your computer and make NOX Player run easier and faster. Does your computer support virtualization (aka VT-x, Virtual Technology)?
Step 1. Use LeoMoon CPU-V
To check if your computer supports VT, you can refer to: LeoMoon CPU-V. It only detects if your CPU supports hardware virtualization, but it also detects if hardware virtualization is enabled in BIOS.
- If the result of your check shows a green check mark under VT-x Supported, it means your computer supports virtualization. If it's a red cross, then your computer doesn't support VT, but you can still install Nox as long as you meet the installation requirements.
- If the result of your check shows a green check mark under VT-x enabled, it means that VT is already enabled in your BIOS. If it's a red cross, follow the steps below to activate it.
Step 2. Find your BIOS type
Press Win + R to open "Run" box, enter "Dxdiag" and click "OK". Then you will see your BIOS information as shown in the screenshot above.
Step 3. Search Google for how to enable VT on your BIOS
Usually entering BIOS requires pressing a designated key repeatedly when your computer starts up. The designated key can be one of the function keys or the ESC key depends on your computer brand. Once you enter BIOS mode, search for Virtualization, VT-x, Intel Virtual Technology or whatever says "virtual" and enable it. When finished, shut down your computer completely and then turn it back on.
Now virtualization is enabled and the performance of Nox App Player is even better
Step 4. Watch out for conflicts
If you are using Windows 8 or Windows 10, there may be conflicts between VT technology and Microsoft Hyper-V. Please disable Hyper-V by following these steps: go to Control Panel -> Programs and Features -> Turn Windows features on or off -> uncheck the box before Hyper-V.
Step 5. Authorize VT
If your VT is enabled in BIOS, but the result of LeoMoon check still shows a red cross under VT-x enabled, it is quite possible that your antivirus software has blocked this function. Taking Avast! for example, to solve this problem …