Solved MSHTML.DLL corrupt dunno how to fix it.

[FloPPyPiLLoW]

I cannot use IE. It simply will not open. When I open it without add ons it will open but when I try to leave the blank page it crashes and leaves "view downloads" open. And any program that uses IE causes a massive amount of errors saying "C:\Windows\system32\mshtml.dll is either not designed to run on Windows or contains an error. Try installing the program again using the original installation media or contact your system administrator or the software vendor for support." However I can't re-install IE because it won't let me install it while it's already installed and it won't let me uninstall because when I go to programs and features>manage updates and right click on IE11 to uninstall it comes up saying "An error has occurred. Not all of the updates were successfully uninstalled." I also tried taking mshtml.dll from my fiance's computer and pasting it over mine but it says I don't have permission (even though I am administrator). This seems like some sort of cruel joke. Catch 22 everywhere. HALP

 

[NoelDP]

Let's start with this...

Please follow the Windows Update Posting Instructions and post the requested data
If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

 

[FloPPyPiLLoW]

I think I have the information that you need. I ran the SFC which failed and tried to follow the instructions but I cannot for the life of me find my windows disk so I couldn't do the extracting files thingy from the disk.

 

[NoelDP]

SFC didn't fail - it just didn't manage to fix things it found but was never designed to fix

2014-06-26 13:27:39, Info                  CSI    0000067a [SR] Repairing 6 components
2014-06-26 13:27:39, Info                  CSI    0000067b [SR] Beginning Verify and Repair transaction
2014-06-26 13:27:39, Info                  CSI    0000067e [SR] Cannot verify component files for Microsoft-Windows-IE-HTMLEditing, Version = 11.2.9600.17107, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2014-06-26 13:27:39, Info                  CSI    00000681 [SR] Cannot verify component files for Microsoft-Windows-IE-HTMLRendering, Version = 11.2.9600.17107, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2014-06-26 13:27:39, Info                  CSI    00000684 [SR] Cannot verify component files for Microsoft-Windows-IE-VersionInfo, Version = 11.2.9600.17107, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2014-06-26 13:27:39, Info                  CSI    00000687 [SR] Cannot verify component files for Microsoft-Windows-IE-HTMLEditing, Version = 11.2.9600.17107, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2014-06-26 13:27:39, Info                  CSI    0000068a [SR] Cannot verify component files for Microsoft-Windows-IE-HTMLRendering, Version = 11.2.9600.17107, pA = PROCESSOR_ARCHITECTURE_IA32_ON_WIN64 (10), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2014-06-26 13:27:39, Info                  CSI    0000068d [SR] Cannot verify component files for Microsoft-Windows-IE-VersionInfo, Version = 11.2.9600.17107, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)

CheckSUR, on the other hand, gives us more data...

Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.2.9600.17107_none_f5b8ad88372109c7.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_11.2.9600.17107_none_000d57da6b81cbc2.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-versioninfo_31bf3856ad364e35_11.2.9600.17107_none_e19b7a1549f1ad7a.manifest
 winsxs\manifests\x86_microsoft-windows-ie-versioninfo_31bf3856ad364e35_11.2.9600.17107_none_857cde9191943c44.manifest
 winsxs\manifests\amd64_microsoft-windows-ie-htmlediting_31bf3856ad364e35_11.2.9600.17107_none_2a9e8453585c539f.manifest
 winsxs\manifests\wow64_microsoft-windows-ie-htmlediting_31bf3856ad364e35_11.2.9600.17107_none_34f32ea58cbd159a.manifest
 servicing\packages\Package_1_for_KB2953522~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_1_for_KB2953522~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_for_KB2953522_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_for_KB2953522_RTM~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_for_KB2953522~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_for_KB2953522~31bf3856ad364e35~amd64~~11.2.1.0.mum
 servicing\packages\Package_1_for_KB2953522~31bf3856ad364e35~amd64~~11.2.1.0.cat
 servicing\packages\Package_1_for_KB2953522~31bf3856ad364e35~amd64~~11.2.1.0.cat
 servicing\packages\Package_for_KB2953522_RTM~31bf3856ad364e35~amd64~~11.2.1.0.cat
 servicing\packages\Package_for_KB2953522_RTM~31bf3856ad364e35~amd64~~11.2.1.0.cat
 servicing\packages\Package_for_KB2953522~31bf3856ad364e35~amd64~~11.2.1.0.cat
 servicing\packages\Package_for_KB2953522~31bf3856ad364e35~amd64~~11.2.1.0.cat

...none of these files are anywhere except in Windows Updates -
I'll post a fix protocol for them a bit later - I'll have to trawl a little for them, I think!

 

[NoelDP]

OK - I think I got a little lucky


I've uploaded a file - fpwaa.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 fpwaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And 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.

 

[FloPPyPiLLoW]

I think I might have compressed more files than needed but i'm sure you'll figure it out xD

 

[NoelDP]

Hmm - nothing happened...
...which usually means that either you or I cocked up somewhere...

Did you run CheckSUR - or SFC?
I ask because the CheckSUR log is dated 26th at 12:54
Please check that you didn't upload the wrong files (it's the same size as yesterday's upload as well

 

[FloPPyPiLLoW]

I ran something it definately wasn't SFC... I think it was checksur but lemme redo it and i'll reupload it.

 

[FloPPyPiLLoW]

It's this thing I am supposed to be doing right? Download System Update Readiness Tool for Windows 7 for x64-based Systems (KB947821) [May 2014] from Official Microsoft Download Center

 

[NoelDP]

Don't forget you have to copy it to the desktop again! (although the CheckSUR log is small enough to upload direct from the source location).

 

[NoelDP]

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

 

[FloPPyPiLLoW]

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

 

[NoelDP]

A definite improvement!

here's all that's left for us to deal with...

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.

 

[NoelDP]

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.

 

[FloPPyPiLLoW]

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)

 

[NoelDP]

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

SORRY - it was my fault!

back in a jiffy!

 

[NoelDP]

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.

 

[FloPPyPiLLoW]

Do I get rid of the incorrect ones?

 

[NoelDP]

No - the system will just ignore them anyhow

 

[FloPPyPiLLoW]

Okay here it is with the new logs