Jump to content
Corsair Community

How I fixed the dreaded "Corsair Link .NET Framework error"!


noxcovenant

Recommended Posts

This solved the problem for me! This problem is 100% rooted in a corrupted registry. But keep in mind, it may take a few restarts for the problem to completely resolve for you. So don't get discouraged if this only partially fixes your problem after the first restart.

 

Step 1: Completely and utterly uninstall Corsair Link from your system (including Corsair Link Dongle and Hydro Series USB Device from the Control Panel). Also completely uninstall .Net Framework. Restart your system.

 

Step 2: Now, let's fix the corruption. Steps 2 through 5 are ripped directly from https://support.microsoft.com/en-us/kb/2305420 (under Known Issue 2). Go there now if you want the original format of these instructions. Anyway, let's locate the corrupted task references in the registry and in Task Scheduler

 

To do this, follow these steps:

 

  • Open Task Scheduler.
  • Expand Task Scheduler Library tree in the left pane, and located the folder that contains the corrupted task. Make a note of the location of the corrupted task. You will need this information later in this procedure.
  • Locate the registry sub-key that corresponds to the corrupted task in one of the following registry sub-key. You can locate the subkey by searching for the name of the task:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree
  • Click the registry sub-key that corresponds to the corrupted task, and then make a note of the GUID value in the "Id" entry. For example, {2911FBBD-A0AA-4A79-A8EE-84EF7555A71B}. You will need this information in the next step of this procedure.
  • Locate the registry sub-key that corresponds to the corrupted task in one of the following registry three sub-keys. To locate this sub-key, search for the GUID value that you noted in the previous step. For example, {2911FBBD-A0AA-4A79-A8EE-84EF7555A71B}. The task will exist in only one of the three locations:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain
  • Or:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Logon
  • Or:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Boot
  • Make a note of the registry location of the corrupted task. You will need this information later in this procedure.

 

Step 3: Create a temporary copy of the corrupted task file

 

  • To do this, follow these steps:
     
  • Open the following folder in Windows Explorer:
     
  • %SYSTEMDRIVE%\Windows\System32\Tasks\<Corrupted_Task_Name>
     
  • Locate and then copy the task file that corresponds to the corrupted task to a temporary location.

 

 

Step 4: Clean up the corrupted task

 

  • To do this, follow these steps:
     
  • Delete the task file that corresponds to the corrupted task from the Tasks folder (%SYSTEMDRIVE%\Windows\System32\Tasks).
  • Delete the registry sub-key that corresponds to the corrupted task from the following registry sub-key:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tree
  • Delete the registry sub-key that corresponds to the corrupted task from the following registry sub-key. The task will be in GUID format. For example, {2911FBBD-A0AA-4A79-A8EE-84EF7555A71B}.
     
  • Note Refer to the note that you made earlier in this procedure to locate the registry folder.
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Tasks
  • Delete the registry sub-key that corresponds to the corrupted task from one of the following registry three sub-keys. The task will exist in only one of the three locations and will be in GUID format. For example, {2911FBBD-A0AA-4A79-A8EE-84EF7555A71B}.
     
  • Note Refer to the note that you made earlier in this procedure to locate the registry folder.
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Plain
  • Or:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Logon
  • Or:
  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Schedule\TaskCache\Boot

 

Step 5: Re-create the task by using the temporary backed-up copy

 

  • To do this, follow these steps: To do this, follow these steps:
     
  • Open Task Scheduler.
  • Expand Task Scheduler Library tree in the left pane, and open the folder that previously contained the corrupted task.
     
  • Note Refer to the note that you made earlier in this procedure to locate the folder.
  • Right-click the folder that previously contained the corrupted task, and then click Import Task.
  • In the Open dialog box, select All files (*.*). Browse to the temporary folder that contains the backed up task file, and then select the task file. Click Open. The new task is created and is visible in Task Scheduler.

 

Step 6: Yay, we're done with the Microsoft instructions. Back to me now! Restart your computer. Reinstall Corsair Link. (I installed 3.2.5742 personally). During the install, it will automatically download and install Microsoft .Net Framework 4.5 beta. Let it do this. It may say ".Net Framework failed to install" at first, but just restart your computer and attempt the Corsair Link install again. Eventually it will successfully go through the process and install both programs (Corsair Link and .Net Framework).

 

Step 7: After Step 6, Restart your computer again! Corsair Link should now automatically start and appear on your taskbar (bottom-right). Double-click on the icon. Now read carefully. You may still get the .Net Framework error at this moment. HOWEVER, close Corsair Link and restart it. The error should not show up anymore.

 

Step 8: To completely resolve the problem, restart your computer again. The error should completely disappear even at the first boot now.

 

Hope it helped. I'm sure this won't solve everyone's problem, but at least it'll get some of your thought-processes jogging. Maybe I can even tweak these instructions and include pictures in the future.

Link to comment
Share on other sites

What Os version are you using and what are your system specs so we have a reference?

 

I'm using Windows 7 Ultimate.

 

It seems that as long as you fix the registry entry and let Windows start Corsair Link BY ITSELF (with the corrected entry), the error goes away.

 

But if I manually start Corsair Link myself (while it's never been turned on before), then the error returns.

 

These may not be hard rules, but I'm just trying to create a schematic for a potential comprehensive solution.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...