Jump to content


Photo

[FIX] CH Products Control Manager after Windows 10 Creator Update


  • Please log in to reply
16 replies to this topic

#1 Somnus

Somnus

    Advanced Member

  • Members
  • PipPipPip
  • 391 posts

Posted 09 December 2017 - 04:16 PM

Alright, I think I might have found a solution to the problem that some of us are having with CH Products Control Manager after the Windows 10 update. The issue that I myself was having was that after downloading a profile to the stick, the buttons that allowed me to switch between direct mode, mapped mode and off mode would grey out, and the stick would become unresponsive. Sometimes this was resolved after numerous reboots, but then only until the next profile download.

 

Using the instructions found here I've been able to successfully switch profiles a number of times without encountering the problem. Here's the steps:

 

You need to prevent your computer from saving information to boot faster upon shutdown (you need to turn off fast startup in windows) so that it treats the controllers the same whether you cold boot or restart.

 

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 "Change settings that are currently unavailable". Lastly UNcheck "Turn on fast startup (recommended)"

 

2. Now when you boot from cold boot or a restart it will treat the controller the same way. 

 

3. Boot/reboot the computer. When it comes up DO NOT DO anything related to games or control manager loading scripts. You must open Control Center, or Control manager and wait for about 2-3 minutes until you hear the last chirp of the USB being recognized. Once that last chirp happens you can then load scripts or change whatever. If you do not wait for the last chirp (2-3 minutes) and you try to manage your controllers then you must reboot and start over.

 

4. Instead of manually opening control center upon startup. You can add the CMStart.exe (CH startup program for the 5 sec delay) shortcut to your SHELL:STARTUP folder.

 

 

 

 

Here's to hoping it holds!

 

S!



#2 Klaiber

Klaiber

    Advanced Member

  • Administrators
  • 10,918 posts

Posted 09 December 2017 - 07:18 PM

Hey Somnus, 

 

I moved this thread to the public Technical Support area.

 

Here's a list of things I've done in the past to try and fix this CH Control Manager / Windows 10 issue:

 

1. Power Management adjustment for USB devices:

 

I first tried to fix this by going to the Device Manager, and then to Universal Serial Bus controllers, and then right clicking on all the USB devices listed, going to properties, and then clicking on Power Management (if there).  I unclicked "Allow the computer to turn off this device to save power" for each USB device.  This prevents the USB devices (like the CH sticks) from going to sleep.  This has helped somewhat, and may be the reason my controls will pop back on sometimes.  I still do this, and recommend that others do as well.

 

2. Minimize TeamSpeak conflicts by removing hotkey support from TS:

 

Second, I found out that the new versions of TeamSpeak doesn't play well with CH stuff (or a lot of controllers in general).  After reading the TS forums, it seems like some conflict problems can stem from the "Gamepad and Joystick Support Plugin" (added to TS 3.1.1).  I don't need hotkey support from TS.  So I went to Tools > Options> Addons, and uninstalled it.  This has helped too.  I've been operating without that plugin for months with no problems.

 

3. Troubleshoot the program in Win10, and run as if in Windows Vista (Service Pack 2):

 

Thirdly, after flying last night, and having the issues start up again, I right-clicked on the exe for the CH Control Manager, clicked Troubleshoot capability, clicked Troubleshoot program, making sure that I selected "The program worked in early versions of Windows but won't install or run now", and then selected Windows Vista (Service Pack 2), which was the last time the CH manager 100% worked for me.  Saving those settings, I'm hoping this helps.

 

If it starts happening again, I'll give your above suggestion a shot. :)

 

I kind of feel like we're shooting in the dark here.  But I'm hoping that one fix, or a combination of them, will solve this bug once and for all.

 

. . . 

 

 

Additional steps to take, from newer posts:

 

  1. Minimize conflicts in Steam
  2. Force the CH Control Manager to always run in administrator mode
  3. Let Windows settle after a start-up / reboot to avoid conflicts

