Asus ROG Chakram X Origin - Either I got a defective mouse or there is some other issue at work here

[ButchDriveshaft]

I bought a new Chakram X Origin to use on my PC and I can not use this thing in wired mode correctly. Everytime I Power on my PC, I have to CONSTANTLY unplug, and replug the mouse in to my PC, and eventually it will work just fine, because it really just decides on its own when it wants to connect. I can't pinpoint the issue - it works just fine on my Old PC, but the PC i'm currently using it with(which is my main PC) always has this problem. Can't pinpoint if it's a driver, my PC, or the Mouse itself. Bluetooth and Wireless dongle work just fine, but even if I remove the dongle to go completely wired it will have this issue. I have to unplug it, and re plug it like 6 ****** times just to get it work. I already updated to the latest driver w/ dongle connected in Armoury Crate, but that didn't solve the problem. And no, I do not have a controller connected.

I just want to know if anyone else has had this issue, because when it works, it's a genuinely good mouse. The 8hz polling rate when used wired is especially great, but it's a pain in the ass to constantly keep plugging this thing in...

[skywalkerx]

I have the exact same issue with chakram x (non-origin) version. It happens especially if the mouse is on higher than 1000 hz polling rate mode. Some times cursor does not move sometimes buttons wont work. Also, the mouse can't hide gamepad devices correctly when in joystick compatibility mode. Here is a screenshot. 

[MasterC]

When Joystick Compatibility Mode is disabled (joystick on), then Steam will recognize it.

Test Input option availableJoystick moved down

When Joystick Compatibility Mode is enabled (joystick off), then you do not have the option to test because no joystick is detected.

Test Input option unavailable

[MasterC]

I understand you don't have a controller connected, but do you have any other device which registers as a controller?

You mentioned that it works fine on your other PC but not this one, so it seems there must be something on the current PC causing a conflict.