CH Manager and Windows 10 problem
-
I recently upgraded to Windows 10 about a month ago. Recently I started noticing issues with my CH products (Fighterstick, Throttle, Pedals) and I’ve narrowed it down to something with CH Control Manager.
When I boot my PC, Windows sees the controllers no problem. I can open CH Control Manager, open my BMS map, and everything at this point still works fine. I can push buttons, move the controllers, and CH Manager will change to that controller and button or axis.
My issue starts when I download my map to my controllers. Once the map is downloaded Windows doesn’t see the controllers (Device Manager, Game Controllers, in BMS, etc.) anymore and CH Manager will quit responding to inputs. Also, the toggle buttons in the CH Control Manager for “Off Mode”, “Direct Mode”, and “Mapped Mode” are all grayed out and the CH Control Manager software is unresponsive.
I’ve done some searches and have tried changing power settings for Windows, and turned off power management for the CH Products in the Device Manager. I have uninstalled, and reinstalled the CH Software and that worked….until I rebooted my PC and had the same issue all over again.
In the interim, I’ve directly mapped my controls to BMS. This is okay for me, the problem is I can only use one of the hat switches being that BMS only recognizes one of them. I used to use the hat on the Throttle for comms and IFF (datalink) and as I write this I don’t know of a way to config this being that I used CH Manager to make the throttle POV a hat switch in CH Manager. I also used the CH software to set curves for the little thumb joystick on the throttle that I use for TDC as well.
Granted I’ve got a partial work around, but I’d like to be able to use my CH Manager software like I typically did. It worked flawlessly for me on Windows 8.x and seemed to be working fine on Windows 10 until recently. Perhaps the latest update.
Long post, but I was wondering if anyone experienced this and had found a viable solution that “works 60% of the time every time”.
-Howler
-
Hi Dubten, I don’t have Windows 10 but I have encountered the problem of greyed-out modes in CH Control Manager. It actually turned out to be a conflict with Track IR. In order to get the modes back I had to shut down Track IR and then check Windows Task Manager to make absolutely sure it was shut down. Then I could select mode and restart Track IR proceeding normally.
Probably not your problem but might be somewhere to start.
-
I have the same issue with CH Control Manager. From what I gather from other posts about this issue Windows broke control manager with one of its updates and the only answer that the folks from CH could give is that maybe Windows with luck will fixit with an update (Not much of an answer). The guy who wrote CH control manager is retired. There doesn’t seem to be a lot of tech support out of CH these days. What worked for me is to load a profile into the joystick with CH manager. When I do this the Joysticks in the USB control panel disappear most of the time (even with all the USB power settings set to on). To get the system to work I reboot the computer. Then I run CMstart. And the CH devices then appear in the USB control panel and your good to go.
Good luck
WW -
Hi all,
I`m facing all these problems stated here, tried all the fixes I could find but when you restart, the problem will be back… Such a nice hardware blown out by software problems… sad.
-
_Let’s see if this is the right solution to this problem since the latest updates from the creators of Windows 10.
First, you need to prevent your computer from saving the information to boot faster after shutting down (you need to turn off quick boot in Windows) so that it treats drivers the same way, either by cold boot or by restarting.
1. Click the Start button and type “CONTROL PANEL”, then choose Hardware and Sound, then Power Options. On the left side, click “Choose what the power buttons do”. Now click on “Change settings that are currently unavailable”. Lastly, uncheck “Enable Quick Launch (Recommended)”
2. Now, when you boot from a cold boot or a reboot, it will treat the controller the same way.
3. Boot / reboot the computer. When it appears, DO NOT do anything related to games or load scripts from the control manager. You should open the Control Center or Control Manager and wait about 2-3 minutes before you hear the latest USB squeal being acknowledged. Once the last chirp happens, you can load scripts or change anything. If you do not wait for the last chirp (2-3 minutes) and try to manage your controllers, you must restart and start over.
4. Instead of manually opening the control center at startup. You can add the shortcut CMStart.exe (CH boot program for the 5 s delay) to your SHELL:
STARTUP folder.
- CMSTART *
To add CMStart to your SHELL folder: STARTUP
1. In the Windows Explorer address bar, type or paste \ Program Files (x86) \ CH Products
2. In the upper left Windows Explorer, choose FILE Open New Window. In the address bar of this window, type or paste SHELL: STARTUP
3. Once you have both windows up, right-click and drag the CMSTART application to the SHELL: STARTUP folder and release. When the options appear, select “create shortcuts here”.
4. Now every time you boot up, the controller will start the 2 minute wait process.
Check this one out !!-
Open Device Manager in Windows
-
Find the CH Product List and expand it
-
For each device listed:
A) Right-click and click properties in the device window.
B) Click the Power Management tab, if there is one. If not, just close the window and move to the next device.
C) Uncheck the box that says “Allow computer to turn off this device to save power”
I restarted your PC !!!
Let’s see if with these two alternatives works normal !!
This Windows 10 is tough !!_ - CMSTART *
-
_Let’s see if this is the right solution to this problem since the latest updates from the creators of Windows 10.
First, you need to prevent your computer from saving the information to boot faster after shutting down (you need to turn off quick boot in Windows) so that it treats drivers the same way, either by cold boot or by restarting.
1. Click the Start button and type “CONTROL PANEL”, then choose Hardware and Sound, then Power Options. On the left side, click “Choose what the power buttons do”. Now click on “Change settings that are currently unavailable”. Lastly, uncheck “Enable Quick Launch (Recommended)”
2. Now, when you boot from a cold boot or a reboot, it will treat the controller the same way.
3. Boot / reboot the computer. When it appears, DO NOT do anything related to games or load scripts from the control manager. You should open the Control Center or Control Manager and wait about 2-3 minutes before you hear the latest USB squeal being acknowledged. Once the last chirp happens, you can load scripts or change anything. If you do not wait for the last chirp (2-3 minutes) and try to manage your controllers, you must restart and start over.
4. Instead of manually opening the control center at startup. You can add the shortcut CMStart.exe (CH boot program for the 5 s delay) to your SHELL:
STARTUP folder.
- CMSTART *
To add CMStart to your SHELL folder: STARTUP
1. In the Windows Explorer address bar, type or paste \ Program Files (x86) \ CH Products
2. In the upper left Windows Explorer, choose FILE Open New Window. In the address bar of this window, type or paste SHELL:STARTUP
3. Once you have both windows up, right-click and drag the CMSTART application to the SHELL:STARTUP folder and release. When the options appear, select “create shortcuts here”.
4. Now every time you boot up, the controller will start the 2 minute wait process.
Check this one out !!-
Open Device Manager in Windows
-
Find the CH Product List and expand it
-
For each device listed:
A) Right-click and click properties in the device window.
B) Click the Power Management tab, if there is one. If not, just close the window and move to the next device.
C) Uncheck the box that says “Allow computer to turn off this device to save power”
I restarted your PC !!!
Let’s see if with these two alternatives works normal !!
This Windows 10 is tough !!_Thanks for the hints, I fixed your Shell:Startup line, can’t have a space in there… hope it works!
- CMSTART *
-
Have to say since I followed Malpaso’s instructions I have had 0 issues with Control Manager! :peace:
-
Have to say since I followed Malpaso’s instructions I have had 0 issues with Control Manager! :peace:
Hello Icer, how are you?
Now just enjoy, BMS !!
Good Sunday !
Good Flights !!
Take care !!
malpaso -
Hi,
I’m thinking about upgrading to Windows 10.
Is above solution working for all of you CH users or is there still some unsolved problem for certain setups ?Thanx
Sunnny -
Hello !
It worked for Icer!
Have to say since I followed Malpaso’s instructions I have had 0 issues with Control Manager! -
Hello !
It worked for Icer!
Have to say since I followed Malpaso’s instructions I have had 0 issues with Control Manager!Weeeell, it worked ok but every once in a while I got a BSOD and the culprit was always CHDriver01.sys (sp. close) so I decided to dump it. I use Win10 calibration and simple in-game programming for it now (Shifted hats/buttons with Alternative launcher Keymapping for BMS!). I also use VoiceAttack so I really am fine without complex Control Manager assignments, can’t remember what does what 1/2 the time anyway! Maybe someone will get Bob Church to release the source code for it and bring it back up to date!
-
I should add that when you replace the OEM CH Mainboards with MTWSims in the CH Fighterstick and Pro Throttle you must uninstall the CH Manager once and for all and use MMJoy2 to calibrate. If you just replace the potentiometers you can still (try to) use it…
-
Just in case anyone - like me - are still using their 20 year old CH Products HOTAS, I found this recent post stating that the Windows Store service has been the reason the Control Manager software would keep locking up. Basically, when the menu buttons gray out just kill or restart the Windows Store app.
More info here (see posts from October 2020 and newer): https://forum.jg1.org/topic/5375-fix-ch-products-control-manager-after-windows-10-creator-update/?do=findComment&comment=64223
-
I have a little batch file on my desktop that kills the store, starts CH, starts my various add-ins for BMS, voiceattack, then BMS.
Sent from my iPhone using Tapatalk
-
@dubten I have found if you shut down the Microsoft Store your CH Manager will work without any problems.
This is the only fix I could get CH Manager to work I tried all the other so-called fixes with out any success.
-
@semipro Interesting I wonder if this is why my CH Control Manager worked from the start without issue. With my windows install before any software installations I go into GPO and disable all unnecessary windows modules, windows store is one of them. I probably disabled close to 70 objects as well as disable about 20 services that I don’t and will not ever use. I would implore people to do the same if they do a new or even with a current installation. Windows runs way more efficient and faster that way and it eliminates a lot of conflicts and issues.
-
Since I have used the Alternative launcher, I never opened CH Manager again.
-
@WurminatorZA
Sorry for my ignorance, but what is GPO? -
@mj3437 Group Policy Objects
-
If you go into your task manager and shut down the Windows Store your CH Manager will work like in Win 7 of XP…! You will have to do this each time you start up Win 10