Corsair Katar Pro XT (Wired) Mouse - POSSIBLE ISSUE WITH NEW 1.6.26 FIRMWARE

[wiggly1uk2000]

Corsair Katar Pro XT (Wired) Mouse - POSSIBLE ISSUE WITH NEW 1.6.26 FIRMWARE

I just upgraded the firmware of my Corsair Katar Pro XT wired mouse (P/N: CH-930C111) via iCUE (v.4.30.162) to version 1.6.26. Since the upgrade the mouse cursor has become erratic and will randomly jump to another place on the screen with even the slightest movement of the mouse. The mouse was perfectly fine before the firmware update. It's in excellent condition and has no hardware issues (such as intermittent USB connection, dirty sensor, etc.). I am confident this is a firmware issue. I have tried the following troubleshooting steps already:

• A factory reset of the mouse
• Redoing the surface calibration in iCUE (I use a Corsair MM700 mouse mat which is a black cloth type)
• Cleaning the sensor thoroughly with a fine brush (though it was already spotless)
• Ensured that 'Button Response Optimization' is disabled (not that I see how that could be a factor)

At this point the next step would seem to be reverting to the previous firmware version. Can anybody confirm the number of the firmware version prior to 1.6.26 (which worked perfectly for me)? Also, how do I get my hands on this older firmware file?

Any and all help much appreciated. The mouse suits me perfectly (apart from a slightly squeaky scroll wheel!) and I'm kicking myself for upgrading the firmware on a whim when the mouse was working just fine. 

Edited November 29, 2022 by wiggly1uk2000

[Noz91]

I confirm, I have the same issue as you !!! Can somebody give us the firmware file to rollback or possibly fix this?

FYI: I tried to contact Corsair support by email but no reply yet 😞

P/N : CH-930C111

iCue version: v.4.30.162

The mouse is jumping to another place on the screen randomly.

 

Edited December 1, 2022 by Noz91

[wiggly1uk2000]

Okay, so that seems to confirm that it's definitely a firmware issue. We just need Corsair to act. I have not yet heard anything from customer support either. I will update this thread with any new information.

I did also notice that the Button Response Optimization function has the switch toggle reversed so you have to turn it on to deactivate it! I don't know if that bug also relates to this new firmware version but it's important to mention because for some people (myself included) having Button Response Optimization active can cause the mouse to incorrectly detect button clicks from just the slightest knock to the mouse casing. This issue has been reported online for other Corsair mouse models too. It would seem that debounce time is affected to the point that the mouse detects non-existent button clicks! 

Please could somebody from Corsair respond to these issues and supply a fix?

 

Edited December 1, 2022 by wiggly1uk2000

[Zerofiuza]

I just bought one and when I plugged it in, the firmware update popped up, so I installed.

I hope it's a firmware issue, cause I didn't even test it before updating.

I was thinking it was a hardware defect.

I just hope Corsair sees into this problem ASAP.

[wiggly1uk2000]

 

14 hours ago, Zerofiuza said:

I just bought one and when I plugged it in, the firmware update popped up, so I installed.

I hope it's a firmware issue, cause I didn't even test it before updating.

I was thinking it was a hardware defect.

I just hope Corsair sees into this problem ASAP.

If you haven't done so already I would encourage you to contact Corsair directly by submitting a ticket using the Contact Us option on the support pages of the Corsair website. Perhaps if enough people raise this issue we'll stand a better chance of receiving a response.

[asrgreenscene]

I also have this problem! I received my mouse on November 26 and updated the firmware immediately without testing it on the firmware it shipped with. I've tried using the mouse with and without iCUE running, updating my motherboard's BIOS, calibrating the surface, and even swapping out mousepads. I'm glad I'm not the only one with this problem because, I really like the mouse and I was hoping it wasn't a hardware problem...

The mouse will randomly jump about 200px in any direction when the mouse is in motion. The problem occurs in any application including just the desktop. When gaming it happens about once every 10 minutes. Sometimes it won't happen for as long as an hour and sometimes it will happen multiple times in a 5 minute window.

[wiggly1uk2000]

8 hours ago, asrgreenscene said:

I also have this problem! I received my mouse on November 26 and updated the firmware immediately without testing it on the firmware it shipped with. I've tried using the mouse with and without iCUE running, updating my motherboard's BIOS, calibrating the surface, and even swapping out mousepads. I'm glad I'm not the only one with this problem because, I really like the mouse and I was hoping it wasn't a hardware problem...

The mouse will randomly jump about 200px in any direction when the mouse is in motion. The problem occurs in any application including just the desktop. When gaming it happens about once every 10 minutes. Sometimes it won't happen for as long as an hour and sometimes it will happen multiple times in a 5 minute window.

Yes, those are the exact symptoms. I'm still using the mouse daily (since it's all I have) but it's a real pain to live with! Prior to the 1.6.26 firmware update I can confirm that the mouse was perfectly fine so you can almost certainly be sure it's not a hardware issue. Unfortunately there's nothing any of us can do until Corsair provides a fix or the means to downgrade the firmware to the previous version.

The lack of any official response so far is disappointing. I wish Corsair would provide a complete archive of all device firmware (past and present) along with release notes. Having to contact them directly to get a .BIN file to fix issues like this is both frustrating and long-winded. Also, a bug like this should never make it into the public domain because it's essentially rendered the device unusable for any tasks that require consistency and accuracy.

[valier]

hopping on this hoping that corsair will see it, iam having the same problem, just got the mouse yesterday, did the update and i noticed the issue immediately . contacted support and no response until now, its almost been 24 hours so cant complain just yet. hopefully it is fixed soon.

[wiggly1uk2000]

5 minutes ago, valier said:

hopping on this hoping that corsair will see it, iam having the same problem, just got the mouse yesterday, did the update and i noticed the issue immediately . contacted support and no response until now, its almost been 24 hours so cant complain just yet. hopefully it is fixed soon.

Thanks for contributing. I've been waiting almost a week and still no response from Corsair. It's as if the whole of tech support is on an extended break!

[Technobeard]

1 hour ago, wiggly1uk2000 said:

Thanks for contributing. I've been waiting almost a week and still no response from Corsair. It's as if the whole of tech support is on an extended break!

It’s the complete opposite of that. Ticket volume goes sky high this time of year for any type of support platform.

[wiggly1uk2000]

5 minutes ago, Technobeard said:

It’s the complete opposite of that. Ticket volume goes sky high this time of year for any type of support platform.

This is a good example of an issue that will only get much bigger (and create more support tickets) if not dealt with quickly. Corsair removing the firmware in question from iCUE would be a prudent first step.

[wiggly1uk2000]

I have another (faulty) Katar Pro XT mouse sitting here which belongs to my partner. I just hooked it up to iCUE and it's being offered the 1.6.26 firmware update. It would seem to indicate that the broken 1.6.26 firmware is still being offered to everyone. I see no progress of any kind and not even an acknowledgment from Corsair that the problem exists.

[Noz91]

Corsair finally answered me but no ETA given, in the meantime I ordered the wireless version of the mouse on black friday due to the situation. I understand things take time to fix but they should stop offering 1.6.26....

Quote

I do apologize for the delay, we are currently looking into the firmware issue, once a solution is given I will update you in this ticket, unfortunately we do not have a time frame of when it will be available

Best Regards,

Glenn H.

Thank you for choosing Corsair.

 

[wiggly1uk2000]

12 hours ago, Noz91 said:

Corsair finally answered me but no ETA given, in the meantime I ordered the wireless version of the mouse on black friday due to the situation. I understand things take time to fix but they should stop offering 1.6.26....

 

I'm pleased to hear that Corsair are aware of the issue and working on a fix. What would help enormously would be the .BIN firmware file for the previous firmware version so that those of us with no other equivalent mouse to use can at least get up and running again while we wait for the fix. I don't feel inclined to buy another mouse when Corsair could so easily supply the necessary (older) firmware to make my Katar Pro XT work perfectly again!

[wiggly1uk2000]

I've found a workaround to this issue which I am happy to share here in case it's helpful to others...

I had access to an old (faulty) Katar Pro XT mouse with older firmware installed (1.2.20). By attaching the faulty mouse to my PC with the recessed button underneath depressed at the same time, it was recognised by the PC as a storage device containing a firmware.bin file. I copied that file to my PC and then disconnected the mouse. I then attached my main Katar Pro XT to the PC in exactly the same way (holding down the recessed button underneath). Next I replaced the firmware.bin file on this mouse with the older one extracted from the faulty mouse. Finally I disconnected and reconnected the mouse whist holding down both mouse buttons (to perform a factory reset). The mouse booted normally and now has the 1.2.20 firmware installed. It's very old firmware and probably lacks some refinements and features introduced in later versions, but at least it doesn't have the awful bug that's present in 1.6.26.