Klaiber_tiny_R.png?dl=0
Klaiber_tiny_O.png?dl=0
Klaiber_tiny_FS.png?dl=0

Hals - und Beinbruch!


#3 Klaiber

Klaiber

    Advanced Member

  • Administrators
  • 10,918 posts

Posted 09 December 2017 - 07:25 PM

Also, I almost forgot -

 

I've also gone into Steam, and tried to minimize conflicts there.

 

Go to Steam (in the upper left) > Settings > Controller > General Controller Settings.  And uncheck the "Guide Button Focuses Steam" checkbox.

 

As with the TeamSpeak "fix", all this is doing is minimizing potential conflicts.  It's probably not going to solve it, but it won't hurt either.


Klaiber_tiny_R.png?dl=0
Klaiber_tiny_O.png?dl=0
Klaiber_tiny_FS.png?dl=0

Hals - und Beinbruch!


#4 Luftritter

Luftritter

    Advanced Member

  • Members
  • PipPipPip
  • 1,850 posts
  • LocationMichigan, United States

Posted 09 December 2017 - 09:21 PM

First, I'm wondering if you guys use "CMStart" in your startup folder.

 

Next, do you minimize Teamspeak before you enter the game?  TS seems to commandeer certain keyboard keys when it's open.

 

Just wondering what the issues are, as for me, I don't experience any issues related to RoF, and never have; but it's the only sim or game I play right now.

 

S!


"People who believe they are ignorant of nothing have neither looked for, nor stumbled upon, the boundary between what is known and unknown in the universe." -Neil deGrasse Tyson

#5 Klaiber

Klaiber

    Advanced Member

  • Administrators
  • 10,918 posts

Posted 10 December 2017 - 01:54 AM

Mostly the issues are that after loading a profile, the buttons intermittently grey out and stop working.  And when that happens, none of the programmed switches on your HOTAS work properly.  The only way to fix it when it breaks is to reboot the computer, and hope it doesn't happen again.  Both Somnus and I got stuck in that loop last night.

 

Unfortunately, there hasn't been any movement from CH on this issue.  Some people are cursed with this problem.  Others haven't had any issues.  So it seems like it has to do with conflicts.  But which ones is anyone's guess.

 

I'm not aware of CMStart.  What is it?

 

I sometimes minimize TS.  I guess it depends on what we're doing.


Klaiber_tiny_R.png?dl=0
Klaiber_tiny_O.png?dl=0
Klaiber_tiny_FS.png?dl=0

Hals - und Beinbruch!


#6 Somnus

Somnus

    Advanced Member

  • Members
  • PipPipPip
  • 391 posts

Posted 10 December 2017 - 01:56 AM

Yeah, so the fix I posted in the OP didn't work. I'm not sure what CMStart is either, so I guess maybe I don't use it? Also, this happens even without TS loaded up.



#7 Klaiber

Klaiber

    Advanced Member

  • Administrators
  • 10,918 posts

Posted 10 December 2017 - 01:58 AM

Hey Somnus, give my posted suggestions a shot.  It may not help, but I'm hoping that it will minimize some of your issues.


Klaiber_tiny_R.png?dl=0
Klaiber_tiny_O.png?dl=0
Klaiber_tiny_FS.png?dl=0

Hals - und Beinbruch!


#8 Luftritter

Luftritter

    Advanced Member

  • Members
  • PipPipPip
  • 1,850 posts
  • LocationMichigan, United States

Posted 10 December 2017 - 03:06 AM

CMStart is an executable that you put into your "startup" folder (or the equivalent action that now automatically runs certain programs at WIndows start up).

 

Here is what it does:

 

CMStart


"People who believe they are ignorant of nothing have neither looked for, nor stumbled upon, the boundary between what is known and unknown in the universe." -Neil deGrasse Tyson

#9 Klaiber

Klaiber

    Advanced Member

  • Administrators
  • 10,918 posts

Posted 09 January 2018 - 07:02 PM

Hi All,

Here is a report from CH Hanger regarding the CH issues that a lot of us have been having:
 
