Homepage » DLL Q & A

How To Repair Corrupted .dll Files With SFC/Scannow

Download Now

Corrupted .dll Files

ANN SUCHOCKI asked on March 7, 2013. Status: Answered & Closed.

How To Repair Corrupted .dll Files With SFC/Scannow

» My copy of Windows started to crash/reboot itself. sfc /scannow reports that there are several .dll files that are corrupted and cannot be repaired. Also the notepad.exe program is listed as corrupted and cannot be repaired. I tried to fall back to the restore point but that failed.

Best Answer

» SFC/Scannow is one of the numerous command-line system tools that come on all current versions of Windows. It will scan all protected system files and replace incorrect or damaged versions with copies from a backup cache or from an installation disk or folder.

Malware infections(VirTool:Win32/CeeInject.gen!ID) are one source of this type of problem so make sure your system is clean before trying repairs. Also, System Restore is easier to use and should be tried first if possible.

Unfortunately, in Windows XP it is quite possible that SFC will first ask for your Windows installation disk. Most people only have a restore disk so it is necessary to take some rather involved steps before running SFC. Even if you have an installation disk, it probably won't work unless Service Pack 3 is on it.

Sometimes one of the important Windows system files can get corrupted. Then you may get messages about missing DLL files or have other indications that there is a problem. Dlls are files shared between a number of software programs (and are similar to .EXE files), used in Microsoft Windows and OS/2 operating systems.

The linkage may be damaged by some virus/Trojan thus leading a missing or abnormal dll error message. In this case, you need to run an antivirus/antimalware scan, and then, use DLL Suite to fix the associated problems by downloading and replacing the associated dll files.

KATHLEEN MASTERSON replied on March 13, 2013

All Answers:

  1. JEFFREY SCALF replied on March 7, 2013: » I would suggest you to follow the method and check. Method 1:Open the Windows Update troubleshooter

    See which Windows updates are installed

    Method 2:
    I would suggest you to follow the steps listed to repair the corrupted files found. How to use the System File Checker tool to troubleshoot missing or corrupted system files on Windows Vista or on Windows 7

  2. ANN SUCHOCKI replied on March 7, 2013: » If I add the old .dll files back into C:\Windows\System32 that I saved from the Ubuntu copy operation the sfc /scannow error remains. Windows 7 still seems to run OK, I can still install updates and other programs BUT now Visual Studio 2013 has sever problems and cannot create a new project, or even open an existing project.

  3. ROLAND RUCI replied on March 9, 2013: » If you have your installation DVD for Windows 7, you can try a Startup Repair. Startup Repair can only fix certain problems, such as missing or damaged system files. I would also make sure you have your data backed up.

  4. DAVID HUTTON replied on March 11, 2013: » The corrupt files are probably the replaced dlls via the patch that were done when u installed the 3rd party theme. If it aint part of the original windows, it will spew out your scannow as a corrupt system. Suggest you undo the theme and see if that fixes it.

  5. JOHN HEICK replied on March 12, 2013: » I had the same problem when I ran the scan I ran it to try and fix an issue with installing programs that use windows installer the scan did not work so I did a repair installation and it worked i ran the can no issues came up and i could install things he might need to do a repair installation!!! he did not take that long just select upgrade in installation options ans let it work its magic

DLL Q & A You Might Like:

  1. DLL Loading Error: Relap5l.dll »
  2. How To Change A Dll File Back To Normal »
  3. Ieframe.dll And Urlmon.dll To Be Fixed »
  4. Netio.sys Error Blue Screen Windows 7 Ultimate BSOD »
  5. Notification.Dll File Registration Problem »
  6. Unable to Load D3dx9_28.dll »
  7. Windows Shell Common DLL Failure »