BotDaddyBotDaddy
All guides

The BotDaddy Tools screen

Three utilities for fixing things. One of them is destructive, and it's clearly marked below.

The BotDaddy Tools screen showing the GnBots import, Disable Virtualization and Rebuild Instances cards
Import, virtualization, rebuild. Only the last one destroys anything.

Import from GnBots

Finds your GnBots settings.json and imports the accounts, logins and supported action settings from it.

Auto-find locates the file for you — it lives in the profiles folder inside your GnBots install. Preview Import shows exactly what will be brought across before anything is written, including what's being skipped.

Only actions BotDaddy has an equivalent for are imported; everything else is listed so you can see what didn't come across. Nothing is deleted from GnBots.

Full walkthrough: migrating from GnBots.

Disable Virtualization

Turns off Hyper-V, VBS, Windows Sandbox, WSL, Containers and the boot hypervisor, so LDPlayer runs at full speed rather than on top of another hypervisor.

It backs up your current configuration first and is fully reversible — "Revert to Saved Configuration" puts everything back. It needs Administrator approval and a reboot to fully apply.

This is the fix for the most common reason LDPlayer won't start at all. If your emulators refuse to launch or run at a crawl, start here — see Hyper-V and virtualization errors.

Rebuild Instances

Wipes and recreates LDPlayer instances with the recommended profile, then reinstalls the game.

This is destructive. Rebuilding permanently deletes each selected instance and creates a fresh one. Everything on those instances is lost — including the game's saved login, so the account has to sign in again. Make sure the account's credentials are filled in before you rebuild its instance.

It only runs while the bot is stopped. Pick the instances from the list, or use Select all / Clear. There's one option:

Rename instances to their account names — after rebuilding, each instance is renamed to the account bound to it, so LDPlayer's own list reads the way your account list does. An instance with no account bound, or a blank account name, keeps its original name. Where several accounts share one instance, the first one bound to it is used.

When to rebuild

  • The instance has become bloated or corrupted and boots unreliably.
  • The instance was created by another bot and isn't set up the way BotDaddy expects.
  • The game on it is broken in a way reinstalling from the Accounts screen doesn't fix.

For an out-of-date or missing game, use Update / Install Game on the account row first — that isn't destructive and is usually enough.

Troubleshooting

Rebuild is refused. The bot is running. Stop it first.

The game file isn't downloaded yet. The card says so, and clicking Rebuild downloads it first.

I rebuilt an instance an account was bound to. The binding survives — LDPlayer gives the new instance a fresh index and the account is repointed at it automatically.

LDPlayer renumbered everything. Restarting the app re-reads the list.

Disable Virtualization asked for Administrator. Expected — it's changing Windows features. Approve it, and reboot afterwards.

I closed the app mid-rebuild. The history and logs for that run are lost. Check the instance list in LDPlayer to see where it got to.