Cannot Install ie10 (9c59)

[mikeyjames]

Hi all,

This is my first time so I hope I get it right. Can't install ie10 on my Win 7 64 bit system. Thought I would just wait until ie11 but can't get that to install either - only from standalone installer but error seems pretty much the same. anyway, here is my error screenshot from ie10 on Windows Update:

View attachment 292874


Also, I had to get rid of a couple of the CBSPersist.cab files before I zipped the folder, otherwise the resulting zip file was too big to upload.

Any help much appreciated

Thanks

Mick

View attachment 292875

 

[NoelDP]

CheckSUR only found the one error...

Checking Component Store
(f) CSI Payload File Corrupt 0x00000000 wdscore.dll amd64_microsoft-windows-servicingstack_31bf3856ad364e35_6.1.7601.17592_none_672ce6c3de2cb17f 
Summary:
Seconds executed: 355
 Found 1 errors
  CSI Payload File Corrupt Total count: 1

the SFC scan found this...

 Line 105353: 2013-11-08 21:59:23, Info                  CSI    0000063d [SR] Repairing 1 components
 Line 105354: 2013-11-08 21:59:23, Info                  CSI    0000063e [SR] Beginning Verify and Repair transaction
 Line 105357: 2013-11-08 21:59:23, Info                  CSI    00000640 [SR] Cannot repair member file [l:22{11}]"wdscore.dll" of Microsoft-Windows-ServicingStack, Version = 6.1.7601.17592, 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

... which is the same problem

There are a number of errors in the background CBE.log data - but we'll have to hope that they will be corrected by repairing the errant file..

back later with a fix protocol.

 

[mikeyjames]

CheckSUR only found the one error...

There are a number of errors in the background CBE.log data - but we'll have to hope that they will be corrected by repairing the errant file..

back later with a fix protocol.

Thanks for that, I appreciate it.

 

[NoelDP]

I've uploaded a file - mjsaa.zip - to my SkyDrive at Noel's SkyDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print theseinstructions!)
Now reboot to the Repair Environment - as soon as the machine restarts, starttapping F8 - this should bring up the Advanced Boot Menu, at the top of whichshould be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\mjsaa
hit the enter key - if you get a 'NotFound' error try
DIR D:\mjsaa
or
DIR E:\mjsaa



The drive letter in use when you find the folder willneed to be substituted (for<drive>) into the followingcommand...



XCOPY<drive>:\mjsaa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time)andwhen the prompt returns, type
EXIT
and hit the Enter key to exit CommandPrompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in anElevated Command Prompt
then reboot and upload the new CBS.log file to your SkyDrive Public folder, andpost a new link

Also run a new MGADiag report, and post the result.

 

[mikeyjames]

Hi Noel,

Very much appreciate your help. Well, I found another problem (now sorted). I don't have the recovery environment on boot. Tried my original Win 7 disc and got told that recovery options weren't compatible with my system? Tried what you suggested using safe mode with command prompt and it wouldn't work. Finally, after a lot of mucking about I was finally able to convince the recovery console that I was indeed using the correct OS

Here is my MGA report

