Update BlueStacks 5 first. If the message persists, choose whether to keep Hyper-V for tools such as WSL, Docker, Windows Sandbox, or virtual machines, or disable the related Windows virtualization features for an older BlueStacks setup. Don’t turn off Intel VT-x, AMD-V, or SVM in your firmware: BlueStacks needs hardware virtualization. Treat disabling Memory integrity as a last resort because it reduces a Windows security protection.
Why BlueStacks reports “Incompatible Windows settings”
BlueStacks says this message commonly appears when Hyper-V is enabled and recommends updating BlueStacks 5. The underlying issue is a mismatch between the BlueStacks build or Android instance and Windows’ virtualization configuration. Hyper-V may be enabled, partly configured, or still running at startup; security features such as Memory integrity can also rely on Hyper-V-related technology. Hardware virtualization in UEFI/BIOS and administrator permissions are separate parts of the picture. BlueStacks’ error guidance and Microsoft’s explanation of virtualization conflicts describe these compatibility issues.
In particular, don’t confuse firmware virtualization with Hyper-V. Intel VT-x, AMD-V, or SVM is a processor feature that BlueStacks generally needs enabled. Hyper-V is Windows’ hypervisor and related Windows features; whether to keep it enabled depends on your BlueStacks configuration and other software.
Start with the low-risk fix: update BlueStacks
- Open BlueStacks 5 and select the gear icon → About → Check for updates.
- If an update is offered, download it, run the installer, and choose Update.
- Restart Windows, then launch BlueStacks and test the instance again.
- If the message remains, right-click the BlueStacks shortcut and select Run as administrator. This is a troubleshooting step for configurations that need elevated permissions, not a guaranteed permanent fix.
These update steps are given in BlueStacks’ instructions for the error. Its published Hyper-V requirements page says BlueStacks 5.20 and later can run with Hyper-V enabled or disabled; treat that as BlueStacks’ documented compatibility statement, not a guarantee for every Android instance or Windows setup. BlueStacks Hyper-V requirements.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problems#1 Best Overall
- 1.1 GHz (boost up to 2.4GHz) Intel Celeron N5030 Quad-Core
Choose the right Hyper-V configuration
| Your situation | Recommended path | Trade-off |
|---|---|---|
| You use WSL, Docker Desktop, Windows Sandbox, Hyper-V virtual machines, Credential Guard, or similar tools | Keep Hyper-V-related features available; update BlueStacks and use a compatible instance. | BlueStacks may need the correct feature configuration, administrator access, and a restart. |
| You need an older or non-Hyper-V-compatible BlueStacks setup and do not rely on Windows virtualization features | Disable the applicable Hyper-V-related Windows features, then restart. | WSL, Docker, Sandbox, virtual machines, and some Windows security capabilities may stop working or be affected. |
BlueStacks’ older disable-Hyper-V guidance specifically discusses versions 5.14 and below; that is historical version-specific advice, not proof that every current installation needs Hyper-V disabled. BlueStacks’ disable-Hyper-V instructions.
Keep Hyper-V enabled
- Confirm hardware virtualization is enabled in UEFI/BIOS. If it is off, use the firmware steps below; do not disable it as a way to resolve a Hyper-V conflict.
- Update BlueStacks using the in-app update route above, and launch an Android instance compatible with Hyper-V.
- Enable only the Windows features present and needed for your installation. BlueStacks’ Hyper-V troubleshooting lists Hyper-V, Virtual Machine Platform, Windows Hypervisor Platform, Windows Sandbox, and Windows Subsystem for Linux; availability varies by Windows edition and setup.
- If BlueStacks offers its Run tool or Hyper-V diagnostic option, use it. BlueStacks says its tool can identify configuration problems, complete partially enabled Hyper-V settings, and apply administrator privileges when required.
- Restart Windows, then launch BlueStacks. If it still fails, right-click the BlueStacks shortcut and choose Run as administrator.
These feature and diagnostic recommendations are from BlueStacks’ Hyper-V launch troubleshooting. Running an application as administrator grants it elevated access, so use that workaround only when needed.
Check whether the Hyper-V hypervisor is actually running
- Press Start, search for
msinfo32.exe, and open System Information. - In the details pane, look for:
A hypervisor has been detected. Features required for Hyper-V will not be displayed.
If that message appears, the hypervisor is running even if Windows Features does not show an obvious Hyper-V entry. Related virtualization components or security features may keep it active, and the visible feature list can differ between Windows editions. Microsoft documents this check in its virtualization troubleshooting guidance.
Rank #2
- 256 GB SSD of storage.
- Multitasking is easy with 16GB of RAM
- Equipped with a blazing fast Core i5 2.00 GHz processor.
Disable Hyper-V for an older or incompatible setup
Before changing Windows features: this route can disrupt WSL, Docker Desktop, Windows Sandbox, Hyper-V virtual machines, and other tools that depend on Windows virtualization. If you use any of them, prefer the keep-Hyper-V path unless you are prepared to reconfigure those tools.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Use Windows Features
- Press Start and search for Turn Windows features on or off.
- Open the Windows Features dialog. For the non-Hyper-V path, clear the applicable entries that are present on your system: Hyper-V, Windows Hypervisor Platform, Windows Sandbox, Virtual Machine Platform, and Windows Subsystem for Linux.
- Select OK and restart Windows when prompted.
Do not assume every computer has all of these entries or that every setup needs all of them disabled. BlueStacks lists these components for its non-Hyper-V troubleshooting path; Windows edition and installed features vary. See BlueStacks’ Windows Features instructions.
Change whether the hypervisor launches at boot
As an alternative, open Command Prompt as administrator and run:
Rank #3
- 14" diagonal, 1366x768 resolution, HD BrightView LED, Glossy NON-TOUCH Display
bcdedit /set hypervisorlaunchtype offRestart Windows afterward. This changes the hypervisor’s boot behavior; it does not necessarily remove or disable every related Windows feature. If BlueStacks still detects a conflict, check Windows Features and Memory integrity rather than repeatedly toggling settings. BlueStacks documents this command in its disable-Hyper-V guide.
Use Microsoft’s DISM or PowerShell alternative
Instead of the boot command, Microsoft documents disabling the Hyper-V hypervisor with either an elevated Command Prompt:
DISM /Online /Disable-Feature /FeatureName:Microsoft-Hyper-V-Hypervisoror elevated PowerShell:
Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-HypervisorThese are alternatives, not commands to run together. Restart after changing the feature. Refer to Microsoft’s virtualization troubleshooting instructions.
Rank #4
- EFFORTLESS EVERYDAY PERFORMANCE: Powered by Intel Celeron N4020 processor and Windows 11 Home system, delivering reliable, low-power efficiency for daily tasks like document editing, email, online classes, and web browsing
- 15.6-INCH FULL HD DISPLAY: Enjoy immersive visuals on the 15.6" FHD (1920x1080) anti-glare screen with micro-edge bezels. Delivers clear details and comfortable viewing for long study sessions, working on spreadsheets, and video playback
- RESPONSIVE MULTITASKING & STORAGE: Built with 4GB LPDDR4 RAM and 128GB eMMC storage for smooth daily essential use. Expand your storage by up to 1TB via the integrated TF card slot to easily store movies, photos, and working files
- ADVANCED CONNECTIVITY: Outfitted with 2x Full-Featured Type-C ports for data transfer, fast charging, and dual-monitor output, alongside 2x USB 3.2 Gen1 ports and a 3.5mm audio jack for complete peripheral compatibility
- LIGHTWEIGHT & SILENT OPERATION: Slim and portable for effortless travel or commuting. Features a 1MP HD webcam for remote meetings, 38Wh battery with 45W Type-C fast charging, and a fanless silent design for peaceful work environments.
Turn off Memory integrity only as a fallback
Try this only if you chose the non-Hyper-V path, restarted after changing the relevant features, and BlueStacks still cannot launch. Memory integrity is a Windows security feature that depends on Hyper-V-related technology; disabling it reduces a security protection, so it should not be the first fix.
- Open Windows Search and search for Core isolation.
- Open Core isolation details.
- Turn Memory integrity off, then restart Windows.
BlueStacks includes this step in its older-configuration troubleshooting; Microsoft explains the security feature’s Hyper-V relationship in its virtualization guidance. If BlueStacks works without this change, leave Memory integrity enabled; after resolving compatibility, re-enable it if your setup allows.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Enable hardware virtualization in UEFI/BIOS
If virtualization is disabled in firmware, enabling or disabling Hyper-V in Windows will not fix that separate requirement. Microsoft’s general route on Windows 10 and 11 is:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- 【Efficient Performance】 Powered by Intel Core i3 processor (2 cores, 4 threads, up to 3.4GHz) with 12GB RAM and 256GB SSD. Handles multitasking, office software, online classes, and HD video streaming smoothly. Integrated Intel UHD Graphics 620
- Backlit Keyboard & Complete Package】Comes with a cool backlit keyboard. Comes with awebcam, dual stereo speakers (8Ω/1.0W each), DC charger, and user manual – ready for late-night studying, online classes, video conferencing, and daily productivity
- 【Vibrant Display】 15.6-inch Full HD (1920x1080) anti-glare screen with 16:9 aspect ratio delivers crisp images and vivid colors – perfect for studying, watching lectures, or entertainment. Thin-bezel design maximizes viewing area
- 【Fast Connectivity & Expansion】 Equipped with WiFi 6 (802.11ax) and Bluetooth 5.2 for stable, high-speed wireless. Features 3 x USB 3.0, HDMI 2.1, Type-C (supports PD3.0 fast charging), and a TF card slot expandable up to 2TB – easily connect external monitors, mice, drives, or expand storage for all your files
- 【Long Battery Life & Portable】 Built-in 11.55V 5000mAh/57.75Wh high-capacity battery delivers approximately 7 hours of mixed-use battery life – enough for a full day of classes and assignments. Lightweight at just 1.63kg (3.6 lbs) and 19.5mm thin, plus a compact packing size – easily slips into a backpack for campus, library, or coffee shop
- Open Settings → System → Recovery.
- Under Advanced startup, select Restart now.
- Choose Troubleshoot → Advanced options → UEFI Firmware Settings → Restart.
- In the firmware menus, enable the setting named by your manufacturer, such as Intel Virtualization Technology, Intel VT-x, AMD-V, SVM Mode, or Virtualization Technology.
- Save the change and restart Windows.
The exact menu and label depend on the computer or motherboard. Change only the necessary firmware setting; see Microsoft’s virtualization instructions.
If the error remains
- After changing Windows Features or boot behavior: restart Windows, then check
msinfo32.exeto see whether a hypervisor is still detected. - If you chose the non-Hyper-V path: check whether Virtual Machine Platform, Windows Hypervisor Platform, or another relevant feature remains enabled. Check Core isolation → Memory integrity only if needed.
- If you chose the Hyper-V path: confirm that the relevant Windows features are enabled and use a compatible BlueStacks instance.
- If the machine reports no usable virtualization: confirm Intel VT-x, AMD-V, or SVM is enabled in firmware.
- If BlueStacks launches only with elevation: use Run as administrator as a permissions workaround. For a recurring need, you can right-click the shortcut, open Properties → Compatibility, select Run this program as an administrator, and apply. This gives BlueStacks administrator access whenever launched through that shortcut.
- If the issue followed a Windows update: check the actual feature and hypervisor state rather than assuming the update enabled Hyper-V. An update can expose a mismatch by changing virtualization, security, or feature states.
- On a work-managed PC: Group Policy, Credential Guard, endpoint security, or organizational restrictions may block changes. Contact your administrator rather than bypassing those controls.
Restore the Windows settings you changed
If you disabled Windows features or changed the hypervisor boot setting, restore only the capabilities you previously used. Re-enable the applicable entries in Turn Windows features on or off. If you ran the boot command, an elevated Command Prompt can restore automatic hypervisor launch:
bcdedit /set hypervisorlaunchtype autoRe-enable Memory integrity under Core isolation details if you turned it off, then restart Windows. Check that WSL, Docker, Sandbox, or virtual machines you rely on work again.
BlueStacks Hyper-V requirements published by BlueStacks
BlueStacks’ cited Hyper-V requirements page lists Windows 10 version 1903 or later, or Windows 11; an Intel or AMD processor; at least 4 GB RAM; at least 5 GB available storage; administrator access; up-to-date graphics drivers; and hardware virtualization enabled. It also lists Hyper-V enabled for the Hyper-V configuration and says Hyper-V Administrators group membership may be needed in some configurations. These are BlueStacks-published baseline details, not a guarantee that a particular game or multiple instances will run well; current support requirements can change. BlueStacks’ Hyper-V requirements page.
Do not add yourself to the Hyper-V Administrators group unless a permissions issue or BlueStacks’ diagnostic guidance calls for it. BlueStacks documents this elevated Command Prompt command, replacing <username> with the Windows account name:
net localgroup "Hyper-V Administrators" <username> /addA restart may be required. The account must have administrator rights to perform the change.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
