WU won't Update IE 9 and 10 - Error codes


  1. Posts : 29
    Windows 7 Home Premium x64
       #1

    WU won't Update IE 9 and 10 - Error codes


    I will start from the beginning, A mate rang me to ask if i could fix his laptop, but i was away on holiday atm, told him to check some local computer stores. So he did and got a local computer to fix his laptop for him.

    When i returned to holiday i rang him to see what was fixed on his laptop and how is it running. he said its fixed the store said the hard drive had bad sectors and they fixed them. But slow at times and windows update is running every night. So i picked up his laptop this weekend. I've replaced the HD with a SSD, used the Samsung migration tool came with it. Ran a Disk Check on it to fix any errors that was copied across.

    Then i looked at the Windows Update issue. I noticed it was stuck on 2 updates for IE. I checked what version was installed which was 9. Thou WU still wanted to installed version 9 and version 10. Tried to uninstall version 9 but wouldn't let me saying Not all of the updates were successfully installed. So i came here read your Windows Update Posting Instructions. Follows the steps there. Ran SURT, and did a sfc scan.

    The 2 errors are Code9C48 and Code9C59. IE 9 and IE 10.

    What can i do to fix this?
      My Computer


  2. Posts : 29
    Windows 7 Home Premium x64
    Thread Starter
       #2

    Having problems uploading the CBS Log, it's too big for single file upload, so i split it into 3 parts, but still won't load. So i uploaded to a website and posted the link here.

    CBS Log
      My Computer


  3. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #3

    You have a fair number of problems in the CheckSUR report...
    Code:
    Unavailable repair files:
     winsxs\manifests\amd64_microsoft-windows-ie-winsockautodialstub_31bf3856ad364e35_9.4.8112.16446_none_64b871223079d9d0.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_9.4.8112.20551_none_a4696b5205d83711.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-versioninfo_31bf3856ad364e35_9.4.8112.16446_none_73b37f0507a9980f.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16446_none_b13d4bdea9497f5a.manifest
     winsxs\manifests\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.20551_none_76f05ec68dacc82e.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-htmlrendering_31bf3856ad364e35_9.4.8112.20551_none_884a7de50e033164.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-winsockautodialstub_31bf3856ad364e35_9.4.8112.20551_none_65323c8f49a416d8.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.16446_none_b032acac1285d767.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.16446_none_bc1acfd16ce87c13.manifest
     winsxs\manifests\amd64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_9.4.8112.16446_none_0d43fc3580754114.manifest
     winsxs\manifests\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_9.4.8112.16446_none_1798a687b4d6030f.manifest
     winsxs\manifests\amd64_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.16446_none_03c745ec248809b7.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_9.4.8112.16446_none_bc314a355f33a983.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.20551_none_05364fa8366a52ad.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-versioninfo_31bf3856ad364e35_9.4.8112.20551_none_742d4a7220d3d517.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-internetexplorer_31bf3856ad364e35_9.4.8112.16446_none_a3ef9fe4ecadfa09.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-jscriptdebugui_31bf3856ad364e35_9.4.8112.20551_none_2f73ba26b97ef317.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-devtools_31bf3856ad364e35_9.4.8112.20551_none_b0ac78192bb0146f.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-ieshims_31bf3856ad364e35_9.4.8112.20551_none_bc949b3e8612b91b.manifest
     winsxs\manifests\amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_9.4.8112.16446_none_2970b7b7a9796493.manifest
     winsxs\manifests\amd64_microsoft-windows-scripting-jscript_31bf3856ad364e35_9.4.8112.16446_none_f76d8872c9d3d04d.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-jscriptdebugui_31bf3856ad364e35_9.4.8112.16446_none_2ef9eeb9a054b60f.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-runtimeutilities_31bf3856ad364e35_9.4.8112.20551_none_bcab15a2785de68b.manifest
     winsxs\manifests\amd64_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16446_none_7676935974828b26.manifest
     winsxs\manifests\amd64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_9.4.8112.20551_none_0dbdc7a2999f7e1c.manifest
     winsxs\manifests\wow64_microsoft-windows-i..etexplorer-optional_31bf3856ad364e35_9.4.8112.20551_none_181271f4ce004017.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.20551_none_b1b7174bc273bc62.manifest
     winsxs\manifests\amd64_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_9.4.8112.20551_none_29ea8324c2a3a19b.manifest
     winsxs\manifests\amd64_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.20551_none_044111593db246bf.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16446_none_04bc843b1d4015a5.manifest
     servicing\packages\Package_1_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.mum
     servicing\packages\Package_1_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.mum
     servicing\packages\Package_2_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.mum
     servicing\packages\Package_2_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.mum
     servicing\packages\Package_for_KB2699988_RTM~31bf3856ad364e35~amd64~~9.4.1.0.mum
     servicing\packages\Package_for_KB2699988_RTM~31bf3856ad364e35~amd64~~9.4.1.0.mum
     servicing\packages\Package_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.mum
     servicing\packages\Package_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.mum
     servicing\packages\Package_1_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.cat
     servicing\packages\Package_1_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.cat
     servicing\packages\Package_2_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.cat
     servicing\packages\Package_2_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.cat
     servicing\packages\Package_for_KB2699988_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
     servicing\packages\Package_for_KB2699988_RTM~31bf3856ad364e35~amd64~~9.4.1.0.cat
     servicing\packages\Package_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.cat
     servicing\packages\Package_for_KB2699988~31bf3856ad364e35~amd64~~9.4.1.0.cat
    This is leading to a failure of SP1 - which explains why IE10 won't install!

    I'll post a fix protocol in a bit.
      My Computer


  4. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #4

    I've uploaded afile - sbyaa.zip - to my SkyDrive at Noel's SkyDrive

    Please downloadand save it.

    Right-click onthe downloaded file, and select Extract all…

    Extract to thedefault location - which will create a new folder sbyaain the same place.

    Open this folder- there should be two folders inside it (Manifests,and Packages)



    Copy the content of the Packages folder to thefolder

    C:\Windows\Temp\CheckSur\Servicing\Packages



    Andthe content of the manifestsfolder (.manifest files) into this folder:



    C:\Windows\Temp\CheckSur\Winsxs\Manifests



    Nowrun the CheckSUR tool again (it may take a while)



    Postthe new CheckSUR.log file, and the CheckSUR.persist.log file.
      My Computer


  5. Posts : 29
    Windows 7 Home Premium x64
    Thread Starter
       #5

    Thank Noel for helping me with this problem. Here is the new CheckSUR and CheckSUR.persist log files.
      My Computer


  6. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #6

    Great - CheckSUR now reads clean.
    Please now run another SFC /SCANNOW and we'll see if that's triggered any problems there - post the new CBS.log file.
      My Computer


  7. Posts : 29
    Windows 7 Home Premium x64
    Thread Starter
       #7

    SFC scan didn't find any problems, attached is new CBS Log
      My Computer


  8. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #8

    OK - do a manual Check for Updates, and see what's found.
    IE9 itself shouldn't be there any more, but you'll probably have a few updates for it. Install those first.
      My Computer


  9. Posts : 29
    Windows 7 Home Premium x64
    Thread Starter
       #9

    Thanks very much Noel, IE is now running on version 10.
      My Computer


  10. Posts : 21,482
    Win 7 x64 Home Premium (and x86 VirtualBox VM)/Win10
       #10

    That's what I like to hear! :)

    Good luck
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 7 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 7" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 09:56.
Find Us