Scimitar side buttons not working

Well, bought the mouse this month. It was working fine on Windows 8.1.

I decided to upgrade to Windows 10 and now the side buttons don't work. If Corsair Utility Engine is reinstalled, the buttons do work again. But, after a reboot, it stops working.

Hello Everyone,

 

If you guys are having this issue, please post your logs so i can forward them to our validation team to assess.

It's a shame. Almost a year since this post was made and this still looks like a common problem. It appears I was wrong to think Corsair products were all reliable and if they had flaws they would be fixed quite fast. Looks like I need to find a different product one that will be debugged within a reasonable period of time instead of telling its users to send in logs for nothing to happen as a result. Will never be recommending another corsair product to my friends again in the future. I'm sure you don't care about the small number of users having this software issue but I'm done looking for fixes for it. :sigh!:

It's a shame. Almost a year since this post was made and this still looks like a common problem. It appears I was wrong to think Corsair products were all reliable and if they had flaws they would be fixed quite fast. Looks like I need to find a different product one that will be debugged within a reasonable period of time instead of telling its users to send in logs for nothing to happen as a result. Will never be recommending another corsair product to my friends again in the future. I'm sure you don't care about the small number of users having this software issue but I'm done looking for fixes for it. :sigh!:

I had this issue too but a newer CUE version fixed it. I guess there are still some rare instances though.

I had this issue too but a newer CUE version fixed it. I guess there are still some rare instances though.

Just 2 days ago or so I installed the new CUE 2.3. Now, im not sure about my issue. My scimitar seems to come out of sleep with the buttons working fine, but my CUE will crash (in the middle of w/e im doing) and need to be restarted. Sometimes now, I get an error saying the installation needs to be repaired and when this happens, my buttons do not work, even with a program restart.

Too early to tell, but im not sure if this has helped the problem or made it worse.

Greetings Scimitar users,

I've had this mouse now since February, all was fine until the Win10 rolled up.

Now I have occasionally my side buttons not working at all and the only way to re-enable them is a PC restart, which sucks in the middle of a Game.

I've tried almost everything, unpluging the mouse, dissableing/enabling the driver, relaunching CUE, nothing besides the restart works.

I've tried to go back on older firmware posted in this forum, I've tried so many things yet nothing's working for me.

I still get the occasionally annoying dis-function of my side buttons that only a whole PC restart can fix.

Do any of you have a similar issue ?

Greetings Scimitar users,

 

I've had this mouse now since February, all was fine until the Win10 rolled up.

Now I have occasionally my side buttons not working at all and the only way to re-enable them is a PC restart, which sucks in the middle of a Game.

 

I've tried almost everything, unpluging the mouse, dissableing/enabling the driver, relaunching CUE, nothing besides the restart works.

 

I've tried to go back on older firmware posted in this forum, I've tried so many things yet nothing's working for me.

 

I still get the occasionally annoying dis-function of my side buttons that only a whole PC restart can fix.

 

Do any of you have a similar issue ?

I'm seeing the same issue here, to the point where I'm pretty close to returning this unreliable piece of junk to the store and demanding a refund.

I've tried it on two different computers, reinstalled the drivers, etc. Nothing. Reboot usually clears the issue, but sometimes it'll take two or three restarts for things to come good.

This isn't a new issue Corsair, time to help your customers by fixing it!

I'm seeing the same issue here, to the point where I'm pretty close to returning this unreliable piece of junk to the store and demanding a refund.

 

I've tried it on two different computers, reinstalled the drivers, etc. Nothing. Reboot usually clears the issue, but sometimes it'll take two or three restarts for things to come good.

 

This isn't a new issue Corsair, time to help your customers by fixing it!

Correct, It's the issue I have atm.

Sadly glad to hear I'm not alone with this problem.

Yeah, this just happened to me.

Haven't played in acouple of days, and now the side buttons don't respond in game. Tried 2 or 3 different profiles in different games. Nothing works.

