Jump to content
Corsair Community

Corsair Link 4.9.5.25 reinstallation fail


tuffalobuffalo
 Share

Recommended Posts

I recently put together a mostly new build with an EVGA Z370 FTW motherboard, an i7-8700K, an EVGA 1080 FTW, 16 GB Corsair Dominator DDR4 3200, and a Corsair H150i cooler as the main guts. The H150i and Corsair Link worked fine upon initial installation and I set it up after some tweaking (why are the fans not set to the CPU core temp by default???), but after a week or so, the LEDs on the pump heatsink stopped being set to the color I set it to, Corsair link didn't register any sensors, and my fan profiles were not working either.

 

So, today, I finally had time to try and fix it and couldn't figure out what the heck was going on after several reboots. I decided to uninstall and then reinstall Corsair Link to see if that would work because google wasn't giving me anything other than this form and nothing here was what I was experiencing.

 

This definitely feels like a Corsair LINK software issue. There were a number of weird things going on. When I went to uninstall in Windows, there were two versions showing as installed. 4.9.5.25 and 4.9.5.28. I was able to uninstall 4.9.5.25 and reboot, and then everything went back to the way it was. It all worked. The LED and fan settings were all how I'd set them. That said, it was all weird and didn't seem right at all. So, I decided to try and redo everything. I uninstalled 4.9.5.28, rebooted, and then tried to install 4.9.5.25. It errored out saying it was missing a CLink4Setup.msi file. At that point, I went and deleted every Corsair folder on my Windows 10 64 home installation. I used a registry to clear out any Corsair or Clink4 registries, and now I get an "Installation failed. Error code 0x80070643." message trying to install Corsair Link 4. I have no idea what to do short of reinstalling Windows 10 which is something I haven't had to do since the 90s for something like this happening. This is kinda ridiculous.

 

A screen capture of the error message is attached for what it's worth. I'm at a loss as to how to proceed other than give up and chuck everything out the window.

Capture.PNG.62821ab4a7274e4d34b144934e270b5f.PNG

Link to comment
Share on other sites

Error 80070643 is, unfortunately, something of a generic error. If you google "msi error 80070643", you'll come up with a bit of information. Unfortunately, there's no one solution.

 

Does Windows show any of the versions still installed? It's likely that you may have completely nerfed something when going through and clearing out registry entries. This may have included registry entries for the driver.

 

I would also encourage you to look at the cooler FAQ. It covers problems with EVGA tools (such as XOC) as well as why you don't want the cooler fan speed set to CPU temp. It's linked in my signature.

Link to comment
Share on other sites

Yeah, there are no versions still installed and everything I can find of Corsair's software-wise is uninstalled. How do I get a driver reinstalled for this thing then? I've tried unplugging the USB cord out of the H150i, rebooting, shutting down, plugging it in, and then booting and that did nothing.

 

Is there any way to do a driver reinstallation that's unrelated to the Corsair Link 4 software? I'll have a look at the cooler faq because of the EVGA incompatibilities. I'm not sure why you would want to link the fans to whatever sensor they set by default. It didn't change at all when CPU temps went up and caused huge overheating problems. I was a little flabbergasted.

 

Edit: Checking that faq on linking to the coolant temp versus the CPU Core temp absolutely wouldn't make sense given what happened to me. The coolant temp on the default sensor would stay at like 30 while the CPU core temp would spike to 60 or something, so the fans would never even kick in. I don't know if I have a faulty H150i, but linking the fans to the CPU Core temp sensors definitely solved the temp problems. My 3 fans are all connected to the cooler controller.

Edited by tuffalobuffalo
Link to comment
Share on other sites

Well, unfortunately, I don't know what to tell you about the installation error. Like I said, it's a generic MSI error. I would suggest that you dig in the Windows Event Logs to see if you can find something that is a bit more descriptive of the actual problem that is occurring. With the information that we currently have, there's nowhere near enough information to understand what's going on.

 

As for your "overheating problem" ... tying the fans to the CPU core temperature completely ignores the actual physics involved with liquid cooling. The coolant is not going to increase in temperature very quickly because it has a significantly higher heat capacity than air or the CPU cores. And a jump to 60 or something with a Skylake or later CPU is normal and is in no way even close to overheating.

Link to comment
Share on other sites

Well, unfortunately, I don't know what to tell you about the installation error. Like I said, it's a generic MSI error. I would suggest that you dig in the Windows Event Logs to see if you can find something that is a bit more descriptive of the actual problem that is occurring. With the information that we currently have, there's nowhere near enough information to understand what's going on.

 

As for your "overheating problem" ... tying the fans to the CPU core temperature completely ignores the actual physics involved with liquid cooling. The coolant is not going to increase in temperature very quickly because it has a significantly higher heat capacity than air or the CPU cores. And a jump to 60 or something with a Skylake or later CPU is normal and is in no way even close to overheating.

 

