Jump to content
Corsair Community

Unable to update Firmware in iCue


mc6415
 Share

Recommended Posts

Every single time I attempt to update the firmware it fails on me. Looking at the logs I've got:

 

  • 2019-05-29T08:04:34 I cue.firmware.update.controller: "K70 RGB MK.2 LP" FW update has been started. From "3.19" to "3.24"
  • 2019-05-29T08:04:35 W cue.firmware.update.process.proto_n: "0" stderr: DD: tryOpen: Failed to open \\?\hid#vid_1b1c&pid_1b55&mi_00&col04#8&f1e5227&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}: 32
  • 2019-05-29T08:04:35 W cue.firmware.update.process.proto_n: "0" stderr: DD: tryOpen: Failed to open \\?\hid#vid_1b1c&pid_1b55&mi_01#8&26e1de6c&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}: 32
  • 2019-05-29T08:04:35 W cue.firmware.update.process.proto_n: "0" stderr: DD: tryOpen: Failed to open \\?\hid#vid_1b1c&pid_1b55&mi_00&col05#8&f1e5227&0&0004#{4d1e55b2-f16f-11cf-88cb-001111000030}: 5
  • 2019-05-29T08:04:35 W cue.firmware.update.process.proto_n: "0" stderr: DD: tryOpen: Failed to open \\?\hid#vid_1b1c&pid_1b55&mi_00&col01#8&f1e5227&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\kbd: 5
  • 2019-05-29T08:04:35 W cue.firmware.update.process.proto_n: "0" stderr: DD: tryOpen: Failed to open \\?\hid#vid_1b1c&pid_1b55&mi_00&col02#8&f1e5227&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}: 32
  • 2019-05-29T08:04:35 W cue.firmware.update.process.proto_n: "0" stderr: DD: tryOpen: Failed to open \\?\hid#vid_1b1c&pid_1b55&mi_00&col03#8&f1e5227&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}: 32
  • 2019-05-29T08:04:35 I cue.firmware.update.process.proto_n: "0" exit code: 4 exit status: 0 Reported: false false
  • 2019-05-29T08:04:35 I cue.firmware.update.process.proto_n: All FW update tools finished: false
  • 2019-05-29T08:04:35 I cue.firmware.update.controller: "K70 RGB MK.2 LP" FW update has been failed. From "3.19" to "3.24"
  • 2019-05-29T08:04:35 W qrc:/qml/ui/settings/DeviceSettings.qml:30: TypeError: Cannot read property 'itemIndex' of null
  • 2019-05-29T08:04:35 W cue.firmware.update: Failure during abort.

Link to comment
Share on other sites

  • Corsair Employees

Try this: https://support.corsair.com/app/answers/detail/a_id/77/kw/clean

 

Then, if that doesn't work, disconnect the keyboard and move it over to a different USB stack on the back of the computer.

 

If THAT doesn't work, try performing the update in Windows Safe Mode with Networking: https://www.digitalcitizen.life/4-ways-boot-safe-mode-windows-10

Link to comment
Share on other sites

 Share

×
×
  • Create New...