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.
No uninstall or downgrade required - the tool patches your existing install in place.
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.). If you want to create another instance, open the BlueStacks Manager
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.
1. Turn on Root + R/W. In the GUI, make sure Toggle Root is ON and Toggle R/W is ON for your instance.
2. Download the APK. Grab the latest Kitsune Magisk APK or older version of Kitsune Mask APK (The original repo is abandoned, so use this copy.)
3. Install it in the instance. Launch the instance from the Multi-Instance Manager, then drag-and-drop the APK into the window to install it.
4. Open Kitsune Mask. Launch the app inside BlueStacks.
5. Direct Install to /system. Tap Install → Next → Direct Install to /system. If that option is missing, close and reopen the app. Let it finish and close the instance
6. Fix the toggles. Back in the GUI, turn Toggle Root OFF, but leave Toggle R/W ON. (This combo is what makes it stick.)
7. Verify. Reopen Kitsune Mask - it should show as installed and active.
Flashing modules: don't use BlueStacks' file picker (it gives 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.
See full rooting guide: GitHub - RobThePCGuy/Root-Bluestacks-with-Kitsune-Mask: Steps to root Bluestacks 5 with Kitsune Mask without any external tools.
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.
"Permission denied" while patching HD-MultiInstanceManager.exe
"Toggle Root" says su isn't in Data.vhdx yet
Root worked, then stopped after a while
R/W toggle doesn't persist
"Direct Install to /system" option missing
Installing a module fails with "Invalid Uri"
Toggle operation errors
BlueStacks won't launch after patching (locked-down / corporate 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.
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.). If you want to create another instance, open the BlueStacks Manager
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:- Select your instance → Toggle Root ON → Toggle R/W ON.
- 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)
Do this only if you want a Magisk-style manager for superuser grants and modules. Works on the latest BlueStacks too, as long as you've done Part 1 first.1. Turn on Root + R/W. In the GUI, make sure Toggle Root is ON and Toggle R/W is ON for your instance.
2. Download the APK. Grab the latest Kitsune Magisk APK or older version of Kitsune Mask APK (The original repo is abandoned, so use this copy.)
3. Install it in the instance. Launch the instance from the Multi-Instance Manager, then drag-and-drop the APK into the window to install it.
4. Open Kitsune Mask. Launch the app inside BlueStacks.
5. Direct Install to /system. Tap Install → Next → Direct Install to /system. If that option is missing, close and reopen the app. Let it finish and close the instance
6. Fix the toggles. Back in the GUI, turn Toggle Root OFF, but leave Toggle R/W ON. (This combo is what makes it stick.)
7. Verify. Reopen Kitsune Mask - it should show as installed and active.
Flashing modules: don't use BlueStacks' file picker (it gives 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.
See full rooting guide: GitHub - RobThePCGuy/Root-Bluestacks-with-Kitsune-Mask: Steps to root Bluestacks 5 with Kitsune Mask without any external tools.
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:
Code:
sc.exe stop BstHdUpdaterSvc
sc.exe config BstHdUpdaterSvc start= disabled
schtasks /Change /TN "BlueStacksHelper_nxt" /DISABLEThe 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.
Common Issues
No instances listed / "Path Not Found"- Run the GUI as Administrator
- Verify registry keys exist: HKLM\SOFTWARE\BlueStacks_nxt (Normal), HKLM\SOFTWARE\BlueStacks_nxt_cn (China), or HKLM\SOFTWARE\BlueStacks_msi5 (MSI)
- Perform a clean reinstall using the official cleaner tool
"Permission denied" while patching HD-MultiInstanceManager.exe
- This means the Multi-Instance Manager window was open, locking the file. The tool now closes it automatically before patching - make sure you're on the latest version, then re-run "Patch BlueStacks Engine."
"Toggle Root" says su isn't in Data.vhdx yet
- The guest su only materializes after the instance's first boot. Start the instance once, shut it down, and toggle root again.
Root worked, then stopped after a while
- BlueStacks likely auto-updated and reverted the patch. Re-run "Patch BlueStacks Engine," then follow Keep Root After Updates.
R/W toggle doesn't persist
- Ensure BlueStacks processes were fully terminated (kill leftovers in Task Manager if needed)
- Keep R/W ON after installing Kitsune Mask
"Direct Install to /system" option missing
- Verify both Root and R/W are ON before launching the instance
- Close and reopen the Kitsune Mask app within BlueStacks
Installing a module fails with "Invalid Uri"
- BlueStacks' file picker gives Magisk/Kitsune a Windows-style path it can't open. Instead, start the instance, tick it in the GUI, and use "Install Magisk Module (.zip)" - it pushes the module in and flashes it via Magisk for you. Close and reopen the instance to activate it. (If the ADB root shell isn't reachable, it drops the zip in the instance's Download folder so you can flash it by hand.)
Toggle operation errors
- Check the status bar in the GUI for the error message
- A full log is written to %TEMP%\BlueStacksRootGUI.log - helpful when reporting an issue
BlueStacks won't launch after patching (locked-down / corporate PCs)
- Patching HD-Player.exe invalidates its digital signature. Machines that enforce Windows Defender Application Control (WDAC) or strict AppLocker publisher rules may then block the patched binary from running. This does not affect normal home PCs.
- If you're on a managed machine and BlueStacks silently fails to start after patching, use "Undo Engine Patch" to restore the signed original, or run on a machine without those policies.
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.
Last edited: