MuMuPlayer Help Center

Confirm that your Windows or macOS version is supported, check available storage and administrator permissions, and make sure the installer was downloaded completely. If an earlier installation failed, remove its remaining files, restart the computer, and run the installer again.

Back up game data and other important files before changing the Android environment. Confirm that the games and apps you use support the target Android version, because an upgrade can affect compatibility, local data, login status, and existing settings.

Initialization can fail when required components cannot be downloaded or written to disk, virtualization is unavailable, security software blocks a process, or the installation directory has restricted permissions. Restart the computer, verify the network and storage location, and try again.

Check whether the internet connection is stable and whether a firewall, proxy, VPN, or security tool is blocking the download. Make sure the installation drive has enough free space and write permission, then retry with a newly downloaded installer.

Verify that you obtained the installer from the intended download page. Review the security warning and allow the installer only after confirming its source. You may also add the relevant installation folder or process to the security tool's allowlist before retrying.

Restart the computer, confirm that hardware virtualization is enabled when required, and check for blocked MuMuPlayer processes. Install pending system and graphics updates, close conflicting virtualization software, and record any error code shown during startup.

A startup stall at 98% can be related to virtualization, security software, damaged instance data, disk access, or conflicting system components. Restart the computer, check virtualization and security settings, and test a newly created instance if the existing one may be damaged.

Update the graphics driver, install pending operating system updates, and close overlays or background utilities that may interfere with rendering. If the problem continues, try another rendering mode or test with default performance settings.

The message usually appears when a required MuMuPlayer process or driver is blocked. Review the security software's recent events and allow the relevant process or folder after confirming it belongs to your installation, then restart MuMuPlayer.

Close unused instances and high-usage background programs, keep sufficient free space on the installation drive, and remove instances you no longer need. A heavily loaded hard drive or an excessive number of startup apps can also delay initialization.

Error 126 is commonly associated with missing or damaged graphics components, an incorrect driver installation, or a conflict on systems with integrated and dedicated GPUs. Reinstall or update the appropriate graphics driver, restart Windows, and confirm that both display adapters are detected correctly.

Open MuMuPlayer performance or display settings and select a supported frame-rate option, then choose the matching frame-rate setting inside the game. Keep the graphics driver current. The maximum available frame rate depends on the game, emulator version, and computer hardware.

Switch between available rendering modes, update the graphics driver, and close applications using significant CPU, GPU, or memory resources. Lower the emulator resolution, frame rate, or in-game graphics quality to determine whether the current settings exceed the computer's capacity.

Open Windows graphics settings or the NVIDIA, AMD, or Intel control panel and assign the MuMuPlayer executable to the high-performance GPU. Restart the emulator after saving the change, then confirm GPU usage with the system performance monitor.

Start with a moderate resolution and the default DPI, then increase them only when the game remains stable. Higher resolution improves image detail but uses more GPU and memory resources, while an unsuitable DPI can affect interface scaling and touch coordinates.

Launch the game, open the key-mapping panel, and begin with an available preset when one is provided. Move, add, or remove controls to match the game's current interface, test them during gameplay, and save the profile before closing the editor.

A game publisher may limit emulator access, require a specific login method, or temporarily lack compatibility with the current Android environment. Check the game's current requirements and MuMuPlayer compatibility information before trying another Android instance.

Update both the game and MuMuPlayer, restart the instance, and clear only the game's temporary cache when it is safe to do so. Confirm that the selected Android version and device configuration are supported, and back up local data before reinstalling the game.

Make sure the game window is active and that the selected control profile matches the current resolution and game interface. Reload the profile or recreate affected controls if a game update moved buttons or changed the screen layout.

A game update can change its Android requirements, rendering method, login process, or emulator policy. Test another supported Android instance only after protecting your data, and check for a MuMuPlayer compatibility update or game-specific notice.

Open MuMuPlayer settings and locate the shared folder or storage path option. Select a local folder that your user account can read and write, save the change, and restart the affected instance if the new location is not detected immediately.

Bridged networking can be useful when an Android instance must appear as a separate device on the local network, such as during development or device testing. Choose the correct physical network adapter and confirm that firewall and network permissions allow the connection.

Confirm that the supported Windows-side MuMuPlayer session is online, both devices use the expected account, and device binding is complete. Check the network connection on both devices, refresh the session list, and repeat the pairing process when necessary.

