Share via

Repair corrupted system files from install media

Anonymous
2016-01-13T21:03:09+00:00

A number of system files on my 64-bit windows 7 machine are corrupted e.g. wbemdisp.dll. sfc /scannow is unable to fix these. I have also tried Startup Repair with the original media on DVD but this didn't help. I don't have a restore-point image, so am trying to replace the files from the original DVD following the procedure recommended here http://www.pcworld.com/article/243190/how\_to\_repair\_a\_corrupt\_windows\_7\_installation.html which effectively involves using the original install media to 'upgrade' the PC. However, I come across a problem since when the installation script runs a compatibility check is says I am running a newer version of Windows and it can't upgrade. The disks are for Windows 7 64 bit and the computer is running Windows 7 64 bit so how do I get around this? Presumably there is some newer service pack that the original media doesn't contain which is why it thinks the disks contain an older version. I'm trying to avoid having to do a clean install as the os still largely works and I don't want to have to reinstall all my software, lose settings etc. but the corrupted files have broken enough programmes that I would like to fix them.

Windows for home | Previous Windows versions | Performance and system failures

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

5 answers

Sort by: Most helpful
  1. Anonymous
    2016-01-14T11:30:05+00:00

    Hello,

    Thank you for posting your query on Microsoft Community.

    With the issue description, I understand that there are corruptions in system files on Windows 7 operating system. I will certainly help you in getting this fixed.

    I appreciate your effort towards resolving the issue.

    Let’s follow below mentioned steps and check if that helps:

    Method 1: Run SFC Scan from command prompt in Windows Recovery Environment using Windows 7 disk

    You may follow the steps provided in below mentioned Microsoft articles to boot the machine using disk and open Windows recovery environment on the machine. I would like to inform you that running sfc scan in Windows Recovery Environment using Windows 7 disk may repair/replace the corrupt system files.

    http://windows.microsoft.com/en-in/windows/startup-repair-faq#1TC=windows-7

    What are the system recovery options in Windows?

    http://windows.microsoft.com/en-us/windows/what-are-system-recovery-options#what-are-system-recovery-options=windows-7

    Boot the computer using Windows 7 disk. After opening Windows Recovery Environment, you may follow below steps:

    1. Click on “Command Prompt
    2. Type the following command

    sfc scannow (press enter)

    Try method 2, if the issue persist

    Method 2 : Run DISM tooland check the issue. Please follow these steps:

    1. Press “Windows key” and type “Command prompt” in search box.
    2. Right click “command prompt” and click on “Run as administrator”
    3. Type the following command in command prompt and press Enter.

    DISM.exe /Online /Cleanup-image /Scanhealth. (Press Enter)

    DISM.exe /Online /Cleanup-image /Restorehealth. (Press Enter)

    To close the Administrator: Command Prompt window, type Exit, and then press Enter.

    Note: The tool might take 15-20 minutes to finish running, so please do not cancel it.

    Hope this information is helpful. Please write back to us if you need any further assistance, we'll be glad to assist you.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  2. Anonymous
    2016-01-21T15:09:56+00:00

    That sounds like the right track - installation media does not match installed SP but shouldn't one be able to download installation media that has SP1 included just in case there is a problem in the future?  Just curious...

    My installation media from a few years ago is plain with no SP but I downloaded an ISO from MS with SP1 included and have used it many times (for practice only of course) and it works just fine (even though it is OEM and I'm not supposed to be able to download OEM media):

    Still works today - just download another OEM SP1 ISO:

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  3. Anonymous
    2016-01-14T15:47:09+00:00

    Thanks for your response - I hadn't considered trying sfc /scannow from the DVD. I tried the various suggestions in your message with the following outcomes:

    1. sfc /scannow

      I get the following

    "Beginning system scan. This process will take some time

    There is a system repair pending which requires reboot to complete. Restart Windows and run sfc again."

    At this stage I wasn't sure whether to rerun sfc from the startup repair command prompt or directly in windows? I tried again from the CD and got the same message so then I did this in an Administrator command prompt on Windows. This ran but the CBS.log file still has many errors e.g.

    "2016-01-14 14:25:53, Info CSI 0000038a [SR] Verify complete 2016-01-14 14:25:54, Info CSI 0000038b [SR] Verifying 100 (0x0000000000000064) components 2016-01-14 14:25:54, Info CSI 0000038c [SR] Beginning Verify and Repair transaction 2016-01-14 14:25:56, Info CSI 0000038d Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-wmi-scripting_31bf3856ad364e35_6.1.7600.16385_none_60e78eba5410cd9e\wbemdisp.dll do not match actual file [l:24{12}]"wbemdisp.dll" :

     Found: {l:32 b:vl9w2Zz/zR3zybQLxrbSnZUg47Q1qTc4V0Udv7u0ftg=} Expected: {l:32 b:hkTQpVxGw/CB8KtD0lPRPlbnfYkzaocQjbjEfW7cOmQ=} 2016-01-14 14:25:56, Info CSI 0000038e [SR] Cannot repair member file [l:24{12}]"wbemdisp.dll" of Microsoft-Windows-WMI-Scripting, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2016-01-14 14:25:57, Info CSI 0000038f Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-wmi-scripting_31bf3856ad364e35_6.1.7600.16385_none_60e78eba5410cd9e\wbemdisp.dll do not match actual file [l:24{12}]"wbemdisp.dll" :

     Found: {l:32 b:vl9w2Zz/zR3zybQLxrbSnZUg47Q1qTc4V0Udv7u0ftg=} Expected: {l:32 b:hkTQpVxGw/CB8KtD0lPRPlbnfYkzaocQjbjEfW7cOmQ=} 2016-01-14 14:25:57, Info CSI 00000390 [SR] Cannot repair member file [l:24{12}]"wbemdisp.dll" of Microsoft-Windows-WMI-Scripting, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch 2016-01-14 14:25:57, Info CSI 00000391 [SR] This component was referenced by [l:202{101}]"Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.WindowsFoundationDelivery" 2016-01-14 14:25:57, Info CSI 00000392 Hashes for file member ??\C:\Windows\SysWOW64\wbem\wbemdisp.dll do not match actual file [l:24{12}]"wbemdisp.dll" :

     Found: {l:32 b:vl9w2Zz/zR3zybQLxrbSnZUg47Q1qTc4V0Udv7u0ftg=} Expected: {l:32 b:hkTQpVxGw/CB8KtD0lPRPlbnfYkzaocQjbjEfW7cOmQ=} 2016-01-14 14:25:57, Info CSI 00000393 Hashes for file member \SystemRoot\WinSxS\x86_microsoft-windows-wmi-scripting_31bf3856ad364e35_6.1.7600.16385_none_60e78eba5410cd9e\wbemdisp.dll do not match actual file [l:24{12}]"wbemdisp.dll" :

     Found: {l:32 b:vl9w2Zz/zR3zybQLxrbSnZUg47Q1qTc4V0Udv7u0ftg=} Expected: {l:32 b:hkTQpVxGw/CB8KtD0lPRPlbnfYkzaocQjbjEfW7cOmQ=} 2016-01-14 14:25:57, Info CSI 00000394 [SR] Could not reproject corrupted file [ml:58{29},l:56{28}]"??\C:\Windows\SysWOW64\wbem"[l:24{12}]"wbemdisp.dll"; source file in store is also corrupted "

    1. I ran DISM.exe /Online /Cleanup-image /Scanhealth

    The output from this shows a number of errors:

    "Summary:

    Seconds executed: 889

    Found 9 errors

     CheckSUR Registry Failure Total count: 1

     CSI Manifest Failed Catalog Check Total count: 4

     CBS MUM Corrupt Total count: 3

     CBS Catalog Corrupt Total count: 1

    Unavailable repair files:

             winsxs\manifests\amd64_6da8ff6d9860e7896741f7e8706f8ab1_31bf3856ad364e35_11.2.9600.17041_none_8533fcec1ecb6dcb.manifest

             winsxs\manifests\amd64_e6b1511c3edf6eb70f2db938173c8636_31bf3856ad364e35_11.2.9600.17041_none_7879e277ff200848.manifest

             winsxs\manifests\amd64_fae088ee990409cb9975d902d294b62c_31bf3856ad364e35_11.2.9600.17041_none_6b96240a992ce896.manifest

             winsxs\manifests\amd64_8078519738a275dcf189976b0aada9d0_31bf3856ad364e35_11.2.9600.17041_none_b32e68c79d9f39d9.manifest

             servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum

             servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum

             servicing\packages\Package_37_for_KB2929437~31bf3856ad364e35~amd64~~11.2.1.0.mum

             servicing\packages\Package_for_KB2929437_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum

             servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat

             servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat

             servicing\packages\Package_37_for_KB2929437~31bf3856ad364e35~amd64~~11.2.1.0.cat

             servicing\packages\Package_for_KB2929437_RTM~31bf3856ad364e35~amd64~~11.2.1.0.cat "

    1. I tried running DISM.exe /Online /Cleanup-image /Restorehealth

    This starts to run, then I get the following:

    "Error: 87

    The restorehealth. option is no recognized in this context.

    For more information, refer to the help.

    The DISM log file can be found at C:\Windows\Logs\DISM\dism.log"I'm not sure what to try now! Thanks for your help.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2016-01-21T12:31:24+00:00

    A number of system files on my 64-bit windows 7 machine are corrupted e.g. wbemdisp.dll. sfc /scannow is unable to fix these. I have also tried Startup Repair with the original media on DVD but this didn't help. I don't have a restore-point image, so am trying to replace the files from the original DVD following the procedure recommended here http://www.pcworld.com/article/243190/how\_to\_repair\_a\_corrupt\_windows\_7\_installation.html which effectively involves using the original install media to 'upgrade' the PC. However, I come across a problem since when the installation script runs a compatibility check is says **I am running a newer version of Windows and it can't upgrade.**The disks are for Windows 7 64 bit and the computer is running Windows 7 64 bit so how do I get around this? Presumably there is some newer service pack that the original media doesn't contain which is why it thinks the disks contain an older version. I'm trying to avoid having to do a clean install as the os still largely works and I don't want to have to reinstall all my software, lose settings etc. but the corrupted files have broken enough programmes that I would like to fix them.

    Hi,

    You normally get that message when the installed Windows 7 has Service Pack 1 installed; whereas the Windows 7 Media you are using for a Repair Upgrade Install does not have SP1 on it.

    How to check if Service Pack 1 is installed:

    http://windows.microsoft.com/en-us/windows7/install-windows-7-service-pack-1

    "To learn if Windows 7 SP1 is already installed

    • Click the Start button , right-click Computer, and then click Properties. If Service Pack 1 is listed under Windows edition, SP1 is already installed on your computer."

    If that is the case > remove SP1 > do the Repair Upgrade Install > reinstall SP1.

    "How to uninstall Windows 7 Service Pack 1 (SP1)"

    http://windows.microsoft.com/en-AU/windows7/uninstall-sp1

    _________________________________________________

    Here is another Tutorial about Repair Upgrade Installs which may interest you.

    http://www.sevenforums.com/tutorials/3413-repair-install.html

    ________________________________________________

    I see you have already tried a Startup Repair.]

    That only fixes files associated with startup problems; not all your system files.

    You are doing it the correct way with a Repair upgrade install.

    _________________________________________________

    As you have the original DVD which you used for Startup Repair (Retail License?), this may also interest you:

    How to Extract Files from the Windows 7 Installation DVD

    Cheers.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2016-01-21T10:46:49+00:00

    Hi,

    If issue still persists try to perform Startup repair and see if it helps you to repair the corrupted files. For performing startup repair you may refer to the article mentioned below and see if it helps.

    **Startup Repair: frequently asked questions**

    Do keep us updated.

    Regards,

    Was this answer helpful?

    0 comments No comments