http://www.ch-hangar...-another-forum/
 

I have been made aware of a post on the IL-2 forums here titled 'Users Of CH Products Gear With Control Manager Software - BE ADVISED! where a member has made a number of statements after apparently talking to someone within CH Products tech support team. Unfortunately I cannot address those points directly as I am still banned from that forum for telling another user that his use of a smiley was "silly" - apparently this was "aggressive" of me. However the points stated were:

  • Bob Church, the developer of the software, has retired.
  • CH is aware that the software, the last version of which was updated in 2011, no longer functions under Windows 10.
  • CH has not reached out to Microsoft for assistance in resolving the problem with the software, hence Microsoft will never know that they broke it. John, on the other hand, seemed to think it possible that Microsoft could release another set of patches to Windows 10 that just might happen to fix the problem, as randomly as it was broken. As a 40+ year Microsoft developer myself, I told John that it is up to CH to contact Microsoft and work with them to resolve the issue; it is not possible for Microsoft to fix a problem with the operating system that they are unaware of, and delusional to expect them to do so.
  • CH has not mounted a search for a developer to pick up the maintenance of the Control Manager Software.
On the first point Bob as far as I am aware is enjoying his much deserved retirement, I've not spoken to Bob for some time. That said on the second point there are many users who are using the CH Control Manager software in Windows 10 without any apparent issues however CH is aware of some users experiencing issues. On point three CH has reached out in the past to Microsoft and still continue to do so, you may remember the issues many hardware manufacturers had with Windows Vista and how CH was one of the first of the joystick hardware manufacturers to get their software working in Vista. CH has not abandoned support for the Control Manager software and are indeed currently looking into solutions to help those experiencing problems but unfortunately do not have a timetable for this work to be completed. The response above is from a direct conversation with Debby at CH where I relayed the frustrations some users are having. I know its probably not the complete answer you wanted but I will try to keep the members of this forum updated as and when I have any news to share.

 


  • Butzzell likes this

Klaiber_tiny_R.png?dl=0
Klaiber_tiny_O.png?dl=0
Klaiber_tiny_FS.png?dl=0

Hals - und Beinbruch!


#10 Lee

Lee

    Advanced Member

  • Members
  • PipPipPip
  • 427 posts
  • LocationVirginia Beach USA

Posted 27 January 2018 - 06:01 AM

Just had this big Windows 10 update run on my flight sim computer.  I use CH Control Manager to program my controllers and the update caused the joystick devices numbers to get shuffled.  I had to reassign the all axis in the RoF settings.  Most of my buttons are programmed to give keystrokes so weren't affected.  Had this happen a couple of years ago after another windows update.



#11 Klaiber

Klaiber

    Advanced Member

  • Administrators
  • 10,918 posts

Posted 27 January 2018 - 06:16 AM

Ouch... Now I'm scared to update.

Klaiber_tiny_R.png?dl=0
Klaiber_tiny_O.png?dl=0
Klaiber_tiny_FS.png?dl=0

Hals - und Beinbruch!


#12 Lee

Lee

    Advanced Member

  • Members
  • PipPipPip
  • 427 posts
  • LocationVirginia Beach USA

Posted 11 February 2018 - 06:53 PM

Another Windows 10 update and another joystick device number shuffel.  Axis again had to be reassigned in settings.



#13 Luftritter

Luftritter

    Advanced Member

  • Members
  • PipPipPip
  • 1,850 posts
  • LocationMichigan, United States

Posted 11 February 2018 - 07:52 PM

Another Windows 10 update and another joystick device number shuffel.  Axis again had to be reassigned in settings.

 

Yes, I have grown used to this.  Although you can get the main axis back in business pretty quickly, for somebody like me, there are a myriad of buttons that need to be re-mapped.

 

BH_Dudley has touted a program that keeps controller ID's the same, but I've never been able to get the actual program online.  It's like it has been commandeered to lead to spam-ware, so it seems impossible for us to get now, unless we can somehow get it directly from Dudley, if he has the original installer or .zip file.  He may not.

 

