MSHTML.DLL corrupt dunno how to fix it.

Page 2 of 3 FirstFirst 123 LastLast

  1. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #11

    ...yep - that's the one. You can use the one you already downloaded assuming you haven't deleted it.
      My Computer


  2. Posts : 24
    Ontario
    Thread Starter
       #12

    Okay these log files are dated today. but it didn't make new cab files so I didn't bother putting them in there.
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #13

    A definite improvement! :)

    here's all that's left for us to deal with...
    Code:
    Unavailable repair files:
     winsxs\manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.2.9600.17107_none_000d57da6b81cbc2.manifest
     winsxs\manifests\x86_microsoft-windows-ie-versioninfo_31bf3856ad364e35_11.2.9600.17107_none_857cde9191943c44.manifest
     winsxs\manifests\wow64_microsoft-windows-ie-htmlediting_31bf3856ad364e35_11.2.9600.17107_none_34f32ea58cbd159a.manifest
    I'll post a new fix for them later.
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #14

    Hmmm - it looks as if you mi-copied the manifest files - either putting them in the wrong folder, or copying the folder across, rather than jus the files.

    Please repeat his part of the above (from post #5)...

    open the folder fpwaa that you extracted earlier.
    there should be two folders inside it (Manifests, and Packages)

    Copy the content of the manifests folder (.manifest files) into this folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

    Now run the CheckSUR tool again (it may take a while)

    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.
      My Computer


  5. Posts : 24
    Ontario
    Thread Starter
       #15

    Well the manifests were in the folder when I went to do it again but I did it again anyways and ran checksur and here are the logs (I checked to make sure they were made just now)
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #16

    strange - still not fixed....
    lemme check my end...
    OoopS!

    SORRY - it was my fault!

    back in a jiffy!
      My Computer


  7. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #17

    I've uploaded a file - fpwab.zip - to my OneDrive at Noel's OneDrive
    Please download and save it.
    Right-click on the downloaded file, and select Extract all…
    Extract to the default location - which will create a new folder fpwab in the same place.
    Open this folder - there should be one folders inside it (Manifests,)

    Copy the content of the manifests folder (.manifest files) into this folder:

    C:\Windows\Temp\CheckSur\Winsxs\Manifests

    Now run the CheckSUR tool again (it may take a while)

    Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

    With any luck that should do it now!

    Assuming it does, run another SFC /SCANNOW and post the new CBS.log file so we can see if it's scared anything out of the bushes.
      My Computer


  8. Posts : 24
    Ontario
    Thread Starter
       #18

    Do I get rid of the incorrect ones?
      My Computer


  9. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #19

    No - the system will just ignore them anyhow :)
      My Computer


  10. Posts : 24
    Ontario
    Thread Starter
       #20

    Okay here it is with the new logs
      My Computer


 
Page 2 of 3 FirstFirst 123 LastLast

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 13:20.
Find Us