Jump to content
Corsair Community

Search the Community

Showing results for tags 'firmware'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • CORSAIR COMMS DEPARTMENT
    • Community Rules & Announcements
    • Live Event Announcements
    • New Product Releases
  • COMMUNITY DISCUSSIONS
    • Non-CORSAIR Tech, Benchmarks, and Overclocking
    • Games & Gaming
    • Battlestation and Build Showcase
  • TECHNICAL SUPPORT & CUSTOMER SERVICE
    • iCUE Software Troubleshooting
    • Build Hardware Troubleshooting
    • Gaming Peripherals & Audio Troubleshooting
    • Furniture and Ambient Lighting Troubleshooting
    • CORSAIR Pre-Built Systems Troubleshooting
  • PRODUCT DISCUSSIONS
    • CORSAIR iCUE
    • Build Hardware
    • Gaming Peripherals
    • Audio Devices
    • Battlestation Hardware: Ambient Lighting, Furniture, etc.
    • CORSAIR Pre-Built Systems
    • CORSAIR Technologies Q&A
  • Alternative Languages
    • Deutscher Support (German Support)
    • French Support
    • Spanish Support
  • LEGACY TOPICS
    • Corsair Enthusiasts Section
    • Corsair Product Discussion
    • Alternate Language Support
    • Customer Service

Categories

  • System Build Inspiration
  • Memory
  • Cases
  • iCUE CONTROLLERS
  • Maximizing Performance
  • Peripherals
  • Storage
  • Liquid Cooling
  • Gaming Mice
  • News and Events
  • How-tos and DIY
  • USB Drives
  • Extreme OC Mods
  • Gaming Keyboards
  • Power Supply Units
  • Gaming Headsets
  • Uncategorized

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Interests


Occupation


Optical Drive # 1


Homepage


ICQ


AIM


Yahoo


MSN


