Best IT Recipes

The clr.dll version does not match the one that mscordacwks.dll was created for

I have a C # console application in Visual Studio 2010 that I can execute just fine. When I try to start the process in debug mode, I get the following error:

clr.dll version doesn't match mscordacwks.dll

I tried to find any information, but I could not find anything. Can anyone make it clear why I cannot run this using the debugger?

EDIT: I have to clarify that earlier I was able to successfully debug the console application, this is a new situation.

+80
visual studio
Apr 24 2018-11-11T00:
source share
10 answers

From what I can say, when I can reproduce this error, it is caused by the fact that we are in the middle of installing Windows updates. So, starting updates, delaying the reboot, and then trying to debug the code is what put me in this broken state.

+164
May 29 '11 at 1:44
source share

I had this problem once, and it was caused by a pending Windows update on the server where the process I would like to add was running.

+5
Nov 26 '12 at 8:23
source share

I finally decided it!

This seemed to happen after I upgraded my Windows 7. One of my files must be out of date.

Fix: Install VS 2010 Service Pack 1 (SP1)

Worked right immediately after installation. Attacking breakpoints and that’s it!

Hope this works for you too!

+3
Apr 29 2018-11-11T00:
source share

I also updated Service Pack 1 and made sure Windows updates were updated, but I still had a problem:

"The version of CLR.dll in the target does not match the one for which the mscordacwks.dll file was created."

Microsoft has closed this problem on connect.microsoft.com as not reproducible ... Unforgivable, irresponsible support system!

But on social.msdn.com I was asked to update through this link , and this solved the problem on my machine (Win7, VS2010, target 4.0)

Hope this helps.

+3
Jul 25 2018-11-11T00:
source share

I ran into the same problem. This happened to me when I tried to connect to the process for debugging. At that time, I delayed a deferred Windows update.

After I restarted my computer and allowed it to be updated, everything began to work fine.

Additional notes. I recently upgraded to Visual Studio 2010 Ultimate and installed its Service Pack 1.

+3
Dec 18 '13 at 15:45
source share

I had this when I installed .NET 4.6 for Visual Studio 2013.

In this particular case, restarting Visual Studio 2013 solved the problem.

+2
Aug 17 '15 at 12:44
source share

This happens when you perform WINDOWS UPDATE and do not restart your system, and the update is not compatible with VISUAL STUDIO. Therefore, to solve this problem, simply update the VISUAL STUDIO information to the latest version. That should fix it

+1
Jul 15 '13 at 20:25
source share

I had this strange problem after installing .NET Framework 4.5 when using .net 4 for my project. updating the VS 2010 service pack did not solve this, only uninstalling .net 4.5 and 4, and then reinstalling only .net 4.

+1
Aug 22 '13 at 12:02
source share

I had VS 2010 Service Pack 1 (SP1), and it rebooted many times. There were no windows updates. I closed all my 2010 IDS IDs and then opened them and the problem disappeared.

0
May 23 '12 at 19:12
source share

Simply. Rebooting Visual Studio solved the problem in my case.

0
Nov 16 '17 at 10:33
source share


More articles:


All Articles