Jump to content
Corsair Community

M65 Pro RGB Mouse Windows 7 wont work


Ballistic27

Recommended Posts

I bought the M65 non pro version and it would not work on my windows 7 pc, i tell my story to the corsair support, and they have me try some basic stuff, doesnt work, so they say return the mouse and get a new one. I returned the mouse then bought the M65 Pro version and got it 2 or so weeks later yet to have the same problem..

 

Its not getting the drivers for the mouse, yet i have a Corsair K70 RGB Keyboard working just fine on my windows 7 machine.

 

Any ideas?

Link to comment
Share on other sites

it will be best to upload your logs here.

 

Does Windows detect the mouse normally? What is it detected as?

You can find this Devices and Printers under Control Panel.

 

http://i.imgur.com/GuTxAIq.pnghttp://i.imgur.com/CPV2aPx.pnghttp://i.imgur.com/2cmsCJi.pnghttp://i.imgur.com/bEYTCPE.png

 

http://i.imgur.com/S9s32NJ.png

 

Latest log file i have

[2016-04-19T08:14:21]: UserSessionInfo: locked changed to 0.
[2016-04-19T08:14:21]: UserSessionInfo: connected changed to 1.
[2016-04-19T08:14:21]: UserSessionInfo: local changed to 1.
[2016-04-19T08:14:23]: UserSessionInfo: locked changed to 0.
[2016-04-19T08:14:23]: UserSessionInfo: connected changed to 1.
[2016-04-19T08:14:23]: UserSessionInfo: local changed to 1.
[2016-04-19T08:14:25]: UserSessionInfo: locked changed to 0.
[2016-04-19T08:14:25]: UserSessionInfo: connected changed to 1.
[2016-04-19T08:14:25]: UserSessionInfo: local changed to 1.
[2016-04-19T08:14:25]: Device profile (meta) for device vid=45e pid=724 not found.
[2016-04-19T08:14:25]: Device profile (meta) for device vid=45e pid=724 not found.
[2016-04-19T08:14:25]: Device profile (meta) for device vid=5ac pid=1105 not found.
[2016-04-19T08:14:25]: Device profile (meta) for device vid=5ac pid=9226 not found.
[2016-04-19T08:14:25]: Device profile (meta) for device vid=1b1c pid=c04 not found.
[2016-04-19T08:14:25]: Failed to open device: vid=1b1c pid=1b13 path=\\?\hid#vid_1b1c&pid_1b13&mi_00#8&161b98e5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-04-19T08:14:25]: Failed to open device: vid=1b1c pid=1b13 path=\\?\hid#vid_1b1c&pid_1b13&mi_01&col01#8&39f2d6a7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-04-19T08:14:25]: Created new device object: K70 RGB; ready: 0
[2016-04-19T08:14:25]: Attached to device object K70 RGB: b=1 a=1
[2016-04-19T08:14:25]: Attached to device object K70 RGB: b=1 a=0
[2016-04-19T08:14:25]: Initializing K70 RGB...
[2016-04-19T08:14:25]: Initialized (st=1) K70 RGB.
[2016-04-19T08:14:27]: Device insertion processing complete for K70 RGB.
[2016-04-19T08:14:35]: Firmware Update: started 'C:/Program Files (x86)/Corsair/Corsair Utility Engine/fwupd path=\\?\hid#vid_1b1c&pid_1b13&mi_03#8&72919c7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030} image=C:\Users\admin\AppData\Local\Temp\l35260.K70RGB_APP_V204.bin usb-vid=1b1c usb-pid=1b13 hid-up=ffc2 test-storage=true' (2).
[2016-04-19T08:14:48]: Firmware Update: tool exit code: 0, exit status: 0. Normal stop: 1
[2016-04-19T08:15:04]: Device vid=1b1c pid=1b13 is marked 'slow startup'.
[2016-04-19T08:15:04]: Device vid=1b1c pid=1b13 is marked 'slow startup'.
[2016-04-19T08:15:04]: Device vid=1b1c pid=1b13 is marked 'slow startup'.
[2016-04-19T08:15:04]: Device vid=1b1c pid=1b13 is marked 'slow startup'.
[2016-04-19T08:15:04]: Device vid=1b1c pid=1b13 is marked 'slow startup'.
[2016-04-19T08:15:04]: Device vid=1b1c pid=1b13 is marked 'slow startup'.
[2016-04-19T08:15:05]: Device vid=1b1c pid=1b13 is marked 'slow startup'.
[2016-04-19T08:15:06]: Created new device object: K70 RGB; ready: 0
[2016-04-19T08:15:06]: Attached to device object K70 RGB: b=1 a=1
[2016-04-19T08:15:06]: Failed to open device: vid=1b1c pid=1b13 path=\\?\hid#vid_1b1c&pid_1b13&mi_00#8&161b98e5&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-04-19T08:15:06]: Failed to open device: vid=1b1c pid=1b13 path=\\?\hid#vid_1b1c&pid_1b13&mi_01&col01#8&39f2d6a7&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2016-04-19T08:15:06]: Attached to device object K70 RGB: b=1 a=1
[2016-04-19T08:15:06]: Attached to device object K70 RGB: b=1 a=0
[2016-04-19T08:15:06]: Initializing K70 RGB...
[2016-04-19T08:15:06]: Initialized (st=1) K70 RGB.
[2016-04-19T08:15:06]: Device insertion processing complete for K70 RGB.
[2016-04-19T20:37:06]: Firmware Update: killing...
[2016-04-19T20:37:06]: Firmware Download: Aborting idle process not supported.

Link to comment
Share on other sites

Windows cannot find the driver for the mouse which is preventing CUE from seeing the mouse properly.

 

Have you tried allowing Windows to search for the driver automatically? If i recall correctly, the HID devices use the default Microsoft HID driver.

 

Can you also try the mouse on another USB port and computer? Does the mouse work fine?

Link to comment
Share on other sites

Windows cannot find the driver for the mouse which is preventing CUE from seeing the mouse properly.

 

Have you tried allowing Windows to search for the driver automatically? If i recall correctly, the HID devices use the default Microsoft HID driver.

 

Can you also try the mouse on another USB port and computer? Does the mouse work fine?

 

I have tried for windows to search for the mouse automatically, doesn't work.

 

Today i was spinning up another Raspberry Pi 2 with OpenElec and i needed another mouse and used the Corsair one and it worked fine.. Before this i tried it on a windows 10 computer and it worked fine.

 

I moved it to another port still doesn't even light up nothing. It did light up on my raspberry pi though.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...