Jump to content
Corsair LogoCorsair Logo
Corsair Community
CORSAIR COMMUNITY Survey, we want to hear your feedback!

[Corsair Composite Virtual Input Device] missing from device manager

WayTooSerious

By WayTooSerious
in Keyboards and Mice

 Share

Recommended Posts

WayTooSerious

WayTooSerious

Posted
Posted

DOES A SOLUTION EXIST?

If anyone has posted a solution that I missed, I would greatly appreciate a link.

 

 

PROBLEM:

In Device Manager we are supposed to see:

[Corsair Composite Virtual Input Device]

 

The device successfully installs with installation of CUE and macros work.

After a reboot or other unknown system event, the device disappears.

 

Macro keys and the pause break key do not work because of this failure.

 

 

TEMPORARY WORKAROUND

What has worked ONCE for me was:

 

1. Uninstall CUE

2. Disconnect Keyboard

2. Restart

3. Install CUE

4. Connect Keyboard

5. Observe Device Manager

6. Repeat until [Corsair Composite Virtual Input Device] is visible in Device Manager.
Link to comment
Share on other sites
terabyte

terabyte

Posted
Posted

Which windows version are you using?

 

Also instead of uninstalling and re-installing try running again the installer while CUE is already installed, and choose the REPAIR option from it instead. Sometime a repair works better than uninstalling.

 

If that doesn't work you could try uninstalling CUE and manually removing also any leftover entries from the registry, there might be something left in there that is causing the issue in case a REPAIR won't fix it.

Link to comment
Share on other sites
terabyte

terabyte

Posted
Posted (edited)
P.S.: please don't post the same exact thing 5 times in multiple thread. You have already made your thread, no need to post in unrelated others too or you'll get replies that overlap each other. Plus it gets confusing :p: Edited by terabyte
Link to comment
Share on other sites
terabyte

terabyte

Posted
Posted

Do you have another computer (either desktop or laptop) where you can try the keyboard?

 

The issue might be something with your windows installation itself but to rule that out you'd have to try a fresh windows install. Testing it on another computer would be better (and quicker) to rule it out.

Link to comment
Share on other sites
WayTooSerious

WayTooSerious

Posted
  • Author
Posted

Regrettably, no.

I am using the keyboard at work for the macro buttons.

They greatly enhance my productivity.

 

I'm currently working on removing all traces of CUE software from the registry before this next install.

 

I can't be the first person to have this problem though...

Link to comment
Share on other sites
WayTooSerious

WayTooSerious

Posted
  • Author
Posted

I think that I've identified the issue's symptoms "a little more."

 

I use a docking station.

 

When I plugged the keyboard into a different USB port, the macros stop working, and the [Pause Break] Key's action changed to [Mode Selection] instead of [Pause Break].

 

The [Corsair Composite Virtual Input Device] was still visible in Control Panel, but the macros did not work.

 

I plugged the keyboard back into the installation USB port, and the macros began working again; however, the [Pause Break] Key's action remained changed to [Mode Selection] instead of [Pause Break].

 

Any thoughts?

Link to comment
Share on other sites
terabyte

terabyte

Posted
Posted

Okay, so the keyboard is not plugged directly into the motherboard but on a separate docking station? That's most likely the issue as you've found out.

 

Not all docking stations/usb hubs are compatible and some may cause weird issues like in your case. Try plugging the keyboard directly on your motherboard and see what happens.

Link to comment
Share on other sites
Wiztard

Wiztard

Posted
Posted
I have this exact same issue but with my Scimitar mouse. The driver simply wont load on the next reboot after installing CUE. There are several other threads about similar issues with various devices, I suspect the cause could be one and the same.
Link to comment
Share on other sites
WayTooSerious

WayTooSerious

Posted
  • Author
Posted
I have this exact same issue but with my Scimitar mouse. The driver simply wont load on the next reboot after installing CUE. There are several other threads about similar issues with various devices, I suspect the cause could be one and the same.

 

Exactly.

 

