Jump to content
Corsair Community

Corsair USBXp Driver?


Gr0u

Recommended Posts

Hello.

I had to format my computer yesterday. After installing drivers for my motherboard (Asus Tuf z270 mark 1), I installed Intel ® Chipset Software Installation Utility driver V10.1.1.38

Intel ® 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/s73r21ciwiyk48d/screen.png?dl=0

Link to comment
Share on other sites

  • Replies 99
  • Created
  • Last Reply

Top Posters In This Topic

Hello.

I had to format my computer yesterday. After installing drivers for my motherboard (Asus Tuf z270 mark 1), I installed Intel ® Chipset Software Installation Utility driver V10.1.1.38

Intel ® 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/s73r21ciwiyk48d/screen.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)"

Link to comment
Share on other sites

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

Link to comment
Share on other sites

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/zfyssxed49e140e/Screenshot%202017-07-20%2016.08.23.png?dl=0

Edited by Gr0u
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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/fjelhykqgyv0k11/Screenshot%202017-07-20%2016.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/x82ytnsryqxegq0/Screenshot%202017-07-20%2017.06.12.png?dl=0

Edited by Gr0u
Link to comment
Share on other sites

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:

Link to comment
Share on other sites

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.

  • Like 1
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

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.

Link to comment
Share on other sites

I had the same problem with my H115i and by reading on forums the solution Corsair support gives you is to disable the driver signature enforcement in Windows. It's a security feature in Windows that allows only digitally signed drivers to function but it's more a pain in the butt than it actually helps.

It's a very easy procedure and it will work afterwards, I followed this guide:

[ame]

[/ame]
Link to comment
Share on other sites

It's a security feature in Windows that allows only digitally signed drivers to function but it's more a pain in the butt than it actually helps.

 

It's there to stop viruses loading unsigned kernel drivers and disabling it is the wrong solution.

 

The correct solution is for Corsair to correctly sign their driver and until they do I recommend using the correctly signed Corsair drivers I attached to:

  1. http://forum.corsair.com/forums/showthread.php?p=856104 (coolers).
  2. http://forum.corsair.com/forums/showthread.php?p=888388 (AXi PSUs).

Edited by red-ray
Add link
Link to comment
Share on other sites

  • 2 weeks later...
Users having these issues, are you also running any of ASUS's software? If so, which software are you running?

 

Hello.

 

I have two Corsair products with this very same "signature" issue.

 

AX1500i and H115i

 

I happen to have an Asus Motherboard (Rampage V Edition 10) (without having Asus AI Suite installed by the way)

 

And an Asus Strix 1080 Ti OC with the Asus Tweak II 1.4376 software installed.

 

All on Windows 10 64 bit build 1703 fully updated.

 

 

 

I had to install the "old" drivers linked in previous posts in order to be able to see the PSU and the Cooling in corsair Link V 4.8.2.1 otherwise they just wouldn't show up in Link, and appeared with an error in device manager.

Edited by Catalonia
Link to comment
Share on other sites

Hi there i have H80i v2 and asus z270f. In the device manager i see it as Corsair USBxp Driver. Before Ausu suit was installed in my pc but later i uninstall it from control panel. As i read in asus forum i need to unisntall it with asus cleaner but that program is not working anymore.

202431578_devicemanager.png.f0e23af0e5347694c300721bf836c309.png

2006325545_devicemanager1.png.1cedf5b751cb3edafd324e217a172cdf.png

553044094_devicemanager2.png.aee675efc96097f47d5ce7f3e8d4a463.png

1948494179_devicemanager3.png.f2749f47bc10f51f9e7690e367db6ea8.png

88746299_devicemanager4.png.1c02975e5c8df53c8b5bdb167aa128b8.png

Link to comment
Share on other sites

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.

 

Dude you’re a boss!

 

I’ve been looking all night for a fix.

I noticed my pump was running at full speed all the time but everything else was running normal speed.

I tried everything that was on other topics.

Until i sa this topic.

After a simple remove, download your drivers and then manually find of drivers corsair link finally finds my h115i.

And my windows also now says "Corsair Hydro Series 7289 USB Device"

 

Big thx m8

 

PS: DO NOT disable the driver signature enforcement, it’s there for a reason.

it’s to make sure viruses can't just install without a prompt of microsoft verification.

So plz be careful and safe in what you disable before it’s to late.

Edited by Toendy
  • Like 1
Link to comment
Share on other sites


×
×
  • Create New...