Skype

  1. I updated the version of Icue to version 4 and it appeared that I could update the firmware version of the K68 keyboard and update it. It asked me to restart windows and when I started again the scroll lock key started blinking and the keyboard did not work. The rgb does turn on even though it did not load the ICUE configuration. For everything to work correctly when starting windows I have to unplug the USB from the keyboard and reconnect it, with this it already loads the ICue configuration and the keys do work. When connecting and disconnecting the keyboard, window makes the typical sound of recognizing the keyboard and at the moment Icue also recognizes it, so I understand that windows does not recognize it and therefore neither does Icue. I've tried different usb ports and still the same. I have tried to force the update of the keyboard from iCue and still the same. I think this is because windows doesn't detect it on startup for some reason when I upgrade to this version of the keyboard. Current versions of ICue and keyboard: Version ICUE -> v.4.25.155 Keyboard firmware version -> v.3.12 The corsair harpoon mouse and the corsair void headset work correctly and charge well, these were not updated. I am attaching the ICue logs, where I have been able to review and it seems that there are some errors but I would not be able to determine if it is correct or not. I have the log report of everything taken from Icue, but it is not a file allowed to upload. I leave here some sample reports from today when starting the system. These reports are from the CUELOGS folder: 2022-07-28 08:47:32.214 I cue.sdk.game.profile_update_scheduler: Scheduled next update at QDateTime(2022-08-04 08:47:32.213 Hora de verano romance Qt::LocalTime) 2022-07-28 08:47:32.215 I cue.session: Connected changed to true 2022-07-28 08:47:32.215 I cue.sdk: Entering working state, session connected. 2022-07-28 08:47:32.215 I cue.sdk: Starting router. 2022-07-28 08:47:32.215 I cue.sdk.device_watcher: Start prepare RestoreDeviceOrderState 2022-07-28 08:47:32.215 I cue.sdk.device_watcher: Finish prepare RestoreDeviceOrderState 2022-07-28 08:47:32.215 I cue.clink.device.hw_lightings: Working state about to change, lock hw lights preview. 2022-07-28 08:47:32.215 I cue.sdk.automation.server: User session about to be unlocked. Starting a listening 2022-07-28 08:47:32.218 I cue.sdk.automation.server: Successfully started listening 2022-07-28 08:47:32.218 I cue.dev.enum.adapter: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed. 2022-07-28 08:47:32.218 I cue.devices.enum.clink: Entering working state. 2022-07-28 08:47:32.218 I cue.dev.enum.adapter: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed. 2022-07-28 08:47:32.218 I cue.devices.enum.headset_accessory: Entering working state. 2022-07-28 08:47:32.223 I cue.dev.enum.adapter: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed. 2022-07-28 08:47:32.223 I cue.devices.enum.dram: Entering working state. 2022-07-28 08:47:32.223 I cue.dev.enum.adapter: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed. 2022-07-28 08:47:32.227 I cue.dev.enum.adapter: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed. 2022-07-28 08:47:32.230 I cue.devices.enum.hid: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed. 2022-07-28 08:47:32.230 W cue.hid_device_detector: Device detector already disabled. 2022-07-28 08:47:32.321 I cue.dev.enum.mccs: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed. 2022-07-28 08:47:32.327 I cue.dev.mccs.usb_detector: Device detection started. 2022-07-28 08:47:32.328 I cue.devices.enum.router: Entering working state. DeviceEnumeratorBase::WorkingStateChangeReason::UserSessionPropertyChanged Session allowed. 2022-07-28 08:47:32.328 I cue.devices.enum.phost: Entering working state. 2022-07-28 08:47:32.528 I cue.plugin.host: Signature verified: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/iCUEDevicePluginHost.exe" 2022-07-28 08:47:32.630 I cue.plugin.host: Signature verified: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/ASUS/asus_plugin.dll" 2022-07-28 08:47:32.630 I cue.plugin.host: Starting check if plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/ASUS/asus_plugin.dll" 2022-07-28 08:47:32.734 I cue.plugin.host: Signature verified: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/Lenovo/CUEPlugin.dll" 2022-07-28 08:47:32.734 I cue.plugin.host: Starting check if plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/Lenovo/CUEPlugin.dll" 2022-07-28 08:47:32.818 I cue.plugin.host: Signature verified: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/LenovoY750s/y750splugin.dll" 2022-07-28 08:47:32.818 I cue.plugin.host: Starting check if plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/LenovoY750s/y750splugin.dll" 2022-07-28 08:47:32.906 I cue.plugin.host: Signature verified: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/LenovoY760/Y760Plugin.dll" 2022-07-28 08:47:32.906 I cue.plugin.host: Starting check if plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/LenovoY760/Y760Plugin.dll" 2022-07-28 08:47:33.245 I cue.plugin.host: Signature verified: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/LenovoY760s/y760spluginX64.dll" 2022-07-28 08:47:33.245 I cue.plugin.host: Starting check if plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/LenovoY760s/y760spluginX64.dll" 2022-07-28 08:47:33.289 I cue.plugin.host: Signature verified: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/MSI/CueMsiPlugin.dll" 2022-07-28 08:47:33.289 I cue.plugin.host: Starting check if plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/MSI/CueMsiPlugin.dll" 2022-07-28 08:47:33.485 I cue.plugin.host: Signature verified: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/MSI/MysticLight_SDK_x64.dll" 2022-07-28 08:47:33.485 I cue.plugin.host: Starting check if plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/MSI/MysticLight_SDK_x64.dll" 2022-07-28 08:47:33.529 I cue.plugin.host: Signature verified: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/Nvidia/NvidiaPlugin.dll" 2022-07-28 08:47:33.530 I cue.plugin.host: Starting check if plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/Nvidia/NvidiaPlugin.dll" 2022-07-28 08:47:33.587 I cue.clink.device.hw_lightings: Entering working state, unlock and disable hw lights preview. 2022-07-28 08:47:33.617 W cue.devices.enum.clink: Can't update devices, isn't connected 2022-07-28 08:47:33.619 C cue.push.controller: Failed to get en_US push notifications: content is not found 2022-07-28 08:47:33.619 I cue.devices: Audio device added: "(vid=1b1c, pid=a1e)" 2022-07-28 08:47:33.619 I cue.dev.enum.mccs: Found: 0 , initialized: 0 2022-07-28 08:47:33.620 I cue.plugin.host: Plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/ASUS/asus_plugin.dll" 2022-07-28 08:47:33.621 I cue.plugin.host: Plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/LenovoY750s/y750splugin.dll" 2022-07-28 08:47:33.623 I cue.plugin.host: Plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/LenovoY760s/y760spluginX64.dll" 2022-07-28 08:47:33.624 I cue.plugin.host: Plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/Lenovo/CUEPlugin.dll" 2022-07-28 08:47:33.625 I cue.plugin.host: Plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/LenovoY760/Y760Plugin.dll" 2022-07-28 08:47:33.626 I cue.plugin.host: Plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/MSI/CueMsiPlugin.dll" 2022-07-28 08:47:33.628 I cue.mod.nxp.enum: Device vid=1b1c pid=a1e ignored by cue::dev::legacy::NxpEnumerator 2022-07-28 08:47:33.629 I cue.mod.nxp.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_01#7&1ec7b2ea&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3c&mi_01\\7&1ec7b2ea&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_1B3C\\0803E021AF0E94E359375D6BF5001942\u0000") inserted. 2022-07-28 08:47:33.629 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_01#7&1ec7b2ea&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms. 2022-07-28 08:47:33.632 I cue.mod.nxp.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col02#7&309761b6&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3f&mi_00&col02\\7&309761b6&0&0001", ParentInstanceId: "USB\\VID_1B1C&PID_1B3F\\1800F019AF3AA4005B8DC8FBF5001BC5\u0000") inserted. 2022-07-28 08:47:33.632 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col02#7&309761b6&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms. 2022-07-28 08:47:33.633 I cue.mod.nxp.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col03#7&309761b6&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3f&mi_00&col03\\7&309761b6&0&0002", ParentInstanceId: "USB\\VID_1B1C&PID_1B3F\\1800F019AF3AA4005B8DC8FBF5001BC5\u0000") inserted. 2022-07-28 08:47:33.633 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col03#7&309761b6&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms. 2022-07-28 08:47:33.634 I cue.mod.nxp.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col04#7&309761b6&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3f&mi_00&col04\\7&309761b6&0&0003", ParentInstanceId: "USB\\VID_1B1C&PID_1B3F\\1800F019AF3AA4005B8DC8FBF5001BC5\u0000") inserted. 2022-07-28 08:47:33.634 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col04#7&309761b6&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms. 2022-07-28 08:47:33.635 I cue.mod.nxp.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_01#7&1d674578&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3f&mi_01\\7&1d674578&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_1B3F\\1800F019AF3AA4005B8DC8FBF5001BC5\u0000") inserted. 2022-07-28 08:47:33.635 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_01#7&1d674578&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms. 2022-07-28 08:47:33.635 I cue.mod.nxp.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_00&col01#7&368b3f2f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3c&mi_00&col01\\7&368b3f2f&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_1B3C\\0803E021AF0E94E359375D6BF5001942\u0000") inserted. 2022-07-28 08:47:33.635 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_00&col01#7&368b3f2f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms. 2022-07-28 08:47:33.635 I cue.mod.nxp.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col01#7&309761b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd", InstanceId: "hid\\vid_1b1c&pid_1b3f&mi_00&col01\\7&309761b6&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_1B3F\\1800F019AF3AA4005B8DC8FBF5001BC5\u0000") inserted. 2022-07-28 08:47:33.636 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col01#7&309761b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd" with delay 0 ms. 2022-07-28 08:47:33.636 I cue.mod.nxp.enum: Device vid=1b1c pid=a1e ignored by cue::dev::legacy::NxpEnumerator 2022-07-28 08:47:33.636 I cue.mod.nxp.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_00&col02#7&368b3f2f&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3c&mi_00&col02\\7&368b3f2f&0&0001", ParentInstanceId: "USB\\VID_1B1C&PID_1B3C\\0803E021AF0E94E359375D6BF5001942\u0000") inserted. 2022-07-28 08:47:33.636 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_00&col02#7&368b3f2f&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms. 2022-07-28 08:47:33.636 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_0a1e&mi_03&col02#7&bc94eb4&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_0a1e&mi_03&col02\\7&bc94eb4&0&0001", ParentInstanceId: "USB\\VID_1B1C&PID_0A1E\\00000000\u0000") inserted. 2022-07-28 08:47:33.636 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_0a1e&mi_03&col02#7&bc94eb4&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms. 2022-07-28 08:47:33.637 I cue.mod.nxp.enum: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_00&col03#7&368b3f2f&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_1b3c&mi_00&col03\\7&368b3f2f&0&0002", ParentInstanceId: "USB\\VID_1B1C&PID_1B3C\\0803E021AF0E94E359375D6BF5001942\u0000") inserted. 2022-07-28 08:47:33.637 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_00&col03#7&368b3f2f&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms. 2022-07-28 08:47:33.637 I cue.devices: Device vid=1b1c pid=1b3c ignored by HidDeviceEnumerator 2022-07-28 08:47:33.639 I cue.devices: Device vid=1b1c pid=1b3f ignored by HidDeviceEnumerator 2022-07-28 08:47:33.640 I cue.devices: Device vid=1b1c pid=1b3f ignored by HidDeviceEnumerator 2022-07-28 08:47:33.640 I cue.devices: Device vid=1b1c pid=1b3f ignored by HidDeviceEnumerator 2022-07-28 08:47:33.641 I cue.devices: Device vid=1b1c pid=1b3f ignored by HidDeviceEnumerator 2022-07-28 08:47:33.642 I cue.devices: Device vid=1b1c pid=1b3c ignored by HidDeviceEnumerator 2022-07-28 08:47:33.642 I cue.devices: Device vid=1b1c pid=1b3f ignored by HidDeviceEnumerator 2022-07-28 08:47:33.642 I cue.hid_device_detector: DeviceInstance(Path: "\\\\?\\hid#vid_1b1c&pid_0a1e&mi_03&col01#7&bc94eb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}", InstanceId: "hid\\vid_1b1c&pid_0a1e&mi_03&col01\\7&bc94eb4&0&0000", ParentInstanceId: "USB\\VID_1B1C&PID_0A1E\\00000000\u0000") inserted. 2022-07-28 08:47:33.642 I cue.hid_device_detector: Add open task: "\\\\?\\hid#vid_1b1c&pid_0a1e&mi_03&col01#7&bc94eb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" with delay 0 ms. 2022-07-28 08:47:33.642 I cue.devices: Device vid=1b1c pid=1b3c ignored by HidDeviceEnumerator 2022-07-28 08:47:33.642 I cue.devices: Device vid=1b1c pid=1b3c ignored by HidDeviceEnumerator 2022-07-28 08:47:33.643 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_01#7&1ec7b2ea&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-07-28 08:47:33.643 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0a1e&mi_03&col02#7&bc94eb4&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-07-28 08:47:33.643 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_0a1e&mi_03&col01#7&bc94eb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-07-28 08:47:33.643 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col02#7&309761b6&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-07-28 08:47:33.643 I cue.hid_device_detector: Mark all tasks as finished. 2022-07-28 08:47:33.644 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col03#7&309761b6&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-07-28 08:47:33.644 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col04#7&309761b6&0&0003#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-07-28 08:47:33.644 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_01#7&1d674578&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-07-28 08:47:33.644 C cue.hid_device_detector: Failed to open: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_00&col01#7&368b3f2f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" 2022-07-28 08:47:33.645 C cue.hid_device_detector: Failed to open: "\\\\?\\hid#vid_1b1c&pid_1b3f&mi_00&col01#7&309761b6&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}\\kbd" 2022-07-28 08:47:33.645 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_00&col02#7&368b3f2f&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-07-28 08:47:33.645 I cue.hid_device_detector: "\\\\?\\hid#vid_1b1c&pid_1b3c&mi_00&col03#7&368b3f2f&0&0002#{4d1e55b2-f16f-11cf-88cb-001111000030}" opened. 2022-07-28 08:47:33.645 I cue.hid_device_detector: Mark all tasks as finished. 2022-07-28 08:47:33.657 W QObject::connect(HidDeviceBatteryController, HeadsetHidDevice): invalid nullptr parameter 2022-07-28 08:47:33.658 I cue.devices: Begin attaching to "VOID PRO SURROUND" "(vid=1b1c, pid=a1e)" "\\\\?\\hid#vid_1b1c&pid_0a1e&mi_03&col02#7&bc94eb4&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 0 2022-07-28 08:47:33.658 I cue.devices: End attaching to "VOID PRO SURROUND" "(vid=1b1c, pid=a1e)" "\\\\?\\hid#vid_1b1c&pid_0a1e&mi_03&col02#7&bc94eb4&0&0001#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1 2022-07-28 08:47:33.846 W cue.devices.audio: Failed to set audio device format: -2004287480 2022-07-28 08:47:33.846 C cue.devices.audio.driver.win: Unable to clear profile. Profile guid = "{8a5527dd-29ed-49b0-8be9-5667ad8999e1}" 2022-07-28 08:47:33.847 C cue.devices.audio.driver.win: Unable to initialize AudioProfile with such guid = "{8a5527dd-29ed-49b0-8be9-5667ad8999e1}" 2022-07-28 08:47:33.867 I cue.devices.enum.hid: Audio device attached "(vid=1b1c, pid=a1e)" 2022-07-28 08:47:33.868 I cue.devices: Created new device"VOID PRO SURROUND" "(vid=1b1c, pid=a1e)"; ready:true 2022-07-28 08:47:33.872 W cue.plugin.host: File isn't supported plugin: 4 "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/MSI/MysticLight_SDK_x64.dll" 2022-07-28 08:47:33.873 I cue.devices: Begin attaching to "VOID PRO SURROUND" "(vid=1b1c, pid=a1e)" "\\\\?\\hid#vid_1b1c&pid_0a1e&mi_03&col01#7&bc94eb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status b= 1 2022-07-28 08:47:33.873 I cue.devices: End attaching to "VOID PRO SURROUND" "(vid=1b1c, pid=a1e)" "\\\\?\\hid#vid_1b1c&pid_0a1e&mi_03&col01#7&bc94eb4&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}" status a= 1 2022-07-28 08:47:33.873 I cue.devices.enum.hid: Audio device attached "(vid=1b1c, pid=a1e)" 2022-07-28 08:47:33.886 I cue.devices: Initializing "VOID PRO SURROUND" "(vid=1b1c, pid=a1e)" 2022-07-28 08:47:33.887 I cue.mod.nxp.enum: Initializing "K68" "(vid=1b1c, pid=1b3f)" 2022-07-28 08:47:33.891 I cue.mod.nxp.enum: Initializing "HARPOON RGB" "(vid=1b1c, pid=1b3c)" 2022-07-28 08:47:33.891 I cue.mod.nxp.hid_io.mouse: "HARPOON RGB trying to force P00 instead of P05" 2022-07-28 08:47:33.906 I cue.mod.nxp.hid_io.mouse: "HARPOON RGB" success, continue initialization on P00 2022-07-28 08:47:33.917 I cue.mod.nxp.enum: Initialized true "HARPOON RGB" "(vid=1b1c, pid=1b3c)" 2022-07-28 08:47:33.936 I cue.mod.nxp.enum: Initialized true "K68" "(vid=1b1c, pid=1b3f)" 2022-07-28 08:47:33.949 I cue.dev.mgr: Candidate device for QMap(("bus", "legacy")("usb-pid", "6972")("usb-vid", "6940")) not found. 2022-07-28 08:47:33.951 W Unimplemented conversion for command: 28 2022-07-28 08:47:33.951 W cue.dev.control.brightness_value: Get dpi brightness level failure 2022-07-28 08:47:33.951 W Unimplemented conversion for command: 32 2022-07-28 08:47:33.951 W Unimplemented conversion for command: 114 2022-07-28 08:47:33.951 W Unimplemented conversion for command: 183 2022-07-28 08:47:33.951 W Unimplemented conversion for command: 184 2022-07-28 08:47:33.951 W Unimplemented conversion for command: 185 2022-07-28 08:47:33.951 W Unimplemented conversion for command: 186 2022-07-28 08:47:33.951 W Unimplemented conversion for command: 187 2022-07-28 08:47:33.951 W Unimplemented conversion for command: 188 2022-07-28 08:47:33.951 W Unimplemented conversion for command: 180 2022-07-28 08:47:33.953 I cue.profiles.mappings_actualizer: Device doesn't need volume wheel workaround: "HARPOON RGB" 2022-07-28 08:47:33.953 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "6972")("usb-vid", "6940")) 2022-07-28 08:47:33.973 W cue.devices.cmd_handler: Unknown command in CommandHandlerBase: cue::dev::cmd::id_ns::Id::GetConnectionType 2022-07-28 08:47:33.984 W cue.devices.cmd_handler: Unknown command in CommandHandlerBase: cue::dev::cmd::id_ns::Id::GetButtonDebounceAlgorithm 2022-07-28 08:47:33.986 C cue.models.present_device: Cannot get model index for CorsairDevicePtr("HARPOON RGB"; 0x1dd28e08870) Model does't contain the device. 2022-07-28 08:47:33.991 W cue.devices.cmd_handler: Unknown command in CommandHandlerBase: cue::dev::cmd::id_ns::Id::GetLightingMode 2022-07-28 08:47:33.999 I cue.devices.audio.driver.win: Setting up new device 2022-07-28 08:47:34.000 C cue.devices.audio.driver.win: Unable to clear profile. Profile guid = "{8a5527dd-29ed-49b0-8be9-5667ad8999e1}" 2022-07-28 08:47:34.002 C cue.devices.audio.driver.win: Unable to clear profile. Profile guid = "{548db709-3562-4d11-bbe5-71251cd14053}" 2022-07-28 08:47:34.010 I cue.devices: Device insertion processing complete for HARPOON RGB (vid=1b1c, pid=1b3c) 2022-07-28 08:47:34.012 I cue.lightings.direct_player: Started lighting worker in 0xe50 2022-07-28 08:47:34.029 I cue.dev.mgr: Candidate device for QMap(("bus", "legacy")("usb-pid", "6975")("usb-vid", "6940")) not found. 2022-07-28 08:47:34.031 W cue.devices.cmd_handler: Unknown command in CommandHandlerBase: cue::dev::cmd::id_ns::Id::GetConnectionType 2022-07-28 08:47:34.031 W Unimplemented conversion for command: 28 2022-07-28 08:47:34.031 W cue.dev.control.brightness_value: Get dpi brightness level failure 2022-07-28 08:47:34.031 W Unimplemented conversion for command: 32 2022-07-28 08:47:34.031 W Unimplemented conversion for command: 114 2022-07-28 08:47:34.031 W Unimplemented conversion for command: 183 2022-07-28 08:47:34.031 W Unimplemented conversion for command: 184 2022-07-28 08:47:34.031 W Unimplemented conversion for command: 185 2022-07-28 08:47:34.031 W Unimplemented conversion for command: 186 2022-07-28 08:47:34.031 W Unimplemented conversion for command: 187 2022-07-28 08:47:34.031 W Unimplemented conversion for command: 188 2022-07-28 08:47:34.031 W Unimplemented conversion for command: 180 2022-07-28 08:47:34.035 W cue.profiles.mappings_actualizer: HW layouts are not ready! "K68" 2022-07-28 08:47:34.036 I cue.dev.mgr: Found candidate device for QMap(("bus", "legacy")("usb-pid", "6975")("usb-vid", "6940")) 2022-07-28 08:47:34.074 W cue.devices.cmd_handler: Unknown command in CommandHandlerBase: cue::dev::cmd::id_ns::Id::GetLightingMode 2022-07-28 08:47:34.078 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.078 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.080 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.080 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.082 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.082 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.084 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.084 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.085 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.086 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.087 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.087 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.089 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.089 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.092 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.092 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.094 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.094 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.095 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.095 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.097 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.097 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.098 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.098 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.100 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.100 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.103 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.103 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.105 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.105 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.108 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.109 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.112 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.112 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.113 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.113 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.115 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.115 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.117 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.117 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.118 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.118 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.120 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.120 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.121 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.121 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.125 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.125 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.127 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.127 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.128 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.128 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.130 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.130 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.131 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.132 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.134 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.134 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.137 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.138 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.144 C cue.models.present_device: Cannot get model index for CorsairDevicePtr("K68"; 0x1dd247c7a30) Model does't contain the device. 2022-07-28 08:47:34.146 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.146 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.155 W cue.devices.layout: Invalid HW layout 2022-07-28 08:47:34.155 C cue.manifest: Cannot find "" layout for "K68" 2022-07-28 08:47:34.159 I cue.devices: Device insertion processing complete for K68 (vid=1b1c, pid=1b3f) 2022-07-28 08:47:34.159 I cue.dev.conn_proxy: Device does not support multiple connection types 2022-07-28 08:47:34.159 W cue.dev.control.button_debounce: Get button debounce mode failure 2022-07-28 08:47:34.161 I cue.plugin.host: Plugin is supported: "C:/Program Files/Corsair/CORSAIR iCUE 4 Software/plugins/Nvidia/NvidiaPlugin.dll" 2022-07-28 08:47:34.162 I cue.plugin.host: Plugins ready to be started 2022-07-28 08:47:34.162 I cue.plugin.host: Elevated host required: true 2022-07-28 08:47:34.165 I cue.lightings.direct_player: Started lighting worker in 0x2abc 2022-07-28 08:47:34.553 I cue.ro_helpers: HostServiceIpc(0x1dd249a1a50) Start connecting to host QUrl("") 2022-07-28 08:47:34.567 W cue.profiles.mappings_actualizer: HW layouts are not ready! "K68" 2022-07-28 08:47:34.567 I cue.profiles.mappings_actualizer: Use volume wheel workaround for "K68" 2022-07-28 08:47:34.569 I cue.dev.conn_proxy: Device does not support multiple connection types 2022-07-28 08:47:34.582 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image" 2022-07-28 08:47:34.582 I cue.firmware.index: "K68" firmware update, expected version: 3.12 same version found, on device: bootloader: 3.0 firmware: 3.12 2022-07-28 08:47:34.584 I cue.ro_helpers: HostServiceIpc(0x1dd249a1a50) Start connecting to host QUrl("tcp://127.0.0.1:58545") 2022-07-28 08:47:34.585 I cue.ro_helpers: HostServiceIpc(0x1dd249a1a50) Successfully connected to host node at QUrl("tcp://127.0.0.1:58545") 2022-07-28 08:47:34.586 I cue.devices.enum.clink: Failed to find manifest: "(vid=1b1c, pid=1)" 2022-07-28 08:47:34.587 I cue.devices.enum.clink: Failed to find manifest: "(vid=1b1c, pid=7)" 2022-07-28 08:47:34.587 I cue.devices.enum.clink: Failed to find manifest: "(vid=1b1c, pid=8)" 2022-07-28 08:47:34.587 I cue.devices.enum.clink: Failed to find manifest: "(vid=1b1c, pid=2)" 2022-07-28 08:47:34.587 I cue.devices.enum.clink: Failed to find manifest: "(vid=1b1c, pid=7)" 2022-07-28 08:47:34.588 W cue.common.download: The download process is not started 2022-07-28 08:47:34.589 I cue.ro_helpers: HostServiceIpc(0x1dd249a1a50) Replica state changed: QRemoteObjectReplica::Default -> QRemoteObjectReplica::Valid 2022-07-28 08:47:34.622 I cue.plugin: Container running, isReady: false "ASUS/asus_plugin.dll" 2022-07-28 08:47:34.678 I cue.plugin: Container running, isReady: false "LenovoY750s/y750splugin.dll" 2022-07-28 08:47:34.720 I cue.plugin: Container running, isReady: false "LenovoY760s/y760spluginX64.dll" 2022-07-28 08:47:34.774 I cue.plugin: Container running, isReady: false "Lenovo/CUEPlugin.dll" 2022-07-28 08:47:34.796 I cue.plugin: Container connected: "ASUS/asus_plugin.dll" 2022-07-28 08:47:34.800 I cue.plugin: Container running, isReady: true "ASUS/asus_plugin.dll" 2022-07-28 08:47:34.824 I cue.plugin: Container running, isReady: false "LenovoY760/Y760Plugin.dll" 2022-07-28 08:47:34.831 C cue.firmware.index: Incorrect index contents: fw obj is empty "combined-image" 2022-07-28 08:47:34.831 I cue.firmware.index: "HARPOON RGB" firmware update, expected version: 3.8 same version found, on device: bootloader: 1.0 firmware: 3.8 2022-07-28 08:47:34.833 I cue.plugin: Start processing: "ASUS/asus_plugin.dll" Thanks for the help
  2. i just updated the wireless dongle firmware to 5.4.99. but after the update and restarting, my laptop (lenovo s14-iil running on windows 10 home updated) isn't recognizing it upon restart automatically. I have to unplug and plug the dongle back for it to be recognized. note: i already did extensive troubleshooting (restarted multiple times, paired my keyboard back multiple times, etc., updated icue to the latest version) but it seems the problem is in the firmware itself not being compatible with the latest windows update. has anyone experienced this? if yes, is there a fix? to corsair tech team. Has anyone raised this problem? please assist to resolve immediately.
  3. Recently I had an issue with my K70 RGB MK.2 keyboard and reached out to corsair support where they then instructed me to reinstall the firmware and provided me with a bin file. I followed their instructions exactly but now my keyboard won't power on and isn't detected. Reviewing the file name of their provided .bin file closer, I believe I was sent the firmware of the wrong model even though I provided my P/N and S/N as it was required when creating the ticket. Looking through old forum posts of users having the same problem, corsair staff stated installing the wrong firmware can brick your keyboard permanently. Now I'm worried my keyboard is now perma bricked and I'm at a loss of what to do since I use the keyboard & configured macros for my job. Anyone have any ideas of how to fix this?
  4. Hello, I have my headset on firmware 0.17.149 (ICUE V3) and i want to update it on firmware 5.2.68 (ICUE V4) I want to know if someone has the firmware file (.zip or .bin) to update it manualy via icue V4. Because my Headset is blinking red. Thank You
  5. Problem: About a month or so ago maybe, when I did the most recent updates for the headset and dongle on my PC (windows 10 and latest iCUE version 4.x.x) and also having done slipstream pairing both my corsair dark core SE and my Virtuoso SE to the Virtuoso dongle... I realized it created 2 different playback devices (see attached files/pics). When I have my cable plugged in and I switch back and forth between wireless and wired modes, they don't automatically switch in windows anymore. I noticed this happen when I was playing games (about a month ago maybe?) and chilling on a discord call when all of sudden the audio just seemed to break and then I noticed that there was the 2 playback devices now instead of the 1 after trying to figure out what was wrong. Everything works fine still except for the seamless transition between wired and wireless where I have to physically click to change the playback device for either the wired or wireless. It's even more annoying because I have to switch it in discord because it seems discord doesn't pick it up either unless I switch it in discord settings. Things I have tried: I tested this on my other gaming laptop (windows 10) iCUE version 3.x.x legacy except on my laptop it only shows 1 pair of input and outputs in device manager and only 1 playback device and works with no problems switching back and forth. iCUE versions are up to date on both my PC and laptop also all the way up to date with windows updates. Resetting my PC erasing all files and apps and it still seems to set up the same way with playback devices and in device manager. Uninstalling the Corsair Virtuoso devices showing in device manager, unplugging the virutoso, restarting, uninstalling iCUE, restarting, re-installing iCUE. Nada. Conclusion: I'm not really sure what the issue is. If the firmware was the issue wouldn't it be affecting my laptop the same way? Any thoughts or suggestions? Thanks in advance. Versions: Windows 10 (latest up to this point) VIRTUOSO SE WIRELESS RECEIVER Firmware v.5.7.115 (latest up to this point) VIRTUOSO SE Firmware v.5.3.70 (latest up to this point) TL;DR: My Corsair Virtuoso no longer seamlessly switches back and forth between wired and wireless without me having to go to windows playback device and choosing the corresponding wired or wireless version. Everything else works fine. Any advice much appreciated.
  6. Hello. I would greatly appreciate it if someone could provide me with a download for the firmware v.2.4.14 (dongle) and firmware v.2.7.37 (mouse) for my dark core RGB pro SE mouse so that icue 3.38.61 can detect it again. Thank you
  7. Hi all! Today iCue suggested a firmware update for me, and now my AIO is dead: FANs at full RPM, no RGB and iCue no longer recognize AIO. Have tried many things and no luck, changed USB port, restarted service and so on :,c I recently read other forums in which they talk about the same topic :c and from what I could see, everyone was able to solve the problem with the hex file of the iCUE H150i RGB PRO XT so I was wondering if you could help me by sharing that file, since the link From mediafire that I enter it says that the file has been deleted, please can you share that file with me to solve my problem since I cannot find the hex file on my computer: c I will be very grateful in advance
  8. about a week ago i plugged in my K70 RGB Rapidfire to a folder titled CRP DISABLD popped up with a file in it labled "firmware.bin". i've already sent a ticket in but no one has responded yet. is there anyone who can help me?
  9. I'll admit I'm a Corsair fanboy and now have quite a collection of hardware. What has struck me for months is that there are apparently no more firmware updates for my hardware. Is nothing further developed or is this a bug? I have the following current status: iCUE 4.19.191 Vengeance Pro 1.03.66 Dark Core Pro SE 5.0.41 HS80 Wireless Receiver 5.5.102 ST100RGB 0.04.106 Commander Pro 0.9.212 H150i PRO 1.0.4 LT100 1.1.38 K70 RGB MK.2 3.24
  10. I updated the firmware to v. 5.5.102 and it broke the pairing for my icue, when i click the pair button the menu will pop up showing what connections to use, the motherboard usb ports or the front/side usb ports, but when i click "next" to pair, the menu closes not allowing me to pair it. only started happening with this latest update, i tried a fresh install of icue and it did nothing the firmware stays the same where do i get a lower version of the firmware to install it? Exact same issue as this, probably put the answer to the post actually in the post so others do not need to put in a ticket.
  11. As the title says. I was just told to update my rams firmware but what am I changing? Where are the changelogs. Come on guys it's 2021 tell us what is different and why we need it. Is that so hard? I'm running this exact ram on a i9-10900k CMT32GX4M2C3466C16
  12. Hello everyone. I bought an ironclaw yesterday and was working fine until I tried to update the firmware when I installed iCue. After that my mouse stopped responding although it is on with rgb and everything and is charged. It is not showing up on iCUE or windows (on windows it is shown as "Game mouse" instead of Ironclaw rgb wireless that was in the beginning). I still get the dongle on iCUE though but every option is greyed out. I tried a fresh install of iCue, an older version of iCUe, a different PC but it makes no difference. I'd like to add that i tried connecting my mouse to my mobile and it worked fine via bluetooth :biggrin:. But on computer it doenst work wired or wireless. Imo something went wrong on the firmware update and the dongle upgraded and mouse got corrupted but i really have no clue how to fix it. Any help would be appreciated.
  13. Hola a todos, he tenido un problema con mis nuevos auriculares void RGB elite Wireless y es que cuando instalé el ICUE y me decía que tenia una actualización de firmware que conectara los auriculares, entonces no se que paso que me hizo elegir unos cuantos modelos y como no ponía wireless elegí el único que si lo decía en su caso instalé (HS70 Wireless) y ahora no me funciona el led de carga tampoco me va la función de silenciar el micrófono levantándolo y escondiéndolo y busco en la pagina de corsairs el firmware CORSAIRS VOID RGB ELITE WIRELESS para instalarlo manualmente y no lo encuentro podrían decirme donde esta o que debo hacer?
  14. Hola, acabo de comprar los carsair virtuoso se gunmetal y estuve durante 2 dias bien sin embargo en algun momento empezo a dar un fallo ya que los conectaba y despues de unos minutos chirreaba el sonido o no daba audio, estuve viendo y al parecer dicen que es por el firmware, tengo instalado icue 4 y el firmware de los audifonos son los siguientes Receptor v. 0.16.80 Audifonos v. 0.17.149
  15. Hace unos días estaba usando mi teclado con el sistema de icue y queria conectarlo a mi ps4, utilicé las teclas "bloq win + F1" Y ahora no me reconoce el teclado, al parecer es el firmware que está dañado, alguien podria ayudarme a conseguir el firmware de este modelo? El que he encontrado es el de k63 wireless y ese no me funciona .. ayuda urgente por favor¡
  16. since I updated the keyboard to the new firmware (3.29.32) the combination of keys wind lock key + f1 no longer works, it is consequently for me it is impossible to put the keyboard in bios mode, and therefore be able to use it on ps4. do you know how to solve?
  17. Hello, after updating the iCue Software to v.4.13.223 the Wireless Receiver got an update to v. 5.4.99 whichafter it stopped connecting to the Headset(v.0.17.149). The Headset itself is working perfectly fine while in wired mode and connected via the USB cable. When I connect the Receiver to any USB Port it flashes Red for a while. The iCue Software recognizes the Receiver and displays version number 5.4.99. The force update option for the Receiver is clickable but does not do anything. When I set the Receiver to Playstation mode "USB Wireless Receiver Pairing" is not clickable. If set to Multipoint then "USB Wireless Receiver Pairing" is also not clickable. The Option to Pair additional devices is Clickable and Prompts a new window to open which descripes where to best connect the Wireless Receiver to. Confirming that prompt closes that window after which nothing happens again. Re-Installing the iCue Software did not change anything. I already contacted Support 3 days ago, but got no response yet. I hope there is a way to resolve this issue.
  18. Hi all! Today iCue suggested a firmware update for me, and now my AIO is dead: FANs at full RPM, no RGB and iCue no longer recognize AIO. Have tried many things and no luck, changed USB port, restarted service and so on... :( Going to create a ticket now with support, but I would love to get some quick tips if someone have them... Cyberpunk 2077 is waiting. *cry* Many thanks!
  19. Hallo Corsair Community, ich bin seit ca. einem halben Jahr stolzer Besitzer einer Corsair K57 Wireless Tastatur. Leider habe ich seit letzter Woche das Problem das sich diese nicht mehr Aktualisieren lässt sowie sich nicht mehr mit dem K57 Dongle Koppeln lässt. Sobald die Aktualisierung startet geht die K57 aus und muss erst vom USB Kabel getrennt werden und dann Aus und wieder Ein geschalten werden damit sie wieder an geht. Ein Soft Reset und die Versuche diverser Foren Einträge haben auch nicht geholfen. Das ganze wurde auf 3 verschiedenen Systemen getestet, mit iCUE 3 und iCUE 4 (auch mit Clean Install) und mit verschiedenen USB Slots (USB 2.0 & USB 3.0) jedoch ohne Erfolg. Der Dongle wurde ohne Probleme aktualisiert. Derzeitige Versionen sind folgende: iCUE v4.9.350 (Aktuell) K57 Dongle v2.2.71 (Aktuell) K57 Tastatur v1.1.164 (Veraltet) ---> v2.2.71 (Neue Version) Ich denke das der Dongle und die Tastatur durch die Software Unterschiede nicht verbinden können. Kennt jemand das Problem oder hat einen Lösungsvorschlag? Ich habe bereits Anfang letzter Woche ein Support Ticket (2004197933) geschrieben jedoch noch keine Antwort erhalten. Grüße
  20. Hi Corsair As a Firmware Engineer I have just build a new Workstation with a Ryzen 5950x, Asus Rog Croshair VIII Hero motherboard. Using a Gentoo Linux, currently with kernel gentoo-sources 5.4.80 gives the following warning on boot. dec 24 12:46:28 nova kernel: nvme nvme0: missing or invalid SUBNQN field. dec 24 12:46:28 nova kernel: nvme nvme0: Shutdown timeout set to 10 seconds This issue with invalid SUBNQN field is a known issue in a number of NVMe units. If you look at the kernel code you will see that it has a dedicated quirk for it. See NVME_QUIRK_IGNORE_DEV_SUBNQN in https://github.com/torvalds/linux/blob/master/drivers/nvme/host/pci.c So my question is what is fixed in firmware 13 for the drive? Does it include the wrong SUBNQN field? I can't find a detailed changelog, preferable with info about for each commit done to the firmware codebase between the two releases. Second is the firmware files available somewhere or only the tool? Based on the input from others regarding the new firmware and performance I will be relectant to upgrade until I know if the issue about the SUBNQN is fixed. If anyone have an upgraded MP600 1TB, can you please boot a linux (just a bootable USB pen) and verify if you see the issue. Just use the journalctl -b
  21. What I was able to find (very old thread) was that the reason the "DIY" devices are not recognized or supported is an issue with the firmware on the Lighting Node Pro? Has this been resolved? Workarounds? ...am I missing something?
  22. I recently purchased the new CORSAIR SABRE RGB PRO CHAMPION SERIES mice. Everything was working perfectly and I thought it was good idea to download the iCUE software & update my firmware. After installing iCUE (v4.11.274) and pressing the firmware update button, windows instantly tells me the device malfunctioned and is no longer recognizable. So mice is not working, plugging it into any different usb port doesn't do anything. I followed the troubleshooting guide which told me to hold left+right click and unplug + plug in and this did not work either. But pressing down the tiny little hole while plugging in the mouse does open a storage device called "CRP_DISABLED". Inside of it exists a firmware.bin file. I'm guessing I need to replace this file? I can't find any resources or download archives to grab a newer firmware to manually update my device? Does anyone have access to the firmware here for this specific mouse or is there another way for me to fix my mouse?
  23. have a nice day i have a CDC RGB PRO SE. But icant install new fw on this dongle. How can i do. Thnx. my icue version 4.
  24. Greetings, I called into support because some of the lights on my Strafe RGB MK.2 were not showing the correct colors, but the keyboard was working otherwise. I tried holding esc and plugging it in a few times before reaching out but that seemed to do nothing - I did not see the keyboard flash as per the instructions nor did the colors change. Support provided me with firmware that I used to do a hard reset per their instruction. After replacing the firmware with the file from support, my keyboard no longer works at all. I can get to the CRP_DISABLED drive and the USB pass-through works, but nothing else. I replied to support via email but have not heard back in days. How long is the typical support response? If I don't hear from them soon I will try calling again but I don't want to start another ticket, per the support site instruction. Is there any way for me to recover the previous firmware or at least get the Strafe into a usable condition? Thanks. Edit: Called support. Apparently they sent me the wrong firmware. Once I got the correct file for my keyboard, it returned to its previous state. The lights still aren't working correctly but at least I can use it as before I changed out the firmware.
  25. I've already contacted customer support and have an open ticket (2004094175) who have told me that I should try reinstalling iCUE, but that didn't work. So I'd read that reflashing my H150i PRO RGB firmware might help with some disconnection issues I've been having, I click the "Update firmware" button in iCUE and wait for half an hour as the "Updating" button spins on the screen. Eventually I get frustrated with waiting and hit "Abort," true to the warning message that came along with clicking the "Abort" button when I restarted and logged back into Windows my H150i PRO RGB wasn't there. Since then I've tried: Uninstalling and reinstalling iCUE (didn't work) Shutting down my PC and clearing CMOS (didn't work) Attaching my H150i PRO RGB to a different USB (didn't work) Reflashing using a firmware I found on the Corsair forums (didn't work) The firmware I found on the Corsair forums was for the H150i PRO XT, and I've got the H150i PRO RGB, which may be why the manual flash didn't take. (I get an "Unhandled exception" warning when I try to use XmcBootloader.exe with the H150_Pro_XT_V1.1.31 firmware.) Customer support has told me that they DO NOT have firmware for the H150i PRO RGB, so I was hoping that maybe somebody here in the user forums might have an old copy of their firmware lying around? Or maybe some other good suggestions on how to un-brick my cooler? I don't have a backup cooler lying around, so an RMA is kind of the last resort for me. Anyway, thanks in advance for any help or suggestions you can offer!
×
×
  • Create New...