MSVCR120_CLR0400.dll

Anonymous
2017-06-20T08:53:52+00:00

After doing a windows update getting the below error message while logging in .

"The procedure entry point nextafterf could not be located in the dynamic link library MSVCR120_CLR0400.dll"

what does it mean and how we can resolve it and now I notice that the Skype for business search is not finding anything as well .

OS -WIN 7 Pro 64 bit SP1

***Post moved by the moderator to the appropriate forum category.***

Windows for home | Previous Windows versions | Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
Anonymous
2017-07-04T10:54:27+00:00

An IT specialist had to sort the issue for me. It turns out it was something to do with the microsoft .net framework 4.7 update that windows installed. He reverted back to version 4. I'm not sure if he had to do anything else to restore the system but it works fine now. He has just advised me not to install that update.

Was this answer helpful?

100+ people found this answer helpful.
0 comments No comments
Answer accepted by question author
Anonymous
2017-06-22T21:08:28+00:00

There are not "several causes" of the error message.

There is one cause of the error message.

Here is what is means:

Search your system for MSVCR120_CLR0400.dll and when you find it check the Properties like this example:

What is the version on your system?

Whatever the version is, write it down and then come back and tell us what it is.

The files get installed with the C++ 2013 Redistributable package and is not part of a Windows installation so it is doubtful sfc  /scannow will help you.

Inside these DLLs are functions and the programs that are complaining are telling you that they are not finding the nextafterf function inside the MSVCR120_CLR0400.dll but as you can see on my system with my installed version of the file it is in there:

Apparently your MSVCR120_CLR0400.dll is afflicted, the wrong version or something else is not right about it.

But as usual we know nothing about your environment...  are you a home user, a corporate user connected to a corporate network or something else?  Maybe there is a reason you have that version of MSVCR120_CLR0400.dll on your system.

First make a System Restore point so in case things get worse you can undo the changes.

If you are a home user you can check your Control Panel, Installed Programs, find the C++ 2013 and uninstall it:

After uninstalling restart your system and if there are more errors that are DIFFERENT, post them too.

Then download and install (in your case) the 64 bit version from this link:

https://www.microsoft.com/en-us/download/details.aspx?id=40784

Then restart your system and check the version of the file again.

If it still doesn't work, tell us the original version you wrote down, and the version you just installed.

In your example error SelfService.exe (and Skype) are not Windows programs so it could be that there is something wrong with them too.

Was this answer helpful?

80+ people found this answer helpful.
0 comments No comments

65 additional answers

Sort by: Oldest
  1. Anonymous
    2019-08-08T17:34:22+00:00

    Hello Antoine! 

    Rolling back to .Net 4.70 is not an option as our new software requires 4.7.2. However we found a fix by uninstalling KB4488669, installing .Net 4.72, applying patch KB4488666, and replacing Msvcp120_clr0400.dll version 12.0.52523.36523 with Msvcp120_clr0400.dll version 12.0.52519.0  in both SYS32 and SYSWOW64 folders on 64bit machines. This is a known issue caused by an update, notes can be found here https://support.microsoft.com/en-us/help/4488669/description-of-the-update-for-net-framework#known and https://support.microsoft.com/en-us/help/4488666/description-of-the-update-for-net-framework.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2019-08-08T17:45:38+00:00

    Hello Taklit!

    What appears to be happening is KB4488669 deletes over 300 functions in the MSVCR120_CLR0400.dll including nextafterf. You can fix this one of two ways, downgrade your .Net, or replace the MSVCR120_CLR0400.dll with version 12.0.52519.0. Version 12.0.52519.0 restores all 1900 functions of the .DLL . We found this by using .DLL exporter and comparing known good and bad PCs. The corrupt version of msvcr120_clr0400.dll is 12.0.52523.36523 when you check the details tab. You will need to replace sys32 and syswow64 versions of this file with known good ones with 12.0.52519.0 being the preferred. If you can get the known good files on a sever I've included a script listed below. If you need to upgrade your .net use either 4.8 or 4.7.2 with patch kb4488666 applied. You still might need to update the MSVCR120_CLR0400.dll files. 

    REM Remove bad security patch

    wusa /uninstall /kb:4488669 /quiet /norestart

    REM Remove corrupted DLL files from KB4488669 patch.

    mkdir C:\New_32bit

    mkdir C:\New_64bit

    move "C:\Windows\System32\msvcr120_clr0400.dll" "C:\New_32bit"

    move "C:\Windows\SysWOW64\msvcr120_clr0400.dll" "C:\New_64bit"

    REM Replace file location with known good DLL from network share and clean up temp location

    copy /Y "\ Microsoft.Net.4.7.2\32bit msvcr120_clr0400.dll\msvcr120_clr0400.dll" "C:\Windows\System32"

    copy /Y  "\ Microsoft.Net.4.7.2\64bit msvcr120_clr0400.dll\msvcr120_clr0400.dll" "C:\Windows\SysWOW64"

    REM Delete old DLL files from temporary locations.

    Del "C:\New_32bit"

    Del "C:\New_64bit"

    REM Install .NET 4.7.2

    NDP472-KB4054530-x86-x64-AllOS-ENU.exe /q /norestart 

    ndp46-kb4488666-x64_62d08d7c700253b0c4d46a3bed952c246c98122f.exe /q /norestart

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2019-08-08T19:45:21+00:00

    Try upgrading your .net to version 4.8, and or replacing MSVCR120_CLR0400.dll with version 12.0.52519.0 in both sys32 and syswow64 folders.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments