How do I install and use CH Products Control Manager on Windows 10 or 11?

CH Products Control Manager can run on Windows 10 and some Windows 11 installations, but its legacy virtual driver may be blocked by modern Windows security. Most simmers should use Windows’ built-in HID support; install Control Manager only for a combined virtual controller, advanced mappings or an existing CH profile.

Do I need CH Products Control Manager?

CH USB yokes, pedals, throttles and joysticks normally work as standard Windows game controllers without Control Manager. Modern simulators can detect the separate devices and assign their axes and buttons directly, which avoids an extra driver and mapping layer.

If you only need ordinary simulator assignments, follow our native CH controller set-up for Windows 11 instead. Installing Control Manager solely for calibration usually creates more problems than it solves.

How do I install CH Control Manager on Windows 10 or 11?

A clean installation is essential because installing over an older Control Manager driver can leave duplicate or unusable virtual devices.

1. Back up your maps. Copy any saved Control Manager profiles or scripts to a separate folder before removing an existing installation.
2. Remove the previous version. Uninstall Control Manager through Windows Installed apps or Programs and Features, then restart the computer. Do not install a new copy directly over an old one.
3. Disconnect the CH controllers. Unplug the yoke, pedals, throttle and joystick before starting the installer.
4. Run the genuine installer as administrator. Use a manufacturer-supplied installation package rather than a repackaged driver archive. Extract it first if it is compressed, then use the installer’s Run as administrator option.
5. Restart Windows. Reboot after installation even if the installer does not insist on it. This allows the controller and virtual-device drivers to initialise properly.
6. Reconnect one device at a time. Use direct motherboard USB ports during the initial set-up and allow Windows to finish recognising each controller before connecting the next one.
7. Test the physical controls. Run joy.cpl and confirm that every axis, hat and button responds. Our guide to checking joystick inputs with joy.cpl explains how to separate a Windows or hardware fault from a simulator problem.
8. Open Control Manager in Direct Mode first. Verify that it can see all the physical devices before creating or loading a map.

Compatibility mode can sometimes help an old installer open, but it cannot make a blocked kernel driver compatible with Windows 11. If Windows Security reports the CH driver as incompatible, repeatedly reinstalling it will not correct that problem.

How do I create and load a CH Control Manager map?

Mapped Mode should be configured before the simulator starts so that the simulator detects the intended virtual controllers.

1. Confirm the device list. Check that Control Manager identifies every connected CH controller correctly. Resolve missing devices before editing a map.
2. Create or open a map. Start with a blank map unless you have a profile made for the same collection of CH hardware.
3. Assign axes and buttons. Map each physical control to the required DirectX axis, button or keyboard command. Combine devices only where the simulator or profile genuinely benefits from it.
4. Calibrate the mapped output. Use Control Manager’s calibration facilities for a mapped profile. Avoid repeatedly calibrating the same axis in Control Manager, Windows and the simulator because each layer can distort the previous one.
5. Download or activate the map. Switch from Direct Mode to Mapped Mode using the application’s map activation command. The precise label can differ between Control Manager releases.
6. Open the simulator afterwards. Bind the axes and buttons belonging to the virtual Control Manager device. Clear automatic assignments from any physical CH devices that the simulator also displays.
7. Save the working map. Keep a backup outside the application’s installation directory so that an uninstall or repair does not remove it.

Load the map before every simulator session if it does not remain active after restarting Windows. Some simulators enumerate controllers only during launch, so changing between Direct and Mapped Mode while the simulator is running may require a restart.

Why does Control Manager not detect my CH controller?

If Windows detects the controller but Control Manager does not, the fault is usually the legacy driver, an incomplete previous installation or a USB enumeration problem.

• Nothing appears in joy.cpl: try another direct USB port, remove unneeded hubs and check the cable. Control Manager cannot repair a device that Windows itself cannot detect.
• Windows sees the device but Control Manager does not: uninstall Control Manager, restart, reinstall with the controllers disconnected and reconnect them one at a time.
• The virtual controller is missing: make sure the map was activated and Mapped Mode was selected before launching the simulator.
• The device stopped working after changing USB ports: return it to its original port, activate the map again and restart the simulator. Windows can treat the new connection as a different controller instance.
• An axis jumps or will not reach full travel: test it in Direct Mode. If the problem exists there, recalibrate once and inspect the hardware; if it appears only in Mapped Mode, check the map’s axis assignment and range.

Should I turn off Windows Memory integrity?

We do not recommend disabling Memory integrity merely to keep legacy controller software working. If Windows Security identifies the Control Manager driver as incompatible, uninstall Control Manager, restart Windows and let the CH hardware use the standard HID driver instead. Direct simulator assignments are the safer long-term choice.

Why do the controls move twice or fight each other?

Duplicate movement means the simulator is reading both the physical CH device and Control Manager’s virtual output, or the same axis has been assigned to two controllers. Keep only the virtual assignments in Mapped Mode, or return to native input and remove the virtual profile.

FSX is particularly prone to automatic duplicate assignments after a controller is reconnected. If the conflict appears there, work through our FSX controller detection and duplicate-axis checks.

Which mode should I use in a flight simulator?

Use native Windows input or Direct Mode for modern simulators; choose Mapped Mode only when you need its virtual-controller or programming features.

Microsoft Flight Simulator, X-Plane, Prepar3D and DCS can bind separate CH controllers directly. FSX, FS2004 and other older software can also use them separately, although a legacy profile or a simulator with limited controller handling may justify Mapped Mode.

Once a configuration works, keep each CH device in the same USB port and avoid switching modes while the simulator is open. That prevents changed controller IDs, lost profiles and unwanted automatic bindings.