Not only does the virtual device simply not load; it doesn't even try to load; there is no failure message. The device is simply MIA like it was never even installed.

 

I saw those other threads about the similar issues too and posted my original message in each of those threads that I could find to draw attention to this unidentified glitch which I also, like you, imagine must be the cause of the plague of macro buttons not working.

Link to comment
Share on other sites
Wiztard

Wiztard

Posted
Posted

I got the following error logged in the event viewer upon install, don't know if its related or not though:

 

 

Device CorsairBus\virtualdevice&10\1&1a590e2c&f&{e7fd4ace-ee13-11e2-afda-000c29100502} could not be migrated.

 

Last Device Instance Id: USB\VID_046D&PID_C21F&IG_00\6&1A27FFF0&0&00

Class Guid: {745a17a0-74d3-11d0-b6fe-00a0c90f57da}

Location Path:

Migration Rank: 0xF000FFFFFFFFF122

Present: false

Status: 0xC0000719

Link to comment
Share on other sites
  • 1 year later...
007.SirBond

007.SirBond

Posted
Posted (edited)

Sorry for necroing a old post. But I am having this problem. Did anyone figure out a solution. Sometimes corsair composite virtual input device is missing from HID devices on restart for me. I'd really like to not have to reinstall over and over. I think it's my Logitech gaming virtual keyboard interfering. Is there any way for me to set priority so the corsair device installs first before the Logitech one?

 

EDIT: Okay, its definitely not Logitech's drivers. I uninstalled all Logitech drivers, the problem is with the corsair drivers itself.

 

The strange thing is that corsair composite virtual input device is there when I restart my computer, but as soon as CUE loads, it disappears. Basically the CUE application is making my computer think corsair composite virtual input device is disconnected.

Edited by 007.SirBond
Link to comment
Share on other sites
007.SirBond

007.SirBond

Posted
Posted (edited)

Here is my CUE Log

 

