Can You Run Multiple Instances of RetroArch on Windows?

Running multiple instances of RetroArch on a single Windows machine is technically possible but requires manual configuration since the application does not support this feature out of the box. This guide explains the limitations of the standard installation, details the file duplication method required to bypass single-instance restrictions, and offers troubleshooting tips for managing separate configuration files and controller inputs effectively.

Understanding the Single-Instance Limitation

By default, RetroArch is designed to run as a single application process. When you launch the executable, it checks for existing instances and typically focuses on the open window rather than starting a new one. This behavior is intentional to prevent conflicts over resources such as audio drivers, video contexts, and controller input handles. For most users, this is preferable, but enthusiasts looking to host local netplay sessions on one PC or run different cores simultaneously will find this restriction limiting.

The Folder Duplication Method

To bypass the single-instance lock, the most reliable method is to create a completely independent installation of RetroArch. This involves copying the entire installation folder to a new location on your hard drive. Once copied, you should rename the folder to distinguish it, such as “RetroArch_Instance_2.” Inside this new folder, the executable file can also be renamed to prevent Windows from associating it with the original process ID.

Configuring Independent Settings

Running two copies of the executable is only half the battle; you must ensure they do not share configuration files. Upon launching the new instance for the first time, navigate to the Settings directory within the interface. You need to verify that the configuration file path is set to store files within the new folder directory rather than the default AppData location shared by the original installation. This ensures that core settings, shaders, and input configurations remain separate, preventing one instance from overwriting the settings of the other.

Managing Controller Inputs

One of the most common issues when running multiple instances is input conflict. Both instances may try to claim the same controller, causing input lag or unresponsive buttons in one of the windows. To resolve this, you must manually configure the input settings for each instance. Assign specific controllers to specific user slots in the first instance and different controllers to the second instance. Using port-specific binding rather than global automatic configuration is essential for a smooth multiplayer experience on a single machine.

Performance and Stability Considerations

While running multiple instances is feasible, it does double the demand on your system resources. Each instance loads its own cores and manages its own video rendering, which can strain the CPU and GPU. It is recommended to close unnecessary background applications and lower the video resolution settings within RetroArch if you experience frame rate drops. Additionally, always ensure you are using the same version of RetroArch for both instances to avoid compatibility issues when utilizing features like local netplay between the two windows.