Yeah, this just happened to me.

 

Haven't played in acouple of days, and now the side buttons don't respond in game. Tried 2 or 3 different profiles in different games. Nothing works.

Did you try restarting your PC ?

When my buttons don't respond it's what I do and it helps.

There is a very simple way to fix this annoying issue. Just use Control Panel Uninstall option and Repair Corsairs Utility Engine using the installation file.

This fixes the issue in about 15 sec until next time this bug happens

There is a very simple way to fix this annoying issue. Just use Control Panel Uninstall option and Repair Corsairs Utility Engine using the installation file.

This fixes the issue in about 15 sec until next time this bug happens

So we need to repair everytime the bug appears ? Really ?

Won't that delete our profiles ?

For how long does the problem get fixed ? 1 week ? 1 month ?

So we need to repair everytime the bug appears ? Really ?

Won't that delete our profiles ?

 

For how long does the problem get fixed ? 1 week ? 1 month ?

Well, i've had this mouse for about a month and a half. It happened twice so far. One time after 2 weeks and another after 2 weeks.

And ye, it saves your profiles and everything if you repair. So, basically it's not that bad of an issue, tho it would be nice if Corsair finally fix this very old issue

Please fill out your system specs.

http://forum.corsair.com/v3/profile.php?do=extra

Depending on the macro assignment, did you try it in Windows e.g. Ctrl+****+Esc or keystrokes in Notepad? Do they work fine?

So after few months of use I got this issue too! :mad:

Repair fixed it this time.

Hello Everyone,

 

If you guys are having this issue, please post your logs so i can forward them to our validation team to assess.

Windows 10 turns on Fast Startup by default, which is a lot alike Hibernation. So when you shut down a Win10 PC, you didn't shut it as Reboot does. Turn Fast Startup off, it then shut down "for real". You can turn it off here: Power Options>Choose What the Power Buttons Do>Change Settings That Are Currently Unavailable>Uncheck Turn On Fast Startup.

With Fast Startup turned off, the side-buttons-not-working issue never happens again, not a single time. But if you turn on Hibernation function, and hibernate, the same problem will show again randomly.

OS: Windows 10 x64 up to date (2017-03-04)

CUE: 2.10.71 up to date (2017-03-04)

Firmware: 2.04 up to date (2017-03-04)

Here's the log.

(I hibernated my PC then waked it up. The side-buttons issue showed up, and I unplugged it then plugged it back in. Nothing's fixed.)

2017-03-04T11:51:43 I cue.session: Locked changed to true

2017-03-04T11:51:43 I cue.dev: Requesting working state leave because session disconnected.

2017-03-04T11:51:43 I cue.dev.enum.hid: Leaving working state.

2017-03-04T11:51:43 I cue.lightings.player: Stopped lighting worker in 0x25bc

2017-03-04T11:51:43 W cue.dev: Device "Scimitar" worker thread has stopped

2017-03-04T11:51:43 I cue.sdk: Leaving working state, session disconnected.

2017-03-04T11:51:43 I cue.sdk: Stopping router.

2017-03-04T11:51:44 I cue.dev: Requesting working state leave because of transition to Suspended or Shutdown state.

2017-03-04T11:51:44 I cue.dev.enum.hid: Leaving working state.

2017-03-04T11:51:44 I cue.sdk: Leaving working state, because of transition to Suspended or Shutdown state.

2017-03-04T11:51:44 I cue.init: Forcing profile saving.

2017-03-04T11:51:44 I cue.precise_timer: Suspended or shutdown state, stopping timer 2

2017-03-04T11:53:10 I cue.dev: Requesting working state enter because of transition from Suspended state.

2017-03-04T11:53:10 I cue.sdk: Entering working state, because of transition from Suspended state.

2017-03-04T11:53:10 I cue.sdk: Starting router.

2017-03-04T11:53:10 I cue.precise_timer: Resuming to working state, starting timer -1

2017-03-04T11:53:16 I cue.session: Locked changed to false

2017-03-04T11:53:16 I cue.dev: Requesting working state enter because session connected.

2017-03-04T11:53:16 I cue.dev.enum.hid: Entering working state.

2017-03-04T11:53:16 I cue.sdk: Entering working state, session connected.

2017-03-04T11:53:16 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=45e pid=800 not found.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=45e pid=800 not found.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=62a pid=4182 not found.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=62a pid=4182 not found.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=62a pid=4182 not found.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=62a pid=4182 not found.

2017-03-04T11:53:16 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=62a pid=4182 not found.

2017-03-04T11:53:16 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:16 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=45e pid=800 not found.

2017-03-04T11:53:16 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:16 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=45e pid=800 not found.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=45e pid=800 not found.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=45e pid=800 not found.

2017-03-04T11:53:16 I cue.dev: Manifest for device vid=45e pid=800 not found.

2017-03-04T11:53:17 I cue.dev: Created new device object: Scimitar; ready: 0

2017-03-04T11:53:17 I cue.dev: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&7094e41&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2017-03-04T11:53:17 I cue.dev: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&1eccda86&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2017-03-04T11:53:17 I cue.dev: Attached to device object Scimitar: b=0 a=0

2017-03-04T11:53:17 I cue.dev: Attached to device object Scimitar: b=0 a=0

2017-03-04T11:53:17 I cue.dev: Attached to device object Scimitar: b=0 a=1

2017-03-04T11:53:17 I cue.dev: Initializing Scimitar...

2017-03-04T11:53:17 I cue.dev.nxp: Scimitar : trying to force P0 0 instead of P0 4

2017-03-04T11:53:18 I cue.dev: Get device info failed. request timed out for Scimitar

2017-03-04T11:53:22 I cue.dev: Get device info failed. Device : Scimitar, Execution result = 0, result = 0, platform error code = 121.

2017-03-04T11:53:22 W cue.dev.nxp: Scimitar : failed, continue initialization on P0 4

2017-03-04T11:53:22 I cue.dev: Get device info failed. request timed out for Scimitar

2017-03-04T11:53:22 I cue.dev: Get device info failed. Device : Scimitar, Execution result = 0, result = 0, platform error code = 995.

2017-03-04T11:53:22 I cue.dev: Get device info failed. request timed out for Scimitar

2017-03-04T11:53:22 I cue.dev: Get device info failed. Device : Scimitar, Execution result = 0, result = 0, platform error code = 995.

2017-03-04T11:53:22 I cue.dev: Get device info failed. request timed out for Scimitar

2017-03-04T11:53:22 I cue.dev: Get device info failed. Device : Scimitar, Execution result = 0, result = 0, platform error code = 995.

2017-03-04T11:53:22 I cue.dev: Initializing Scimitar: spent all tries on getDeviceInfo().

2017-03-04T11:53:22 I cue.dev: Initializing Scimitar: failed to read proto version.

2017-03-04T11:53:23 I cue.dev: Get device info failed. request timed out for Scimitar

2017-03-04T11:53:23 I cue.dev: Get device info failed. Device : Scimitar, Execution result = 0, result = 0, platform error code = 995.

2017-03-04T11:53:23 I cue.dev: Get device info failed. request timed out for Scimitar

2017-03-04T11:53:23 I cue.dev: Get device info failed. Device : Scimitar, Execution result = 0, result = 0, platform error code = 995.

2017-03-04T11:53:23 I cue.dev: Get device info failed. request timed out for Scimitar

2017-03-04T11:53:23 I cue.dev: Get device info failed. Device : Scimitar, Execution result = 0, result = 0, platform error code = 995.

2017-03-04T11:53:23 I cue.dev: Initialized (st=0) Scimitar.

2017-03-04T11:53:23 I cue.dev: Get device info failed. request timed out for Scimitar

2017-03-04T11:53:23 I cue.dev: Get device info failed. Device : Scimitar, Execution result = 0, result = 0, platform error code = 995.

2017-03-04T11:53:23 I cue.dev: Device object failed to initialize, so it won't be registered with application susbystems. Scimitar.

2017-03-04T11:53:24 W QFSFileEngine::open: No file name specified

2017-03-04T11:53:24 C cue.download.fw: Aborting idle process not supported.

2017-03-04T11:53:24 W QFile::remove: Empty or null file name

2017-03-04T11:53:43 W cue.dev: Device "Scimitar" worker thread has stopped

2017-03-04T11:53:45 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:45 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:45 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:45 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:45 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:45 I cue.dev: Device vid=1b1c pid=1b1e is marked 'slow startup'.

2017-03-04T11:53:46 I cue.dev: Created new device object: Scimitar; ready: 0

2017-03-04T11:53:46 I cue.dev: Attached to device object Scimitar: b=0 a=0

2017-03-04T11:53:46 I cue.dev: Attached to device object Scimitar: b=0 a=0

2017-03-04T11:53:46 I cue.dev: Attached to device object Scimitar: b=0 a=1

2017-03-04T11:53:46 I cue.dev: Initializing Scimitar...

2017-03-04T11:53:46 I cue.dev: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_00#7&7094e41&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2017-03-04T11:53:46 I cue.dev.nxp: Scimitar : trying to force P0 0 instead of P0 4

2017-03-04T11:53:46 I cue.dev: Failed to open device: vid=1b1c pid=1b1e path=\\?\hid#vid_1b1c&pid_1b1e&mi_01&col01#7&1eccda86&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}

2017-03-04T11:53:46 I cue.dev.nxp: Scimitar : success, continue initialization on P0 0

2017-03-04T11:53:49 I cue.dev: Initialized (st=1) Scimitar.

2017-03-04T11:53:49 I cue.lightings.player: Started lighting worker in 0x357c

2017-03-04T11:53:49 I cue.dev: Device insertion processing complete for Scimitar.

2017-03-04T11:53:50 W QFSFileEngine::open: No file name specified

2017-03-04T11:53:50 C cue.download.fw: Aborting idle process not supported.

2017-03-04T11:53:50 W QFile::remove: Empty or null file name

2017-03-04T11:54:07 I cue.init.ui: Starting UI.

2017-03-04T11:54:08 W MainWindow_QMLTYPE_326(0xcc81458) must be a top level window.

2017-03-04T11:54:08 W MainWindow_QMLTYPE_326(0xcc81458) must be a top level window.

2017-03-04T11:54:08 W qrc:/qml/ui/accordion/LibraryPropertyViewsAccordionItem.qml:453:12: QML LibraryPropertyViewsAccordionItemToolbar: Binding loop detected for property "applyFromLibraryEnabled"

2017-03-04T11:54:15 I cue.init.ui: Trimming cache.

This obviously is a small thing to fix. It has to be something related to Fast Startup, Sleep Mode, and Hibernation. It's been two years and no solution.

Here in China all review posts said Scimitar has a Windows 10 compatibility problem, which I know is not entirely true. But people stop buying it.

It's a great mice other than this little issue. What a pity.

This obviously is a small thing to fix. It has to be something related to Fast Startup, Sleep Mode, and Hibernation. It's been two years and no solution.

 

Here in China all review posts said Scimitar has a Windows 10 compatibility problem, which I know is not entirely true. But people stop buying it.

 

It's a great mice other than this little issue. What a pity.

And herein lies the tragedy of this mouse. Mechanically it's a brilliant piece of kit but it's never worked properly.

I hung onto one that I keep in cupboard in the hope one day Corsair will sort out the bugs with this mouse. I've been unable/reluctant to use it because it's so unreliable sadly. :(:

Best

Wulf