2017-07-16T02:23:28 I cue.init: CUE version: 2.15.83
2017-07-16T02:23:28 I cue.init: Updates server: https://www3.corsair.com/software/CUE_V2/
2017-07-16T02:23:28 I cue.init: Build type: Public Release
2017-07-16T02:23:28 I cue.init: Applicaiton ID: 13552
2017-07-16T02:23:28 W cue.locale: "Cannot load qt_en.qm translations"
2017-07-16T02:23:28 I cue.init.font: Using Regular text font family: "Open Sans"
2017-07-16T02:23:28 I cue.init.font: Using Title text font family: "Gotham Bold"
2017-07-16T02:23:28 I cue.session: Locked changed to false
2017-07-16T02:23:28 I cue.session.win: Will notify 'connected changed to' with delay
2017-07-16T02:23:28 I cue.session: Local changed to true
2017-07-16T02:23:28 I cue.profiles.folders.tree: Profile order deserialization started: "C:\\Users\\Terry\\AppData\\Roaming/Corsair/CUE/profiles/tree.cueprofileorder"
2017-07-16T02:23:28 I cue.profiles.folders.tree: Profile order deserialization finished: "C:\\Users\\Terry\\AppData\\Roaming/Corsair/CUE/profiles/tree.cueprofileorder"
2017-07-16T02:23:28 W cue.library: Lightings load failed:  Could not detect cereal root node - likely due to empty or invalid input
2017-07-16T02:23:28 W cue.library: Lightings load failed:  Could not detect cereal root node - likely due to empty or invalid input
2017-07-16T02:23:28 W cue.library: Actions load failed:  Could not detect cereal root node - likely due to empty or invalid input
2017-07-16T02:23:29 I cue.action.macro.win: Init time: 0.401661 (init: 2.93e-07 reset: 0.00149415 )
2017-07-16T02:23:29 I cue.session: Connected changed to true
2017-07-16T02:23:29 I cue.dev: Requesting working state enter because session connected.
2017-07-16T02:23:29 I cue.dev.enum.hid: Entering working state.
2017-07-16T02:23:29 I cue.sdk: Entering working state, session connected.
2017-07-16T02:23:29 C dev.manifest: Cannot find path for manifest key  QPair(1133,49738)
2017-07-16T02:23:29 I cue.dev: Manifest for device vid=46d pid=c24a not found.
2017-07-16T02:23:29 C dev.manifest: Cannot find path for manifest key  QPair(1133,49738)
2017-07-16T02:23:29 I cue.dev: Manifest for device vid=46d pid=c24a not found.
2017-07-16T02:23:29 C dev.manifest: Cannot find path for manifest key  QPair(1133,49738)
2017-07-16T02:23:29 I cue.dev: Manifest for device vid=46d pid=c24a not found.
2017-07-16T02:23:29 C dev.manifest: Cannot find path for manifest key  QPair(1133,49713)
2017-07-16T02:23:29 I cue.dev: Manifest for device vid=46d pid=c231 not found.
2017-07-16T02:23:29 I cue.dev: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_01&col01#8&1a9da89a&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2017-07-16T02:23:29 I cue.dev: Created new device object: K95 RGB; ready: 0
2017-07-16T02:23:29 I cue.dev: Attached to device object K95 RGB: b=0 a=0
2017-07-16T02:23:29 I cue.dev: Attached to device object K95 RGB: b=0 a=0
2017-07-16T02:23:29 I cue.dev: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_00#8&2dcdc4d8&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
2017-07-16T02:23:29 I cue.dev: Attached to device object K95 RGB: b=0 a=1
2017-07-16T02:23:29 I cue.dev: Initializing K95 RGB...
2017-07-16T02:23:29 C dev.manifest: Cannot find path for manifest key  QPair(5013,4096)
2017-07-16T02:23:29 I cue.dev: Manifest for device vid=1395 pid=1000 not found.
2017-07-16T02:23:29 C dev.manifest: Cannot find path for manifest key  QPair(1133,49714)
2017-07-16T02:23:29 I cue.dev: Manifest for device vid=46d pid=c232 not found.
2017-07-16T02:23:29 I cue.dev: Initialized (st=1) K95 RGB.
2017-07-16T02:23:30 I cue.lightings.player: Started lighting worker in 0x35e0
2017-07-16T02:23:31 I cue.dev: Device insertion processing complete for K95 RGB.
2017-07-16T02:23:31 W QFSFileEngine::open: No file name specified
2017-07-16T02:23:31 C cue.download.fw: Aborting idle process not supported.
2017-07-16T02:23:31 W QFile::remove: Empty or null file name

 

HID log:

 

[2017-06-08T00:45:18]: MacroCommand/Win: Cannot open driver device.
[2017-06-08T00:45:18]: UserSessionInfo: locked changed to 0.
[2017-06-08T00:45:18]: UserSessionInfo: connected changed to 1.
[2017-06-08T00:45:18]: UserSessionInfo: local changed to 1.
[2017-06-08T00:45:19]: Invalid XML.
[2017-06-08T00:45:19]: Invalid XML.
[2017-06-08T00:45:19]: Invalid XML.
[2017-06-08T00:45:19]: UserSessionInfo: locked changed to 0.
[2017-06-08T00:45:19]: UserSessionInfo: connected changed to 1.
[2017-06-08T00:45:19]: UserSessionInfo: local changed to 1.
[2017-06-08T00:45:20]: UserSessionInfo: locked changed to 0.
[2017-06-08T00:45:20]: UserSessionInfo: connected changed to 1.
[2017-06-08T00:45:20]: UserSessionInfo: local changed to 1.
[2017-06-08T00:45:20]: UserSessionInfo: locked changed to 0.
[2017-06-08T00:45:20]: UserSessionInfo: connected changed to 1.
[2017-06-08T00:45:20]: UserSessionInfo: local changed to 1.
[2017-06-08T00:45:20]: Created new device object: K95 RGB; ready: 0
[2017-06-08T00:45:20]: Device profile (meta) for device vid=46d pid=c24a not found.
[2017-06-08T00:45:20]: Device profile (meta) for device vid=46d pid=c24a not found.
[2017-06-08T00:45:20]: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_00#8&32d1c8b4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2017-06-08T00:45:20]: Device profile (meta) for device vid=1395 pid=1000 not found.
[2017-06-08T00:45:20]: Device profile (meta) for device vid=46d pid=c231 not found.
[2017-06-08T00:45:20]: Failed to open device: vid=1b1c pid=1b11 path=\\?\hid#vid_1b1c&pid_1b11&mi_01&col01#8&72dbcf9&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}
[2017-06-08T00:45:20]: Device profile (meta) for device vid=46d pid=c24a not found.
[2017-06-08T00:45:20]: Attached to device object K95 RGB: b=1 a=1
[2017-06-08T00:45:20]: Attached to device object K95 RGB: b=1 a=1
[2017-06-08T00:45:20]: Device profile (meta) for device vid=46d pid=c232 not found.
[2017-06-08T00:45:20]: Attached to device object K95 RGB: b=1 a=0
[2017-06-08T00:45:20]: Initializing K95 RGB...
[2017-06-08T00:45:21]: Initialized (st=1) K95 RGB.
[2017-06-08T00:45:21]: Device insertion processing complete for K95 RGB.

