explorer.exe - Entry Point Not Found

[Blossom37]

My computer is self-assembled. CPU: Intel i5. OS is Windows 7 Pro, SP1, 64-bit. Hard drive has a capacity of 1 TB and RAM is 8 GB.

When I right click a folder icon on the desktop or in Windows Explorer, the menu comes up correctly. When I right click a file icon, I receive the following error message:

explorer.exe - Entry Point Not Found

The procedure entry point
?in@?Scodecvt@DDHstd@@QEBAHAEAHPE6DlAEAPEBDPEAD3AEA
PEAD@Z could not be located in the dynamic link library MSVCP110.dll.

OK

Once I click “OK” the menu comes up normally.

I have done the following actions in an attempt to correct the problem:

• Checked for explorer.exe in C:\windows – it was there.
• Check the Registry, “WinLogon” for explorer.exe – it was there.
• Ran the Windows 7 DVD “Repair My Computer" – no change
• Restored the computer to a date in January 2015-no change
• Ran “Memory Diagnostics” – no discrepancies
• Ran “scf /scannow – no change

Can you tell me what is causing this problem and how to correct it?

 

[Boozad]

Reinstall Visual C++

Link

If that doesn't work try this one.

Link

 

[Blossom37]

Thanks for the reply.

I downloaded vcredist x64.exe and ran it. I received this error message; “A newer version of Microsoft visual C++ 2010 Redistributable has been detected on the machine.” I uninstalled MS VC++ 2010 x64 Redistributable 10.0.40219. This time vcredist x64 installed, but I still had the “explorer.exe – Entry Point Not Found” error after the installation. I ran vcredist x64 again and it asked to Repair VC++ x64. I said OK but afterwards I continued to get the “Entry Point Not Found” error message.

Have I missed something or do you have any additional directions?

 

[Layback Bear]

Give this tutorial by Brink a try. Can't hurt but might help.

http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[Blossom37]

I ran sfc /scannow three times. Each time I got "Windows Resource Protection did not find any integrity violations."

One thing I noted was the error message did not show up as Administrator, but once I switched back to my personal long on, the error showed up again