K95 Platinum not working with Windows Insider Version 17133

Hi!

I am a Windows Insider in the fast ring and tried updating from 17128.1 to 17133.1 now 3 times but always the same: This new Windows build broke the Corsair K95 Platinum Keyboard. It is not lighting up at all, it is not detected in iCue and it is shown as a unknown HID in the device Manager in Windows with a yellow warning sign.

Rolling back to 17128.1 Always solved the issue and the K95P is working again.

 

I dont actually know if its a windows issue or a iCue or a hardware issue but 17133.1 is supposed to be the next Windows version Spring Creators Update (RTM version) so this issue cant be rolled over to the public and needs investigation from Corsair and Microsoft so I post this here.

Yes, beside installing the Insider version 3 times I also tried reinstalling iCue but the K95 is still dead.

Its even dead when the pc boots so iCue isnt even loaded, just like the USB device is not registered at all by the pc. The lighting of the Keyboard just lights up for 3 seconds directly after I pressed the power button to turn on the pc, then all Corsair stuff goes blank, Windows tries to load all USB devices again and the K95P is dead at that point.

All other usb devices are working fine (including Glaive RGB, MM800C and other USB devices). Its just the K95P which is dead.. I became a Windows Insider just lately with Build 17115 on the 9th March to get a first glimpse whats new in the new Win 10 Update and never got any issues with Corsair gear in all the published builds but 17133 is very likely the RTM build for the Spring Creators Update and I think this issue needs to get resolved before it hits all users in mid April.. :/

Might be a driver issue because i'm also in 17133.1 but with a K70 lux rgb and all is working well.

BUT :) i was with CUE when Windows updated itself. I installed iCue after.

 

I remember i had some same issues using my Steelseries apex m800, at each software update, the lock keys didnt want to light on/off, they were always on. To get it to work well i was forced to uninstall the device in HID Devices (in device manager) and then Windows was reinstalling itself the good driver.

Did you reproduced the issue?

I gave the Spring Creators Update Insider Build 17133.73 /which is most likely THE final build) another chance today but still have the issue which makes it completely impossible to actually use Windows 10 1803 Spring Creators Update.

If this gets released to the public I think Corsair has a BIG problem.

 

Here you can find a video which shows the exact moment where the K95P looses connection during the installation process. It happens at 43% of the install of the 17133 update.

 

[ame]https://www.youtube.com/watch?v=z7qVtyUAHH0[/ame]

 

You can see the K95P goes black and does not recover. MM800 and Glaive are still lighting.

 

And here you can see what happens when my PC boots:

 

[ame]https://www.youtube.com/watch?v=jCdwo1_rhkc[/ame]

 

As you can see at first directly after pressing the power-on button the K95P lights up together with the MM800 and Glaive. Then all devices go black. But when the windows logo appears, the USB devices get another boot and only the MM800 and Glaive are lighting up again - the K95P stucks black and is completely dead.

 

This is what the device manager shows:

 

https://1drv.ms/u/s!AmpzWY6tGIepgrMwkltOGvo3htSAZw

 

https://1drv.ms/u/s!AmpzWY6tGIepgrMxKM_OXLFQv-MD5g

 

The keyboard is listed 3 times as a unknown device and in the properties page there is a error code 28 which is in conflict with the ASMedia USB Host it seems.

 

Please get in contact with Microsoft before they roll out the SCU in the next days... There is NO problem with the previous Insider Build 17128 so I dont know what they did with 17133 but the K95P is dead.

I Google this error code 28 which I get in the device manager and it says that this error code happens when no driver was installed for that device.

So during the installation of 17133 the driver was not installed. Is there a way to install the device driver manually? When I try the automatic search no driver was found.. And iCUE does also not install the driver...

Anything from Corsair related to this?

K95 Platinum is still not usable with today's latest Insider 17134!!!!!!!

Please Corsair, get in contact with Microsoft ASAP. This needs to get resolved before 1803 will be released as that update would crash thousands of keyboards!!!

K95 Platinum is still not usable with today's latest Insider 17134!!!!!!!

Please Corsair, get in contact with Microsoft ASAP. This needs to get resolved before 1803 will be released as that update would crash thousands of keyboards!!!

 

Hi momorious,

If I may get n on this discussion. Where does one go to find this “17134”....and what type of driver is it ? Point me n the direction to go and I’ll check mine.

 

I had a blank board issue that was resolved, and I may be able to help. I bought my board about a month ago. Had some issues, and now it’s solved. Sounds similar to mine.

 

I won’t bore you with my problem until. Find out what that 17134 is, and where do I find out mine.

Hope I can help

Hi momorious,

If I may get n on this discussion. Where does one go to find this “17134”....and what type of driver is it ? Point me n the direction to go and I’ll check mine.

 

I had a blank board issue that was resolved, and I may be able to help. I bought my board about a month ago. Had some issues, and now it’s solved. Sounds similar to mine.

 

I won’t bore you with my problem until. Find out what that 17134 is, and where do I find out mine.

Hope I can help

 

17134 is the Windows Insider version in the fast ring, most likely to become RTM build for Windows 10 1804 Spring Creators Update.

I am on 17134 using K95P without issue (now). It is a laugh, but what I found was after the update, somehow the keyboard brightness (little snowflake button) was set to off of the 4 possible positions. I was unplugging and replugging the keyboard, doing hard and soft resets to it, ect. to no avail. I decided to just hit the brightness button for the hell of it and lo-and-behold, there were my lights once again. XD

I am on 17134 using K95P without issue (now). It is a laugh, but what I found was after the update, somehow the keyboard brightness (little snowflake button) was set to off of the 4 possible positions. I was unplugging and replugging the keyboard, doing hard and soft resets to it, ect. to no avail. I decided to just hit the brightness button for the hell of it and lo-and-behold, there were my lights once again. XD

 

Unfortunately thats not the issue I have. The keyboard is dead with the latest Insider build. Without the virtual keyboard I wouldnt even be able to login and reset back to the old 17128...

OK, let us see what we can do... Let's start basic.

 

Have you tested the keyboard in different usb 3.0+ ports?

 

Have you tested a different device in the port you are plugging the keyboard into to verify that that port is functioning correctly?

 

If you are using ASUS's ASMedia 3.1 ports, have you checked for an ASMedia driver update?

 

Tried to uninstall and reinstall the ASMedia drivers?

 

Have you hard reset the keyboard Plug it into the usb port while holding the [esc] key)?

 

Have you disconnected all other USB devices and tried ONLY the keyboard, just to see if we are having assignment issues?

 

Try these minor things and let me know. You and I have very similar base equipment (just a generation off) so maybe we can comparatively troubleshoot the issue.