Internet Explorer Crashes on Startup - Other Corruptions

[Benevolence]

Hello. We imaged a client's failing hard drive onto a new drive. We are trying to salvage the OS without doing an in place install. Currently IExplore crashes on startup with infinite crash report windows. Additionally running SFC shows corrupted files, but is unable to repair them. I am hoping to replace the damaged files from ones extracted from the repair media, but am having a difficult time identifying the exact files from the CBS logs. Do these member files seem like they would be causing these issues? I should add that we've taken a few steps to restoring functionality, like reinstalling IE11, removing startup items, starting

CSI 00000339 [SR] Beginning Verify and Repair transaction

CSI 0000033b [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

CSI 0000033d [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

CSI 0000033f [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

CSI 00000340 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"

CSI 00000342 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-06-19 10:23:05, Info

CSI 00000343 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2015-06-19 10:23:05, Info

CSI 00000346 [SR] Repair complete

 

[BigBadBeef]

Failing hard drive usually comes with data damage. When the damage reaches a point to where an inexperienced person such as your client would notice the problems, considerable data loss is already present. I'm afraid the only viable solution is salvaging whatever data remains intact, moving it to a portable drive and then wiping everything and starting again.

 

[Benevolence]

While this is always an option, I would prefer to try something else. We have a company stigma against crashing an OS, in-place installs etc...

 

[Benevolence]

After finding more information about the SFC components, I do not believe they were involved in the IE error. While we tried downgrading to IE10 with no success, downgrading to IE9 actually did work. We were able to upgrade back up to 11 from 9, and everything appears to be working correctly.

Beef, it is bad practice to use a reinstall as a go-to to fix specific components. Your approach is like saying "the kitchen sink is broken" - "Start by tearing the whole house down and rebuild everything". For many clients, especially the many legal and medical clients we work with, it is worth spending several hours troubleshooting an issue, than to have to rebuild an OS plus all of the security settings, vpns, programs etc...

 

[BigBadBeef]

No, what I'm saying more is more like: "The house is ridden with termites, exterminator can kill the termites, but he can't plug the holes the mites have chewed up"!