Solved IE10 install error 9C44

[Nick2010]

[RESOLVED]IE10 install error 9C44

I'm tidying up a friend's laptop but I'm having trouble installing IE10. Windows Update is giving me error code 9C44 and the standalone installer tells me that 'Internet Explorer 10 can only be installed on Windows 7 Service Pack 1 or higher'.

The laptop is running Windows 7 Home Premium x64 build 7601 so everything should be ok. However, when viewing 'Computer' properties, the Windows Edition just shows as Windows 7 Home Premium with no mention of SP1. Looking through the list of installed updates, I can see Service Pack for Microsoft Windows (KB976932) is installed and the Service Pack install files are available in disk cleanup.

I have successfully run the SURT. KB2670838 is also installed.

The WindowsUpdate log references the following error: 0x80070643 which seems to suggest it's something to do with the .NET Framework but I'm not entirely sure.

I would appreciate any help and I will be happy to provide any more details.

Thanks.

Have attached the CBS and WindowsUpdate logs.

Edit: Currently running sfc. SFC said it found some issues but was unable to repair them. Have added the new CBS log (CBS-SFC.zip).

 

[Nick2010]

The IE10_main.log file contains the following lines for each attempted IE10 installation:

00:00.062: INFO:    Operating System: Windows Workstation: 6.1.7601
00:00.062: ERROR:   System version and prerequisite validation checks failed.
00:00.062: INFO:    Setup exit code: 0x00009C44 (40004) - Old OS Version.

It seems the installer is having trouble picking up SP1 on the laptop.

 

[Nick2010]

Some progress....

I decided to uninstall SP1 which took the entire night. At first, I tried to uninstall via installed updates but after leaving the process running for a few hours, it seemed to hang so I forced a restart. I then tried to command line method and left it running then I went to bed. I restarted in the morning and then checked for updates. SP1 was offered so I went ahead and chose to install. A couple of hours later it completed and Service Pack 1 now shows in 'Computer' properties as well as winver.

Currently trying to install IE10 again....

 

[Nick2010]

Success!

 

[NoelDP]

Great!

For what it's worth, you had a couple of fairly critical file errors in the SFC log...

 Line 9612: 2013-04-18 19:57:10, Info                  CSI    00000859 [SR] Repairing 2 components
 Line 9613: 2013-04-18 19:57:10, Info                  CSI    0000085a [SR] Beginning Verify and Repair transaction
 Line 9616: 2013-04-18 19:57:10, Info                  CSI    0000085c [SR] Cannot repair member file [l:20{10}]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, 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
 Line 9619: 2013-04-18 19:57:10, Info                  CSI    0000085e [SR] Cannot repair member file [l:20{10}]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, 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

It may be these that the install was complaining about - or there may have been more errors discovered by a CheckSUR scan.
I would recommend running both SFC and CheckSUR again, and posting the new results.

 

[Nick2010]

Great!

For what it's worth, you had a couple of fairly critical file errors in the SFC log...

 Line 9612: 2013-04-18 19:57:10, Info                  CSI    00000859 [SR] Repairing 2 components
 Line 9613: 2013-04-18 19:57:10, Info                  CSI    0000085a [SR] Beginning Verify and Repair transaction
 Line 9616: 2013-04-18 19:57:10, Info                  CSI    0000085c [SR] Cannot repair member file [l:20{10}]"gptext.dll" of Microsoft-Windows-GroupPolicy-Gptext, 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
 Line 9619: 2013-04-18 19:57:10, Info                  CSI    0000085e [SR] Cannot repair member file [l:20{10}]"gpedit.dll" of Microsoft-Windows-GroupPolicy-Admin-Gpedit, 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

It may be these that the install was complaining about - or there may have been more errors discovered by a CheckSUR scan.
I would recommend running both SFC and CheckSUR again, and posting the new results.

Thanks for the reply NoelDP.

I did notice them when I checked the log before posting...I put it down to me manually adding the group policy files to the home premium installation.

Do you think that could that be the reason?

 

[NoelDP]

You really shouldn't mess with the system in that way - the files are already present in all installs, it's merely the necessary links that are missing. Group Policy is not configurable in Home Premium and lower editions of Windows 7 - and these files shouldn't need changing in the higher editions.
modifying policies manually doesn't make any changes to the dll files.