Well, I guess I'm at the point of doing a complete Windows reinstallation due to some Corsair software's bug. I'm stunned. Any chance it'd be more wise to wait a month or two for a software update that fixes this issue? I've used Corsair products for so, so many years. I've always read people complaining about the software problems of Corsair software but kinda shrugged it off since I didn't buy many software dependent products.

 

What you're saying makes some sense on CPU cooling, but my temperature sensor for the liquid cooling fluid did not reflect what was going on with the actual CPU temps at all even over long term periods. I don't think making the critical part you're worried about with heat heating up a heat sensor that senses fluid flowing through a system makes any sense to monitor. Given that modern systems in typical use fluctuate between idle and high power, I'd much rather have a reactive system than a constant fan system.

Link to comment
Share on other sites

So, I get this info in the Windows Event Viewer when trying to install Corsair Link 4:

 

Product: Corsair LINK 4 -- Error 1714. The older version of Corsair LINK 4 cannot be removed. Contact your technical support group. System Error 1612.

 

Under details it says this:

 

+ System

 

- Provider

 

[ Name] MsiInstaller

 

- EventID 11714

 

[ Qualifiers] 0

 

Level 2

 

Task 0

 

Keywords 0x80000000000000

 

- TimeCreated

 

[ SystemTime] 2018-03-12T23:37:07.451048100Z

 

EventRecordID 5499

 

Channel Application

 

Computer FERDINAND

 

- Security

 

[ UserID] S-1-5-21-1144172786-3731184374-2921546724-1001

 

 

- EventData

 

Product: Corsair LINK 4 -- Error 1714. The older version of Corsair LINK 4 cannot be removed. Contact your technical support group. System Error 1612.

(NULL)

(NULL)

(NULL)

(NULL)

(NULL)

 

7B41373636313642462D434236422D343744442D423343352D4241453644463345414430467D

 

 

--------------------------------------------------------------------------------

 

Binary data:

 

 

In Words

 

0000: 3637417B 42363136 42432D46 342D4236

0010: 2D444437 35433342 4541422D 33464436

0020: 30444145 7D46

 

 

In Bytes

 

0000: 7B 41 37 36 36 31 36 42 {A76616B

0008: 46 2D 43 42 36 42 2D 34 F-CB6B-4

0010: 37 44 44 2D 42 33 43 35 7DD-B3C5

0018: 2D 42 41 45 36 44 46 33 -BAE6DF3

0020: 45 41 44 30 46 7D EAD0F}

Link to comment
Share on other sites

One thing that I'm finding odd in the events is related to this CLink4Setup.msi file. When I'm looking through the event log, it still is trying and failing to go to that MSI file.

 

This is what the event viewer says (Source is MsiInstaller)

Beginning a Windows Installer transaction: C:\ProgramData\Package Cache\{A76616BF-CB6B-47DD-B3C5-BAE6DF3EAD0F}v4.9.5.25\CLink4Setup.msi. Client Process Id: 11772.

 

After the install fails, I go to that location, and there isn't a folder there. There is one folder in Package Cache that's Corsair related and running the installer will put it there. It has the Corsair USBXpDriver files in it. I renamed it and ran the installer and it just puts it right back there.

Link to comment
Share on other sites

Right. Windows Installer is trying to uninstall a version that it thinks is there but isn't. That's why it's failing. Now, you can copy the correct file to that location or you can clean up the MSI entries so that Windows Installer doesn't try to uninstall them.

I do have that file; PM me and I can put it on a OneDrive drop for you. But you'd probably be better off cleaning up the entries.

Link to comment
Share on other sites

OK ... this shouldn't require a reinstall of Windows. You just need to clean up the installation.

Start with this: https://support.microsoft.com/en-us/help/17588/fix-problems-that-block-programs-from-being-installed-or-removed.

 

Thanks!

 

Okay, I gave that a shot. Nothing shows up related to Corsair when going the install troubleshooter or the uninstall troubleshooter. I tried the "Not Listed" option and that was a no go. Next step?

Link to comment
Share on other sites

Right. Windows Installer is trying to uninstall a version that it thinks is there but isn't. That's why it's failing. Now, you can copy the correct file to that location or you can clean up the MSI entries so that Windows Installer doesn't try to uninstall them.

I do have that file; PM me and I can put it on a OneDrive drop for you. But you'd probably be better off cleaning up the entries.

 

Okay, I'll PM you for the file. If I can get the installer to work at that point, would it be worthwhile trying to uninstall using the troubleshooter and then start fresh with the Corsair Link installer?

Link to comment
Share on other sites

I'd just place the file and try to run as before. I'm making an educated guess here dude ... personally, I've never had a lick of issues with installing.

 

Well, my problem seems to have arisen from Link stopping to work and then my usual uninstall/reinstall method of troubleshooting seems to have not been a good plan.

 

