BotDaddyBotDaddy
All guides

Disable MuMu Player's remote service

MuMu Player installs a Windows background service called MuMuPlayerRemoteService. On a large farm it can bog MuMu Player down until it stops starting instances. If you run BotDaddy on MuMu Player and see the signs below, switch it off. It takes a minute, and BotDaddy doesn't need it.

The signs

  • MuMu Player's own window gets slow or stops responding.
  • Instances stop starting, or start only after a long wait, while the ones already running carry on.
  • BotDaddy's activity feed says "Host recovery: restarting the emulator itself", and every MuMu instance closes and reopens, sometimes more than once.

It builds up over time, and the more instances you have, the sooner it happens. With a handful of instances you may never notice it. A farm with dozens can run into it within minutes of MuMu Player starting.

Why it happens

MuMu uses this service for its remote features. To keep them up to date, it asks MuMu Player's main window about every one of your instances, several times a second, all the time, whether or not you ever use those features.

That main window is also what starts and stops your instances, and it deals with requests one at a time. With enough instances it falls behind, the queue keeps growing, and eventually it stops answering altogether, including when BotDaddy asks it to start an instance. BotDaddy can restart MuMu Player when that happens, but while the service is on, the queue simply builds up again.

How to switch it off

  1. Open the Start menu, type Services, right-click Services and choose Run as administrator.
  2. Find MuMuPlayerRemoteService in the list (it's in alphabetical order) and double-click it.
  3. If Service status says Running, click Stop.
  4. Set Startup type to Disabled.
  5. Click OK.

Then give MuMu Player a fresh start: stop the bot, close MuMu Player completely, open it again, and start the bot.

Or with two commands

If you prefer, open PowerShell as administrator and run:

Stop-Service MuMuPlayerRemoteService
Set-Service MuMuPlayerRemoteService -StartupType Disabled

What you lose

Only MuMu's remote features. MuMu Player itself, your instances, the game and BotDaddy all work exactly as before.

Undoing it

Open Services as administrator again, double-click MuMuPlayerRemoteService, set Startup type back to Automatic, click Start, then OK.

Worth knowing

BotDaddy never changes this for you. It's a Windows setting that belongs to another program, so the choice is yours.

A MuMu Player update may switch it back on. If the signs come back after MuMu updates, check the service again.

Instances that never start while your monitor is off are a different problem. MuMu's Vulkan graphics mode can't start an instance without a display. In BotDaddy, set Settings → Emulator → Graphics to DirectX, which is the default and works with the monitor off. See MuMu Player setup for Viking Rise.

One instance failing while the rest are fine isn't this either. This problem hits MuMu Player as a whole. A single bad instance can be rebuilt with Tools → Rebuild Instances.

Still stuck? Ask in our Discord and attach your latest backend log from Documents\BotDaddy\logs.