Now I have a usable mouse until a proper fix is released.

Three important things worth mentioning here:

• The method described above has revealed the fact that it's possible to back up existing firmware before upgrading to a new version. I will remember this in future as it's a lot easier and quicker then relying on customer support for assistance.
• This demonstrates how easy it is to downgrade the firmware of this model, as long as you have access to the necessary firmware.bin file.
• As with any firmware upgrade, there is always the potential for things to go wrong and leave you with a completely non-functioning mouse. For that reason I'm not advocating use of this procedure without careful consideration of the risks!

Whilst I would be happy to share the extracted 1.2.20 firmware with other users I expect it goes against forum rules and probably isn't permitted by Corsair either.

 

[Epicmonkie]

I would love a copy of that firmware, if you would DM me a link to it.

[wiggly1uk2000]

24 minutes ago, Epicmonkie said:

I would love a copy of that firmware, if you would DM me a link to it.

I'm very wary of offering this firmware to multiple users in case it causes more problems than it fixes! If you're having the same problem that I was having with the Katar Pro XT (caused by firmware 1.6.26) then it might be best to hang on for an official fix from Corsair. I had a message from Corsair customer support a little while ago confirming that they are definitely working on a fix so hopefully it won't be too long.

If any moderators or Corsair reps would like to chip in with the official rules on sharing firmware on this forum then that would be most helpful. I'd be happy to provide a link to the old 1.2.20 firmware in this thread but only if it's within the rules. If it's totally fine then I have to wonder why Corsair aren't doing it themselves!

[Corsair Raven]

Hello there, our teams are aware of this issue. If you are encountering this issue, please contact our support team by opening a ticket at https://help.corsair.com/hc/en-us/requests/new  Then you can either provide me with the ticket number here or you can PM it to me.

[wiggly1uk2000]

10 hours ago, Corsair Raven said:

Hello there, our teams are aware of this issue. If you are encountering this issue, please contact our support team by opening a ticket at https://help.corsair.com/hc/en-us/requests/new  Then you can either provide me with the ticket number here or you can PM it to me.

Message sent. Looking forward to a resolution for everyone affected.

[R314XXX]

I found a way to install an old firmware version!
all we need is to install the corsair legasy version from the official website. then forced to flash it in the old version (for some reason, the latest version is 1.5.24 there)

[wiggly1uk2000]

16 minutes ago, R314XXX said:

I found a way to install an old firmware version!
all we need is to install the corsair legasy version from the official website. then forced to flash it in the old version (for some reason, the latest version is 1.5.24 there)

That's very useful info. Thanks for sharing it. I'm pretty sure 1.5.24 was the previous version before 1.6.26 was released so it's an ideal solution for getting my mouse back to exactly where it was before everything went horribly wrong. Thanks again! 

[valier]

corsair support contacted me , they mentioned that a new version will be released  for the mouse in the  next 2 days if god wills. 

[wiggly1uk2000]

Corsair sent me a new firmware file via technical support to try with my Katar Pro XT. Has anyone else received this file and tried it? The firmware.bin file that was provided by Corsair is around twice the size of normal Katar Pro XT firmware files (516KB instead of 256KB) which strikes me as a little odd. 

While I wait for Corsair to respond to my concerns, I would love to know if anyone else has received the same 516KB firmware.bin file. If so, have you tried it with your Katar Pro XT? With my mouse happily running the older 1.5.24 firmware again, I don't want to risk messing it up!

Edited December 9, 2022 by wiggly1uk2000

[wiggly1uk2000]

UPDATE: I can now confirm that the new 516KB firmware file sent to me from Corsair is NOT suitable for the Katar Pro XT and must have been sent in error. There's not even enough storage space on the mouse to contain a firmware file that big so you couldn't try it if you wanted to!

Please Corsair, get this sorted! 🙄

[커세어엿먹어라]

Damn it, I'm very sympathetic to this subject. This stupid company is not doing anything about this error. I already ordered a mouse from another company. You guys missed a lot of customers. These stupid companies. Imagine that the arrow moves randomly in the game, and it happens in an important situation. I feel like I want to break a mouse.