The Corsair User Forums

The Corsair User Forums (https://forum.corsair.com/forums/index.php)
-   Corsair Link (https://forum.corsair.com/forums/forumdisplay.php?f=209)
-   -   Corsair USBXp Driver? (https://forum.corsair.com/forums/showthread.php?t=169312)

Gr0u 07-20-2017 03:58 AM

Corsair USBXp Driver?
 
Hello.
I had to format my computer yesterday. After installing drivers for my motherboard (Asus Tuf z270 mark 1), I installed Intel (R) Chipset Software Installation Utility driver V10.1.1.38
Intel (R) Chipset Software Installation Utility V10.1.1.38 for Windows 7 32-bit & 64-bit, Windows 8.1 64-bit, Windows 10 64-bit (WHQL), after installing this driver started asking me Install a Driver (Corsair USBxp Driver)


However in the program available corsair (corsair link) when opening the program, it does not recognize that I have installed on my computer HydroSeries H115i

https://www.dropbox.com/s/s73r21ciwi...creen.png?dl=0

Gr0u 07-20-2017 04:39 AM

Quote:

Originally Posted by Gr0u (Post 912534)
Hello.
I had to format my computer yesterday. After installing drivers for my motherboard (Asus Tuf z270 mark 1), I installed Intel (R) Chipset Software Installation Utility driver V10.1.1.38
Intel (R) Chipset Software Installation Utility V10.1.1.38 for Windows 7 32-bit & 64-bit, Windows 8.1 64-bit, Windows 10 64-bit (WHQL), after installing this driver started asking me Install a Driver (Corsair USBxp Driver)


However in the program available corsair (corsair link) when opening the program, it does not recognize that I have installed on my computer HydroSeries H115i

https://www.dropbox.com/s/s73r21ciwi...creen.png?dl=0



"Windows can not verify the digital signature for the drivers required for this device. A recent hardware or software change may have installed a file that is improperly or damagedly signed, or may constitute malicious software from an unknown source. (Code 52)"

Breene 07-20-2017 11:00 AM

I am having the exact same problem with an h100i v2 - it worked fine on the PC for a few months. i installed windows 10 (fresh, not upgrade) and have the same problem as you with an asus z170 pro mobo.

link does not see the cooler, in device manager there is the same driver errors.

I'm going to repost this to the cooler section of the forum too

Gr0u 07-20-2017 11:06 AM

Quote:

Originally Posted by Breene (Post 912585)
I am having the exact same problem with an h100i v2 - it worked fine on the PC for a few months. i installed windows 10 (fresh, not upgrade) and have the same problem as you with an asus z170 pro mobo.

link does not see the cooler, in device manager there is the same driver errors.

I'm going to repost this to the cooler section of the forum too

Hello Breene.


Today I reported this problem to asus technical support. Unfortunately they did not give me any solution, they asked me to contact Corsair Support.

Maybe the problem is the new Corsair Link


https://www.dropbox.com/s/zfyssxed49...08.23.png?dl=0

Gr0u 07-20-2017 11:38 AM

Quote:

Originally Posted by red-ray (Post 912594)
The issue is with the signing of the Corsair USBxp Driver and only Corsair can fix this.

You could try the drivers I attached to http://forum.corsair.com/forums/showthread.php?p=856104

I re-install the old version and it's fine.
Maybe i wait for Corsair fix this issue, then i update the new version.

red-ray 07-20-2017 11:52 AM

The issue is with the signing of the Corsair USBxp Driver
 
The issue is with the signing of the Corsair USBxp Driver and only Corsair can fix this.

The old driver package was OK, so you could try the copy of those drivers I attached to http://forum.corsair.com/forums/showthread.php?p=856104 which is the same driver, but with a different .INF file.

Once the old driver package is installed CL 4.8.0.82 should report Asetek coolers.

Gr0u 07-20-2017 12:01 PM

Quote:

Originally Posted by red-ray (Post 912596)
The issue is with the signing of the Corsair USBxp Driver and only Corsair can fix this.

The old driver package was OK, so you could try the copy of those drivers I attached to http://forum.corsair.com/forums/showthread.php?p=856104 which is the same driver, but with a different .INF file.

Once the old driver package is installed CL 4.8.0.82 should report Asetek coolers.

https://www.dropbox.com/s/fjelhykqgy...59.46.png?dl=0 The old Version

Sorry for repost, but i try install the new version....and it's good for me :p

https://www.dropbox.com/s/x82ytnsryq...06.12.png?dl=0

Gr0u 07-20-2017 12:18 PM

https://www.dropbox.com/s/gjl5qdvx8b...14.02.png?dl=0

First install the version V4.8.0.82 and then unnistall
Second i install the version V4.2.4.25, now i make the update for the version V4.8.0.82 and fine for me :p

gotriceeclipse 07-20-2017 06:40 PM

I had the same issue with the driver error (52 i believe) in windows 10 64bit, and the link4 software not detecting my h100i gtx at all. after uninstalling and reinstalling and searching for a while i finally came across an answer as well on these forums to uninstall v4.8.0.82 and then i also completely removed/uninstalled the driver as well, then installed v4.7.0.77, which I had on it before the update it just did. Back to working perfectly again! No driver errors or anything! I'm glad too because a lot of the other forums I read, people were suggesting to RMA it.. ain't nobody got time for that!
If the prior links don't work for the download, you an just google that version and it will show up on a few sites. If anything, you can probably find a newer version.. just gonna stick with this one for now :biggrin:

AndyBlak 07-21-2017 02:56 AM

Quote:

Originally Posted by red-ray (Post 912596)
The issue is with the signing of the Corsair USBxp Driver and only Corsair can fix this.

The old driver package was OK, so you could try the copy of those drivers I attached to http://forum.corsair.com/forums/showthread.php?p=856104 which is the same driver, but with a different .INF file.

Once the old driver package is installed CL 4.8.0.82 should report Asetek coolers.


Thanks a ton, Ray! This fixed my problem. H100i is showing up in CL4 as normal, again.

harrynyce 07-26-2017 09:23 PM

Same issue: Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)
This potentially occurred either during the Creator's Update process, or when i upgraded to the newest version of Corsair Link. So many problems with this software, although it had gotten slightly better.
Windows 10 Pro 64-bit
Corsair H100i v2
Corsair Link 4.8.0.82

I didn't even notice it until today when i plugged in my new Corsair STRAFE keyboard and went to install the Corsair Utility Engine and now some of the USB devices that i try to plug in generate other errors.

linxeye 07-31-2017 01:23 PM

Exact same issue here with 4.8 CL release. Are they planning on an official fix or something ? Like maybe something more recent than a 7 years old driver ?

jinseidon 08-05-2017 10:04 AM

C'mon Corsair do you not test updates before you release it?


I had this exact same issue, I had no idea why my fans were a lot louder than usual so after looking into it, opening CL4 and my h115i now showing up started to annoy me, after multiple installs/unistalls and restarts. I decided to install an older version, I had version v4.7.0.77 still in my downloads, installed it and now it works like a charm.

ctudor 08-06-2017 07:05 AM

Hi, I had the same ploblem and my solution was to clear the secure boot keys. I have Asus Z270G and is located in BIOS > "Secure Boot" > "Key Management" and select "Clear Secure Boot keys" it worked for me.

YhuggyBear 08-06-2017 02:31 PM

Same boat as OP z170 asus hero alpha. Same error code 52. Its killing mee :(


All times are GMT -4. The time now is 01:06 AM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.