Diagnostic Report (1.9.0027.0):
-----------------------------------------
Windows Validation Data-->
Validation Code: 0
Cached Online Validation Code: 0x0
Windows Product Key: *****-*****-HKD3V-FXXHY-M9824
Windows Product Key Hash: u6FLUQvZRbAmPV9P9zd2ufLvx7g=
Windows Product ID: 00426-292-5198757-85597
Windows Product ID Type: 5
Windows License Type: Retail
Windows OS version: 6.1.7601.2.00010100.1.0.001
ID: {EBBC9C7F-BCCA-4091-B805-23F9E5D5AF5B}(3)
Is Admin: Yes
TestCab: 0x0
LegitcheckControl ActiveX: Registered, 1.9.42.0
Signed By: Microsoft
Product Name: Windows 7 Ultimate
Architecture: 0x00000009
Build lab: 7601.win7sp1_gdr.130828-1532
TTS Error: T:20120722040755752-
Validation Diagnostic: 
Resolution Status: N/A
Vista WgaER Data-->
ThreatID(s): N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
Windows XP Notifications Data-->
Cached Result: N/A, hr = 0x80070002
File Exists: No
Version: N/A, hr = 0x80070002
WgaTray.exe Signed By: N/A, hr = 0x80070002
WgaLogon.dll Signed By: N/A, hr = 0x80070002
OGA Notifications Data-->
Cached Result: N/A, hr = 0x80070002
Version: N/A, hr = 0x80070002
OGAExec.exe Signed By: N/A, hr = 0x80070002
OGAAddin.dll Signed By: N/A, hr = 0x80070002
OGA Data-->
Office Status: 100 Genuine
Microsoft Office Enterprise 2007 - 100 Genuine
Microsoft Office Project Standard 2007 - 100 Genuine
Microsoft Office Visio Standard 2007 - 100 Genuine
OGA Version: N/A, 0x80070002
Signed By: N/A, hr = 0x80070002
Office Diagnostics: B4D0AA8B-604-645_7E90FEE8-198-80004005_025D1FF3-364-80041010_025D1FF3-229-80041010_025D1FF3-230-1_025D1FF3-517-80040154_025D1FF3-237-80040154_025D1FF3-238-2_025D1FF3-244-80070002_025D1FF3-258-3
Browser Data-->
Proxy settings: N/A
User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Win32)
Default Browser: C:\Program Files (x86)\Internet Explorer\IEXPLORE.exe
Download signed ActiveX controls: Prompt
Download unsigned ActiveX controls: Disabled
Run ActiveX controls and plug-ins: Allowed
Initialize and script ActiveX controls not marked as safe: Disabled
Allow scripting of Internet Explorer Webbrowser control: Disabled
Active scripting: Allowed
Script ActiveX controls marked as safe for scripting: Allowed
File Scan Data-->
Other data-->
Office Details: <GenuineResults><MachineData><UGUID>{EBBC9C7F-BCCA-4091-B805-23F9E5D5AF5B}</UGUID><Version>1.9.0027.0</Version><OS>6.1.7601.2.00010100.1.0.001</OS><Architecture>x64</Architecture><PKey>*****-*****-*****-*****-M9824</PKey><PID>00426-292-5198757-85597</PID><PIDType>5</PIDType><SID>S-1-5-21-3265357140-3170985111-3218714167</SID><SYSTEM><Manufacturer>Gigabyte Technology Co., Ltd.</Manufacturer><Model>To be filled by O.E.M.</Model></SYSTEM><BIOS><Manufacturer>American Megatrends Inc.</Manufacturer><Version>F13f</Version><SMBIOSVersion major="2" minor="7"/><Date>20120820000000.000000+000</Date></BIOS><HWID>3CE23707018400F2</HWID><UserLCID>0C09</UserLCID><SystemLCID>0409</SystemLCID><TimeZone>AUS Eastern Standard Time(GMT+10:00)</TimeZone><iJoin>0</iJoin><SBID><stat>3</stat><msppid></msppid><name></name><model></model></SBID><OEM/><GANotification/></MachineData><Software><Office><Result>100</Result><Products><Product GUID="{90120000-0030-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Enterprise 2007</Name><Ver>12</Ver><Val>7480B9502DF0D86</Val><Hash>oYWOW5ayFE3pZ+jvTpuXYsY64JE=</Hash><Pid>89388-707-8722531-65701</Pid><PidType>14</PidType></Product><Product GUID="{90120000-003A-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Project Standard 2007</Name><Ver>12</Ver><Val>437005356259D86</Val><Hash>G5Qjl2nuHEjAmcG9TDdU8SHIOkc=</Hash><Pid>89402-707-0356806-63494</Pid><PidType>14</PidType></Product><Product GUID="{90120000-0053-0000-0000-0000000FF1CE}"><LegitResult>100</LegitResult><Name>Microsoft Office Visio Standard 2007</Name><Ver>12</Ver><Val>437005356259D86</Val><Hash>G5Qjl2nuHEjAmcG9TDdU8SHIOkc=</Hash><Pid>89406-707-0356806-63455</Pid><PidType>14</PidType></Product></Products><Applications><App Id="15" Version="12" Result="100"/><App Id="16" Version="12" Result="100"/><App Id="18" Version="12" Result="100"/><App Id="19" Version="12" Result="100"/><App Id="1A" Version="12" Result="100"/><App Id="1B" Version="12" Result="100"/><App Id="3A" Version="12" Result="100"/><App Id="44" Version="12" Result="100"/><App Id="53" Version="12" Result="100"/><App Id="A1" Version="12" Result="100"/><App Id="BA" Version="12" Result="100"/></Applications></Office></Software></GenuineResults>  
Spsys.log Content: 0x80070002
Licensing Data-->
Software licensing service version: 6.1.7601.17514
Name: Windows(R) 7, Ultimate edition
Description: Windows Operating System - Windows(R) 7, RETAIL channel
Activation ID: ac96e1a8-6cc4-4310-a4ff-332ce77fb5b8
Application ID: 55c92734-d682-4d71-983e-d6ec3f16059f
Extended PID: 00426-00170-292-519875-00-3081-7601.0000-2042012
Installation ID: 007952142624293965241154309042001632056724637330639401
Processor Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88338[/URL]
Machine Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88339[/URL]
Use License URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88341[/URL]
Product Key Certificate URL: [URL]http://go.microsoft.com/fwlink/?LinkID=88340[/URL]
Partial Product Key: M9824
License Status: Licensed
Remaining Windows rearm count: 5
Trusted time: 10/11/2013 7:31:55 PM
Windows Activation Technologies-->
HrOffline: 0x00000000
HrOnline: 0x00000000
HealthStatus: 0x0000000000000000
Event Time Stamp: 11:10:2013 17:55
ActiveX: Registered, Version: 7.1.7600.16395
Admin Service: Registered, Version: 7.1.7600.16395
HealthStatus Bitmask Output:
 
HWID Data-->
HWID Hash Current: NgAAAAIAAAABAAEAAwAEAAAAAQABAAEAHKIQSdqalF3INfrQ7hbeiOznyiu8iezwLwMc1DQh
OEM Activation 1.0 Data-->
N/A
OEM Activation 2.0 Data-->
BIOS valid for OA 2.0: yes, but no SLIC table
Windows marker version: N/A
OEMID and OEMTableID Consistent: N/A
BIOS Information: 
  ACPI Table Name OEMID Value OEMTableID Value
  APIC   ALASKA  A M I
  FACP   ALASKA  A M I
  HPET   ALASKA  A M I
  MCFG   ALASKA  OEMMCFG.
  SSDT   INTEL  CpuPm
  MATS   ALASKA  A M I
  MATS   ALASKA  A M I

Here is the link to my logs

Thanks again,

Mick

 

[NoelDP]

The request for an MGADiag was an aberration on my part - sorry about that!
It seems that you have an upgrade of Windows 7 installed?


The lack of the Repair option implies that you don't have the System Reserved partition in place - which in turn implies that you pre-formatted the drive before installing Windows Vista or above.


Not disastrous - but it can make doing things like this more difficult


My Internet connection is playing up today - so it may be some time before I can detail the CBS data

 

[mikeyjames]

Thanks Noel. Yes, I was rather lazy when I first got Win 7 and just did an upgrade install. I planned on a clean install when I upgraded my system last year. When I put in the new motherboard and CPU, basically everything bar the hard drive (since updated to SSD) I booted up, Win 7 loaded the new drivers and ran so well I've never bothered with the clean install.

lazy I know

Thanks
Mick

 

[NoelDP]

Got the files eventually!
The file error has been corrected, according to the SFC log...
The other errors are still present -
2013-11-10 18:11:16, Error CBS Failed to shred identity: Microsoft-Windows-InternetExplorer-LanguagePack [HRESULT = 0x80070057 - E_INVALIDARG]
and many similar ones.


These seem to be triggered by the following packages..
2013-11-09 10:20:11, Info CBS Read out cached package applicability for package: Package_for_KB2879017~31bf3856ad364e35~amd64~~9.4.1.0, ApplicableState: 112, CurrentState:112

2013-11-10 18:11:17, Info CBS Read out cached package applicability for package: Package_for_KB2849470~31bf3856ad364e35~amd64~~6.1.1.3, ApplicableState: 112, CurrentState:112

2013-11-10 18:11:17, Info CBS Read out cached package applicability for package: Package_for_KB2761465~31bf3856ad364e35~amd64~~10.2.1.0, ApplicableState: 0, CurrentState:0


In the other logs, the only thing of significance that I can see is that Norton 360 appears either to be currently installed, or has been improperly uninstalled?




Please run the following commands, and let's see what the result is...


REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2879017~31bf3856ad364e35~amd64~~9.4.1.0"
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2761465~31bf3856ad364e35~amd64~~10.2.1.0"
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2849470~31bf3856ad364e35~amd64~~6.1.1.3"





Here are some instructions to make life easier


1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.


2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.


3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

 

[mikeyjames]

Hi Noel,

Here are the results.

Thanks

Mick

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
 C:\Users\Mick>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2879017~31bf3856ad364e35~amd64~~9.4.1.0"
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2879017~31bf3856ad364e35~amd64~~9.4.1.0
    InstallClient    REG_SZ    WindowsUpdateAgent
    InstallName    REG_SZ    update.mum
    InstallLocation    REG_SZ    [URL="file://\\?\C:\Windows\SoftwareDistribution\Download\8e20801a21124956594794dc5d647fd6\inst\"]\\?\C:\Windows\SoftwareDistribution\Download\8e20801a21124956594794dc5d647fd6\inst\[/URL]
    CurrentState    REG_DWORD    0x50
    SelfUpdate    REG_DWORD    0x0
    Visibility    REG_DWORD    0x1
    InstallTimeHigh    REG_DWORD    0x1cec487
    InstallTimeLow    REG_DWORD    0x734c2cb4
    InstallUser    REG_SZ    S-1-5-21-3265357140-3170985111-3218714167-1001
    Trusted    REG_DWORD    0x1
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2879017~31bf3856ad364e35~amd64~~9.4.1.0\Owners
  
 C:\Users\Mick>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2761465~31bf3856ad364e35~amd64~~10.2.1.0"
ERROR: The system was unable to find the specified registry key or value.
  
 C:\Users\Mick>REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2849470~31bf3856ad364e35~amd64~~6.1.1.3"
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2849470~31bf3856ad364e35~amd64~~6.1.1.3
    InstallClient    REG_SZ    WindowsUpdateAgent
    InstallName    REG_SZ    update.mum
    InstallLocation    REG_SZ    [URL="file://\\?\C:\Windows\SoftwareDistribution\Download\f5df9272697b7977258a9f6b789428b6\"]\\?\C:\Windows\SoftwareDistribution\Download\f5df9272697b7977258a9f6b789428b6\[/URL]
    CurrentState    REG_DWORD    0x70
    SelfUpdate    REG_DWORD    0x0
    Visibility    REG_DWORD    0x1
    InstallTimeHigh    REG_DWORD    0x1ce98ac
    InstallTimeLow    REG_DWORD    0x1c73aefc
    InstallUser    REG_SZ    S-1-5-21-3265357140-3170985111-3218714167-1001
    Trusted    REG_DWORD    0x1
 HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\Packages\Package_for_KB2849470~31bf3856ad364e35~amd64~~6.1.1.3\Owners
 C:\Users\Mick>

 

[NoelDP]

As far as I can see, those are normal - which means I'm looking in the wrong place

The missing IE10 reference is to be expected, if the install failed because of the other errors.


I've just discovered that MS have released a new version of the CheckSUR tool in the past 24hours - it would be worth running it to see if it highlights anything new for us.
Please download the new one, and run it - post the new CheckSUR log and we'll see what we can see

 

[mikeyjames]

Hi Noel,

Thanks very much for all of your help. I am now using ie11 after a successful ie10 install. I thought I'd give it a try and it worked!

I really can't thank you enough as I have been trying everything I could think of since 10 was released.

It must have been that one file you got me to install. Out of interest isn't the winsxs folder just backups of old updates or something? Why would one corrupt file that seems to have nothing to do with anything have blocked the update

Cheers
Mick

 

[NoelDP]

The Winsxs folder is a lot more than just backups!
many of the files in Windows7 only actually exist in the winsxs folder - what you see elsewhere may be nothing but a hardlink to the winsxs file. Also if a file is damaged elsewhere, then the system will attempt to replace it from the winsxs copy.

In this case the file is actually an integral part of the ServicingStack package - which as its name implies takes control of servicing operations. It's this package (in conjunction with a few others) that actually does the work involved in installing new patches and programs - so you can see why things fail if that's not working properly.

 

[seaklarmacher]

IE10 installation not possible

Hi,
Same for me, first time I post something here and 2nd IE10 installation failed on WIN7 64bit (IE11 failed too). I tried every item found in the internet...
Finally, SURT, 3xSFC Scan with errors, cleaned event log, started win IE10 update, SFC Scan. CBS log & error screenshot is attached. Now I am here.
I am not a computer crack, I tried to follow your steps so please be patient with me.
Thanks for your help guys.

 

[NoelDP]

There's only the one file error in your SFC scan -

2014-03-23 01:27:49, Info                  CSI    00000311 [SR] Cannot repair member file [l:22{11}]"wdscore.dll" of Microsoft-Windows-ServicingStack, Version = 6.1.7601.17592, 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

- but it's possible that there are other problems.

Please download and save the CheckSUR tool from http://support.microsoft.com/kb/947821
(you'll need to look in the details for Windows 7, downloading from the Microsoft Download Center)

Run it - The tool can take anywhere from 5 mins to a couple of hours to run (or 'Install') depending on how much it has to do, and may exit silently - it may appear to freeze for most of that time, but be patient.
The result is logged in the C:\Windows\Logs\CBS\CheckSUR.log file - and an archive …\checksur.persist.log file

Then zip the CheckSUR.log and upload it to your reply.

 

[seaklarmacher]

Thanks for your reply ,
I cleaned the event log, installed the tool and afterwards ran windows update installation IE10. Same error code. The files are attached. (Win 7, 64 bit SP1)

 

[NoelDP]

That has found the same error - and nothing else, so it should be a fairly simple fix.
I'll post the protocol later.

 

[NoelDP]

Sorry about the delay!


I've uploaded a file - skmaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.

Right-click on the saved file and select Extract all...
Change the target to C:\ and click on Extract
Close all windows (it would be a good idea to print these instructions!)

Now reboot to the Repair Environment - as soon as the machine restarts, start tapping F8 - this should bring up the Advanced Boot Menu, at the top of which should be the option 'Repair my Computer'
Pick that
You'll have to log in with your username and password.

Pick the option to use a Command Prompt
At the prompt type
DIR C:\skmaa
hit the enter key - if you get a 'Not Found' error try
DIR D:\skmaa
or
DIR E:\skmaa



The drive letter in use when you find the folder will need to be substituted (for<drive>) into the following command...



XCOPY <drive>:\skmaa <drive>:\windows\winsxs /y /i /s /v /h



(e.g. XCOPY P:\wfire P:\windows\winsxs /y /i /s /v /h )



run the command (it should take almost no time) and when the prompt returns, type
EXIT
and hit the Enter key to exit Command Prompt - reboot to Normal Mode Windows.

Now run SFC /SCANNOW in an Elevated Command Prompt
then reboot and upload the new CBS.log file to your reply

 

[seaklarmacher]

IE10 installation not possible

Hi Noel,

I tried it, but I cannot find the file on the respective drive letter. When I open the command prompt it comes up with X:/Windows/System32
I tried every possible option.
I guess it is E:, but it tells me the device is not ready. Any idea?

 

[Layback Bear]

seaklarmacher be very careful.
Many of Noels posts/repairs are designed only for the computer in question.

I would suggest that you start a new thread of your own so you can get exact instruction for your exact needs.