IE10 fails to install on HP laptop running Win 7 Ultimate 32 bit

dalchina · 07 Apr 2013

Hi,thanks, true, I 'won' a license for that, and then Bitdefender. However, real time protection from Advanced System Care has always been off. Basically it's redundant, and as I said before I think, I never used its registry cleaner so uninstalling it is no great loss.

Having thought about the SFC log, I decided to run the scan in Safe Mode. (attached)

The result is a whole lot simpler, and I think just points to winhelp32.exe if I have the file name right (to support old version help, which has to be added for recent Windows). Which begs the question as to why in normal mode it's now showing a lot more problems. That's nothing to do with ASC, as I had run that check and no problems (reported on the other forum I've mentioned above I think), and ASC was running then.

I could have a look for what's stopping the sfc scan now..

NoelDP · 07 Apr 2013

There are actually two affected files in the log.

Code:

 Line 2454: 2013-04-06 21:11:32, Info                  CSI    000001fd [SR] Repairing 2 components
 Line 2455: 2013-04-06 21:11:32, Info                  CSI    000001fe [SR] Beginning Verify and Repair transaction
 Line 2458: 2013-04-06 21:11:32, Info                  CSI    00000200 [SR] Cannot repair member file [l:32{16}]"winhlp32.exe.mui" of Microsoft-Windows-Winhstb.Resources, Version = 6.1.7600.16385, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
 Line 2461: 2013-04-06 21:11:32, Info                  CSI    00000202 [SR] Cannot repair member file [l:24{12}]"winhlp32.exe" of Microsoft-Windows-Winhstb, 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

The reason that the file is so much simpler is two-fold.
1) the system archived everything else first
2) there are no other services running which can actually do anything in the way of updating the system at the same time.

I'll post a fix protocol for these errors a bit later.