So, I'm still not able to get the install to work. I can actually just run the MSI and it quits partway through saying that it cannot remove the previous version of Corsair Link. I tried hunting through the registry for clink4 and corsair an

 

Is there anything else I can clean off Windows so it doesn't keep thinking Corsair Link is still installed? Are there any other registry searches I can do?

 

I found another thing unrelated to this software regarding MSI file installation problems. They recommended using msiexec and writing the output to a log file which I did now that I actually have the CLink4Setup.msi.

 

msiexec /i "C:\ProgramData\Package Cache\{A76616BF-CB6B-47DD-B3C5-BAE6DF3EAD0F}v4.9.5.25\CLink4Setup.msi" /l*v C:\Users\Username\Desktop\corsairlinkinstall.log

 

I'm not seeing any info in that log file that's giving me any clues as to what's going wrong. There's a lot of info there, though. It's attached to this post.

corsairlinkinstall.log

Link to comment
Share on other sites

Here's the issue:

Action start 17:33:05: RemoveExistingProducts.

RemoveExistingProducts: Application: {62BE14B0-C98C-47AC-8E02-E27402AADB82}, Command line: UPGRADINGPRODUCTCODE={A76616BF-CB6B-47DD-B3C5-BAE6DF3EAD0F} CLIENTPROCESSID=11868 CLIENTUILEVEL=0 REMOVE=ALL

MSI (s) (40:40) [17:33:05:814]: Resetting cached policy values

MSI (s) (40:40) [17:33:05:814]: Machine policy value 'Debug' is 0

MSI (s) (40:40) [17:33:05:814]: ******* RunEngine:

******* Product: {62BE14B0-C98C-47AC-8E02-E27402AADB82}

******* Action:

******* CommandLine: **********

MSI (s) (40:40) [17:33:05:815]: Warning: Local cached package 'C:\Windows\Installer\35276.msi' is missing.

MSI (s) (40:40) [17:33:05:816]: User policy value 'SearchOrder' is 'nmu'

MSI (s) (40:40) [17:33:05:816]: User policy value 'DisableMedia' is 0

MSI (s) (40:40) [17:33:05:816]: Machine policy value 'AllowLockdownMedia' is 1

MSI (s) (40:40) [17:33:05:816]: SOURCEMGMT: Looking for sourcelist for product {62BE14B0-C98C-47AC-8E02-E27402AADB82}

MSI (s) (40:40) [17:33:05:816]: SOURCEMGMT: Adding {62BE14B0-C98C-47AC-8E02-E27402AADB82}; to potential sourcelist list (pcode;disk;relpath).

MSI (s) (40:40) [17:33:05:816]: SOURCEMGMT: Now checking product {62BE14B0-C98C-47AC-8E02-E27402AADB82}

MSI (s) (40:40) [17:33:05:816]: Note: 1: 2718 2: {62BE14B0-C98C-47AC-8E02-E27402AADB82}

MSI (s) (40:40) [17:33:05:816]: SOURCEMGMT: Failed to resolve source

CustomAction returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)

MSI (s) (40:50) [17:33:05:817]: Note: 1: 1714 2: Corsair LINK 4 3: 1612

Error 1714. The older version of Corsair LINK 4 cannot be removed. Contact your technical support group. System Error 1612.

MSI (s) (40:50) [17:33:07:869]: Product: Corsair LINK 4 -- Error 1714. The older version of Corsair LINK 4 cannot be removed. Contact your technical support group. System Error 1612.

It's trying to uninstall yet another previous version.

This may help ... or something similar: https://stackoverflow.com/questions/4069431/how-to-manually-remove-msi-installation

Link to comment
Share on other sites

Thanks, DevBiker, yeah, that's what I found and then was able to use the uninstaller to get rid of it. When Link stopped working properly, and I originally went to uninstall it, there were two versions showing up as programs on my system to uninstall. 4.9.5.25 and 4.9.5.28. So, I think maybe I was pushed a bad update that killed something. I don't see an update available now when I'm on 4.9.5.25. Maybe it was pulled due to issues? Uninstalling went all weird and led me to posting here. Whatever 4.9.5.28 was, that messed something up.
Link to comment
Share on other sites

I can't say that I know where 5.28 came from. I'm running 5.25. The previous version (which is actually on my laptop for testing devices) is 4.28. On my daily systems, I typically keep pretty up to date with Link releases.

 

But ... you're sorted now?

Link to comment
Share on other sites

I can't say that I know where 5.28 came from. I'm running 5.25. The previous version (which is actually on my laptop for testing devices) is 4.28. On my daily systems, I typically keep pretty up to date with Link releases.

 

But ... you're sorted now?

 

Yeah, it must have been 4.9.4.28. But yeah, all sorted.

Link to comment
Share on other sites

 Share

×
×
  • Create New...