TheWatcher7Z1 Posted October 15, 2021 Share Posted October 15, 2021 Keep getting this message on Windows 11 Home Insider Preview (see attachment for details on build version). Using iCUE version 3.38.61. Let me know if you have any suggestions, Kind Regards, 1 Link to comment Share on other sites More sharing options...
Doondoons Posted October 16, 2021 Share Posted October 16, 2021 Same issue for me Pro version of win 11 updated yesterday to 22478.1012 which is when it broke (also on insider build) but i am using the latest icue 4 build Link to comment Share on other sites More sharing options...
istehwin Posted October 16, 2021 Share Posted October 16, 2021 same issue 22478.1012 (Windows Feature Experience Pack 1000.22478.1012.0) Link to comment Share on other sites More sharing options...
Niko76 Posted October 17, 2021 Share Posted October 17, 2021 I was having same. I deleted asus aura sync and armoury crate and corsair icue program. Then re- installed all of them and link to armoury crate tool too ( from corsair page ) Link to comment Share on other sites More sharing options...
iMaximusrex Posted October 17, 2021 Share Posted October 17, 2021 I am not getting the error message, maybe because it is still able to monitor temps from my CPU/GPU, but I am not able to see any of my other hardware, Keyboard, RAM, Fans, Pump. CPU and GPU Waterblocks. I was able to use Signal RGB to at least get my keyboard LEDs semi-functional. I am also on Windows 11 Insider Dev Build. Link to comment Share on other sites More sharing options...
dpesulima Posted October 18, 2021 Share Posted October 18, 2021 from what i gathered from the other forum post, the latest dev channel build breaks iCUE. I reverted back to the stable channel and iCUE works again. Testing the beta channel at the moment... Link to comment Share on other sites More sharing options...
c-attack Posted October 18, 2021 Share Posted October 18, 2021 The BETA channel 22000.282 works fine as have all prior beta channel releases. This highlights the problems with running Developer channel builds. You are getting it at the same time they are. Link to comment Share on other sites More sharing options...
74lobster Posted October 18, 2021 Share Posted October 18, 2021 (edited) Windows 11 dev. build 22478.1012 broke completely the functionality of iCUE ver. 4.16.194 program. iCUE doesn't recognize anymore all the Corsair peripherals that I have installed, like K95 RGB Platinum keyboard, H150i ELITE CAPELLIX and the Commander PRO. I hope that Corsair will update the iCUE program soon... Edited October 18, 2021 by 74lobster Link to comment Share on other sites More sharing options...
Tracer900Junkie Posted October 19, 2021 Share Posted October 19, 2021 I have tried multiple versions of ICUE on my system (also insider build Win 11 latest version).. and none of them recognize keyboard, mouse or lighting controller (K70RGB, Nightsword RGB, Lighting Node Pro) having to use the Windows MOUSE function to control pointer speed, and it is not pretty, lol! Link to comment Share on other sites More sharing options...
phgen03 Posted October 20, 2021 Share Posted October 20, 2021 I'm on the latest version of dev and the solution that works for me is to disable Secure Boot from the BIOS. Hope this help. Link to comment Share on other sites More sharing options...
Valer1y Posted October 23, 2021 Share Posted October 23, 2021 Hi! One year ago and today My keyboard k70 was not found by the program. English not my language sorry Link to comment Share on other sites More sharing options...
Djsquidguts Posted October 23, 2021 Share Posted October 23, 2021 macos 11.6 apple m1 chipset CORSAIR iCUE macOS v3.38.61 off to a bad start for a 200 plus dollar keyboard k70 mk2 What is the issue ? Link to comment Share on other sites More sharing options...
c-attack Posted October 23, 2021 Share Posted October 23, 2021 This thread was about a specific issue on one of the Windows 11 Developer Release Builds and a device initialization problem unique to it. If you are having device recognition problems on anything other than Build 22478.1012, make sure you post in a new thread so you can be seen and get help. The underlying cause is going to be different. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now