u/Particular-Cook2919

BlueStacks 5 breaks Virtualization detection on Ryzen 7 8700G (Zen 4) due to internal engine bug

Just wanted to give a heads-up to anyone running the new AMD Ryzen 7 8700G APU. There is a severe virtualization layer conflict in BlueStacks 5 (Pie 64-bit engine).

  • The Scenario: To get rid of the horrible mouse acceleration in shooters like Free Fire MAX (since BlueStacks removed the Raw Input toggle from their UI), you have to manually set bst.force_raw_mode="1" in bluestacks.conf.
  • The Bug: The moment this flag is enabled, BlueStacks fails to detect SVM. It throws a false "VT Disabled" error and locks you out, even though Virtualization is 100% Enabled in BIOS and Windows Task Manager shows it clearly.
  • The Proof: Tested on multiple 8700G systems on Discord—it's 100% reproducible.
  • The Support Response: Absolute corporate ignorance. Their support keeps sending automated bot replies telling users to "reinstall" or that "BlueStacks doesn't need hardware optimization", completely ignoring that their own Pie64 engine calls the wrong virtualization registers when raw input is forced on Zen 4.

If you are on AM5 and notice your emulator breaking over config changes, it’s not your PC. It’s their code.

u/Particular-Cook2919 — 5 days ago

Legacy Raw Mode is broken on Ryzen 7 8700G / AM5. Fix your hardware check guys.

Hi bluestacks team,

I am writing this here because your zendesk support is just sending me robotic copy-paste answers and i am losing my mind. There is a serious bug with BlueStacks 5 Raw Mode on the new AMD AM5 platform, specifically with the Ryzen 7 8700G APU.

When i try to force raw mode from the config file (bst.force_raw_mode="1" and bst.status.raw_mode="1"), bluestacks completely fails to see my virtualization and pops up the "VT disabled" error.

And before your support tells me to enable it in bios, please look at what i have already done. I am not a newbie.

  1. BIOS: SVM is 1000% ENABLED. I even disabled IOMMU to stop windows from touching it.
  2. Windows Security: Core isolation and Memory integrity are completely DISABLED. Virtualization-Based Security (VBS) is "Not enabled".
  3. Hyper-V: Completely uninstalled via DISM command line (Microsoft-Hyper-V-All, VirtualMachinePlatform, HypervisorPlatform are all gone). My hypervisorlaunchtype is strictly set to OFF.
reddit.com
u/Particular-Cook2919 — 6 days ago