Assign fewer CPU cores and less memory to background instances, reduce their resolution and frame rate, and disable sound or unnecessary visual features where available. Run only the number of instances your hardware can support without sustained CPU, GPU, or memory saturation.

Confirm that the file type is supported, the Android instance is running, and the destination has available storage. If drag and drop still fails, move the file through the shared folder and check that both Windows and the instance have permission to access it.

Check the network connection, account credentials, verification code, and the date and time configured on the computer. Avoid repeated login attempts when a security limit appears. Remember that a game account and a MuMuPlayer account may be managed by different service providers.

Identify which data is stored by the game account and which files exist only inside the local instance. Back up instances, screenshots, recordings, and shared-folder files before changing computers, then reinstall MuMuPlayer and restore only data supported by the relevant backup method.

No. MuMuPlayer instances are generally separate Android environments. A game or app may synchronize data through its own account or cloud system, but local files, settings, and login sessions are not necessarily shared between instances.

Confirm that you signed in with the same store, game, or service account used for the purchase. Refresh the app, restart the instance, and check whether the benefit is limited by platform, region, server, account type, or application version.

Use a dedicated instance for each account or workflow, name the instances clearly, and avoid importing one instance over another. Back up important local data and verify the active account before making purchases or changing game settings.

Install Pocket MuMu on the mobile device, sign in with the account expected by the Windows-side session, and complete device binding. Keep MuMuPlayer running and online, select the available computer or instance, and follow any connection or authorization prompt.

Pocket MuMu is provided for supported iOS and Android devices. Compatibility can depend on the mobile operating system version, app release, region, and the Windows-side MuMuPlayer version, so review the current download information before installation.

Start with the Pocket MuMu help topics for installation, account sign-in, device binding, remote connection, control gestures, notification permissions, and session management. Make sure the mobile and computer versions are compatible before troubleshooting individual features.

Remote actions depend on the current Pocket MuMu version, the state of the Windows computer, and whether the MuMuPlayer session is already available. The computer must remain powered on, connected, and configured to allow the supported remote workflow.

Allow notifications for Pocket MuMu in the mobile operating system, confirm that the correct account and computer are bound, and check that the Windows-side session remains online. Battery optimization or background app restrictions can also delay mobile notifications.

The current macOS version is intended for supported Apple silicon Macs, including compatible M-series models. Intel-based Macs are not supported by that build. Check the download page before installation because operating system and model requirements may change between releases.

Open System Settings and review Privacy & Security for a message about the blocked application. Confirm that the DMG finished downloading, move the app to the expected Applications location when instructed, allow it to open, and then launch it again.

Close memory-intensive apps, keep adequate free storage, and select emulator graphics and resolution settings appropriate for the Mac model. Keep macOS and MuMuPlayer current, and avoid running more instances than the available memory can support.

macOS may require approval for application launch, input monitoring, files, screen access, or other features. Open Privacy & Security, review the permission requested by the feature, grant only the access you intend to use, and restart MuMuPlayer.

No. Apple silicon and Intel processors use different architectures, and the current Apple silicon build is not an Intel Mac installer. Use only a version that explicitly lists support for your Mac's processor and operating system.

Use the MuMuManager documentation that matches your installed MuMuPlayer version. Start by listing available instances and testing a read-only or single-instance command, then add start, stop, configuration, or batch operations after confirming the target identifiers and parameters.

Start the intended Android instance, enable the supported debugging connection, and use ADB to verify that the device is visible. Android Studio should then list the instance as a deployment target. Resolve duplicate or unauthorized ADB connections before starting a debugging session.

Common workflows include installing APK files, connecting with ADB, collecting logcat output, testing network behavior, inspecting application data available to the developer, and starting or stopping instances through supported command-line tools.

Locate the instance's supported ADB address or port, confirm that the local ADB executable is available, and connect from a terminal. After the device appears in the ADB device list, you can install test packages, collect logs, run shell commands, or connect Android Studio.

Confirm that the instance is running and that the address, port, and ADB version are correct. Disconnect stale devices, restart the ADB server, and retry the connection. A firewall, conflicting Android tool, or an instance restart may change the available connection.

Use supported MuMuManager or command-line operations with explicit instance identifiers. Validate each command against one test instance, handle errors and timeouts, and avoid sending a large batch of start operations that exceeds the computer's available CPU and memory.