Tutorial How to root BlueStacks 5 using BlueStacks Root GUI (Windows) (All versions)

[AndnixSH]

One tool, a couple of clicks, and you've got root on current BlueStacks 5 - including the latest 5.22.x. The old "Android system doesn't meet security requirements" popup is patched out automatically, so you no longer have to hunt down 5.21. The core job is just toggling root. A root manager like Kitsune Mask is optional.

What You Need​

• Windows 10 or later
• BlueStacks 5, BlueStacks 5 China, or MSI App Player
• Admin rights (5.22.150.1014+)
• BlueStacks Root GUI - grab the latest .exe from the Releases page

No uninstall or downgrade required - the tool patches your existing install in place.

Main Method - Current Builds (5.22.150.1014+)​

This gets root working for apps without touching /system or installing anything inside the guest.

1. Create the instance first. On a fresh install, open BlueStacks once so it builds and boots your instance, then close it. (The guest su only appears after the first boot.)
2. Run the GUI as admin. Right-click the .exe → Run as administrator. It auto-detects your install and lists your instances. It'll show the engine-patch button since you're on a patch-mode build.
3. Patch the engine (once per install). Click "Patch BlueStacks Engine (required for root)" → Yes. It closes all BlueStacks processes, then patches and backs up HD-Player.exe and HD-MultiInstanceManager.exe. This kills the security/tamper shutdown.
4. Toggle Root (per instance). Tick your instance → click "Toggle Root." This sets the root flags and patches the guest su inside Data.vhdx. If it says su isn't there yet, boot the instance once, close it, and toggle again.
5. Restart and verify. Launch the instance — it boots with no security popup, and root checkers (or Kitsune/Magisk) will see root. Done.

Classic Builds (5.22.130 and older / MSI)​

Older/MSI builds use the original flag method instead of the engine patch:

1. Select your instance → Toggle Root ON → Toggle R/W ON.
2. Launch the instance. You've got root. (R/W is only needed if you're going to write to /system, e.g. for the optional Kitsune step below.)

Kitsune Mask (Optional)​

Only if you want managed superuser grants and modules (Zygisk, Play Integrity Fix, LSPosed, etc.). This is a more involved setup with real emulator gotchas, so skip it unless you actually need modules.

• On classic builds: with Root + R/W ON, install the pinned Kitsune Mask APK (drag-drop) → open it → Install → Next → Direct Install to /system → reboot. Then in the GUI, turn Root OFF but leave R/W ON. Reopen Kitsune to confirm it's active.
• To flash a module: don't use BlueStacks' file picker (it hands Magisk an "Invalid Uri"). Instead, start the instance, tick it in the GUI, and use "Install Magisk Module (.zip)" - it pushes and flashes for you. Close/reopen the instance to activate.

Full module + hiding walkthrough is in the companion guide linked in the repo.

Keep Root After Updates​

Root survives normal restarts, but a background auto-update can silently replace the patched files and bring the security check back. If that happens, just re-run "Patch BlueStacks Engine." To prevent it, run this in an admin PowerShell:

sc.exe stop BstHdUpdaterSvc
sc.exe config BstHdUpdaterSvc start= disabled
schtasks /Change /TN "BlueStacksHelper_nxt" /DISABLE

The scheduled task is the important one - some builds don't even have the BstHdUpdaterSvc service (you'll get "service does not exist," which is fine), but they still ship the task. Disable whichever exist. Note: setting bst.auto_update="0" in the conf does not work - it's ignored.

Quick Troubleshooting​

• No instances / "Path Not Found" → run as admin; clean-reinstall via the official cleaner if needed.
• "Permission denied" patching HD-MultiInstanceManager → the Manager window was open; latest version closes it automatically, so update and re-run.
• "su isn't in Data.vhdx yet" → boot the instance once, close it, toggle again.
• Root stopped working later → it auto-updated and reverted; re-patch, then disable updates above.
• Won't launch on a locked-down/corporate PC → patching invalidates the exe signature, which WDAC/AppLocker may block. Use "Undo Engine Patch" to restore the signed original. (Doesn't affect normal home PCs.)

Credit: RobThePCGuy on GitHub - GitHub - RobThePCGuy/BlueStacks-Root-GUI: A python application to toggle root access and enable read/write (R/W) permissions for your BlueStacks instances.