Jump to content

Boight

Members
  • Posts

    12
  • Joined

Reputation

10 Good

Converted

  • Occupation
    Retirement Trainee
  1. Metazolid's post #24 fixed it for me. Thanks Bud! :cool: Well.. it came back after I changed Account control to wide open. (off) So.. now I've changed syswow's hsmanager to win 8 compatibility and admin mode and Icue to win 8 compatibility and admin mode. Both accessed from taskmanager startup. I haven't had to change my Xonar driver though. So far.... so good.
  2. Found this issue with some searching. Exactly my problem after a complete format and install of my win10 system. Nothing in these forums was helping. My Fix: 1: uninstall and delete ALL CUE/ICUE files in c: I use an app called EVERYTHING to find Corsair stuff. Save your .profile profiles though. 1a: Restart 2: Install an old CUE version i.e. Corsair-Utility-Engine-v1.16.42.zip It's pretty old but does install for my Strafe. 3: Update to ICUE eg. CorsairUtilityEngineSetup_3.1.131_release.msi and make sure that works. 4: Let iCue update itself to latest version. So far so good!! YEAH!
  3. I've tried everything (solution) in this thread except taking it apart and filing the pads or replacing the switch. Very disappointed Corsair!:[pouts: Mine is out of warranty so nothing ventured nothing gained. I see a number of articles on how to disassemble. It picks my butt that I have to do this when I have 10+ year old mice with no click issues.
  4. Did a inplace update to 1903, that didn't help. :confused:
  5. This is the second time I've had this error. I'm using 1803 still. I was lucky enough to get into safemode and use a restore point. Last time I had to load a backup image. There's a problem here and someone needs to pay attention.
×
×
  • Create New...