Edited by 007.SirBond
Link to comment
Share on other sites
  • 2 weeks later...
007.SirBond

007.SirBond

Posted
Posted (edited)

I think i figured a temporary solution.

 

If I disable Corsair Bus under System devices with the CUE application open. It asks me to restart my computer. After restarting my computer. CUE says my installer needs to be repaired. Now I enable Corsair Bus again, and Corsair composite virtual input device under Human Interface Devices now shows up as connected. I ignore the message from CUE telling me to repair and can just use the software as intended now.

 

PS: I did try a repair and it doesn't fix it. I think this problem needs to be looked into as I believe it is with the CUE application not communicating properly with the Corsair Bus under System Devices of the Device Manager.

 

And if I restart my computer. I have to do this entire process again just to get Corsair composite virtual input to show up as connected.

Edited by 007.SirBond
Link to comment
Share on other sites
007.SirBond

007.SirBond

Posted
Posted

I disabled auto start up. It does not fix anything.

 

Corsair composite virtual input device does load up at the start of my OS, I can see it in my Device Manager. But when the CUE app loads, it disconnects itself. It disconnects if its from auto startup or if I manually start CUE by opening the app.

Link to comment
Share on other sites
  • 3 months later...
Buster1

Buster1

Posted
Posted

The strange thing is that corsair composite virtual input device is there when I restart my computer, but as soon as CUE loads, it disappears. Basically the CUE application is making my computer think corsair composite virtual input device is disconnected.

 

I have EXACTLY the same problem. I repair an installation and Corsair composite virtual input device is there. I reboot, it's still there. I startup CUE and the Corsair composite virtual input device now goes "hidden" with error message "...Currently, this hardware device is not connected to the computer. (Code 45)...". Hidden means that it shows up in Computer Management -> Device Manager when you select View -> Show hidden devices.

 

Ironically, I moved from Razer keyboard and mouse to Corsair because I loved the old 1.x CUE software. Now it's the same software that has me abandoning my Corsair mouse and keyboard, going back to Razer. The fact that these types of issues have been ongoing for so long is just really disappointing. Gamers deserve more attention than this. We spend more money on exotic peripherals than consumers.

Link to comment
Share on other sites
  • 9 months later...
  • 3 weeks later...
mnoisy

mnoisy

Posted
Posted
I have the same issue with the latest iCUE 3.6.109 running on the latest Windows Home 64 bit (fully updated as of today - Sept 3rd, 2018). It definitely has to do with the iCUE software, not Windows.

 

 

x2.

 

Experiencing the identical issue. Did you get this resolved yet?

Link to comment
Share on other sites
  • 1 month later...
  • 4 months later...
 Share
Go to topic listing
×
×
  • Create New...