With this in mind, I've made up my mind to create 3 different controls maps that work with 3 different ID's for my joystick.  The ID's seem to rotate, so I think it could work.  I'll name the controls maps to correspond with whatever the main joystick ID is; theoretically the other two I have should fall in line.

 

We'll see.  Save whatever you're using right now with a name that you know corresponds to your current joystick ID.  Later, if you get screwed again, save your corrections as the next ID for your joystick.

 

Theoretically, eventually you should come back around to your original ID scheme.  At that point, you should be able to import that scheme back in, or one of the others, without having to re-do everything again.

 

Since this problem apparently doesn't exist in BoX series, it should be a thing of the past when FC comes out.


"People who believe they are ignorant of nothing have neither looked for, nor stumbled upon, the boundary between what is known and unknown in the universe." -Neil deGrasse Tyson

#14 Lee

Lee

    Advanced Member

  • Members
  • PipPipPip
  • 427 posts
  • LocationVirginia Beach USA

Posted 11 February 2018 - 10:29 PM

Fortunately, I only have to reassign the main joystick axes. I use the CH ControlManager to assign keyboard commands to all my buttons so it doesn’t matter what the controller device number is, text is text and the buttons function as expected.

#15 Klaiber

Klaiber

    Advanced Member

  • Administrators
  • 10,918 posts

Posted 26 June 2018 - 04:42 PM

Hi Guys,

 

I have another step people can try:

 

This is in addition to the four others I posted above:

 

http://forum.jg1.org...ate/#entry34105

 

http://forum.jg1.org...ate/#entry34106

 

Make the CH Control Manager always run in administrator mode.

 

  1. Right click on the CH Control Manager.
  2. Select Properties
  3. Click Advanced within the Shortcut tab.
  4. Tick the run as administrator box and click okay.
  5. Click okay on the main properties window and click Continue.
  6. Reboot the computer.  
  7. The CH Control Manager should now have a shield next to it.
  8. It will now prompt you regarding administrator mode every time you click it.

Klaiber_tiny_R.png?dl=0
Klaiber_tiny_O.png?dl=0
Klaiber_tiny_FS.png?dl=0

Hals - und Beinbruch!


#16 Klaiber

Klaiber

    Advanced Member

  • Administrators
  • 10,918 posts

Posted 26 June 2018 - 04:50 PM

Finally, a seventh possible fix.  It's a simple one, but works for me.

 

When you turn your computer on from a cold start or even a reboot, let it sit for a minute or two.

 

In a cold start or reboot, a bunch of background programs are coming online and starting up.  Your computer is finding it's peripherals and checking for changes.  Starting up the unsupported CH Control Manger during this process could cause a conflict, resulting in the manager graying out and no longer working.

 

Generally, I let the computer sit until I hear an auditory beep from Windows, indicating that the computer has found my HOTAS and that things are stabilized.

 

This might be different for everyone's computer.  Perhaps only mine does this.  But it's something to note.  Every time I've rushed to use the CH Control Manager after a cold start or reboot, it doesn't work.


Klaiber_tiny_R.png?dl=0
Klaiber_tiny_O.png?dl=0
Klaiber_tiny_FS.png?dl=0

Hals - und Beinbruch!


#17 Luftritter

Luftritter

    Advanced Member

  • Members
  • PipPipPip
  • 1,850 posts
  • LocationMichigan, United States

Posted 26 June 2018 - 09:17 PM

Many thanks. Now that I'm experiencing the exact issue you posted above, this will be very helpful.

My suspicion is that the compatibility mode is the big one. I never had trouble in Win7. However if you know the Vista mode works, who cares which one it's using, if they're any different at all.

Honestly we should be happy we even have this option. Remember life before it? Sometimes you just had to write off a program, or even a piece of hardware!
  • Klaiber likes this
"People who believe they are ignorant of nothing have neither looked for, nor stumbled upon, the boundary between what is known and unknown in the universe." -Neil deGrasse Tyson




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users