Cannot install IE10 on Win 7 x64 on Dell Latitude

Page 1 of 5 123 ... LastLast

  1. Posts : 18
    Windows Enterprise 64bit
       #1

    Cannot install IE10 on Win 7 x64 on Dell Latitude


    Hello, I need help repairing my Windows in order to upgrade to IE 10.

    I am getting error code 9C59.

    I ran the SURT - Windows6.1-KB947821-v26-x64.msu

    Attached is my CheckSUR.log, please let me know what I need to do to correct this problem.

    I ran SFC /SCANNOW and have attached sfcdetails.txt file as well.

    Thanks
    Last edited by jruiz22; 03 Apr 2013 at 01:02. Reason: Adding Content
      My Computer


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

    You have some fairly major system corruption....
    From the CheckSUR
    Code:
    Unavailable repair files:
     winsxs\manifests\amd64_microsoft-windows-ie-controls.resources_31bf3856ad364e35_9.4.8112.16443_en-us_2273b6e38a9560e7.manifest
     winsxs\manifests\amd64_microsoft-windows-i..rolviewer.resources_31bf3856ad364e35_9.4.8112.16443_en-us_16feb7e28f502777.manifest
     winsxs\manifests\amd64_microsoft-windows-ieframe.resources_31bf3856ad364e35_9.4.8112.16443_en-us_0450e72ea0608423.manifest
     winsxs\manifests\amd64_microsoft-windows-i..onmanager.resources_31bf3856ad364e35_9.4.8112.16443_en-us_0979a9e1a2043663.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-setup.resources_31bf3856ad364e35_9.4.8112.16443_en-us_c5b84a42a315520e.manifest
     winsxs\manifests\amd64_microsoft-windows-i..kitengine.resources_31bf3856ad364e35_9.4.8112.16443_en-us_58a237eda551fefe.manifest
     winsxs\manifests\amd64_microsoft-windows-ie-feedsbs.resources_31bf3856ad364e35_9.4.8112.16443_en-us_bd048d99aae88a13.manifest
     winsxs\manifests\amd64_microsoft-windows-i..trolpanel.resources_31bf3856ad364e35_9.4.8112.16443_en-us_97154455bade5049.manifest
     winsxs\manifests\amd64_microsoft-windows-i..filercore.resources_31bf3856ad364e35_9.4.8112.16443_en-us_d812f0b2c6de824a.manifest
     winsxs\manifests\amd64_microsoft-windows-i..rendering.resources_31bf3856ad364e35_9.4.8112.16443_en-us_81730a84d61f5330.manifest
     winsxs\manifests\amd64_microsoft-windows-i..rofilerui.resources_31bf3856ad364e35_9.4.8112.16443_en-us_be56672dd6eea4bf.manifest
     winsxs\manifests\amd64_microsoft-windows-i..tbranding.resources_31bf3856ad364e35_9.4.8112.16443_en-us_6ac95865d9f23ccb.manifest
     winsxs\manifests\amd64_microsoft-windows-i..explorer-deployment_31bf3856ad364e35_9.4.8112.16443_none_c251ee64ebbd3509.manifest
     winsxs\manifests\x86_microsoft-windows-i..ntrolpanel-optional_31bf3856ad364e35_9.4.8112.16443_none_862586c1332c1d0b.manifest
     winsxs\manifests\amd64_microsoft-windows-i..orer-oob-deployment_31bf3856ad364e35_9.4.8112.16443_none_c8eb3eb49f72f8f6.manifest
     winsxs\manifests\x86_microsoft.vc90.atl_1fc8b3b9a1e18e3b_9.0.30729.6161_none_51cd0a7abbe4e19b.manifest
     winsxs\manifests\msil_system.design_b03f5f7f11d50a3a_6.1.7601.17966_none_89ab3041bfbe7442.manifest
     winsxs\manifests\msil_system.directoryservices.protocols_b03f5f7f11d50a3a_6.1.7601.17966_none_837b7fa210fd83d6.manifest
     winsxs\manifests\amd64_microsoft-windows-windowsupdate-adm_31bf3856ad364e35_7.6.7600.256_none_9286cad7bab620de.manifest
     winsxs\manifests\x86_microsoft-windows-virtualpc-additions_31bf3856ad364e35_7.1.7600.16393_none_fa50c45d13592d39.manifest
     winsxs\manifests\msil_system.directoryservices.protocols_b03f5f7f11d50a3a_6.1.7601.22126_none_6ca9dae42aa878ce.manifest
     winsxs\manifests\amd64_72eca7b5ceeb2568f653dc818af98453_b03f5f7f11d50a3a_6.1.7601.17587_none_22dd77a2b8e92492.manifest
     winsxs\manifests\amd64_81078092d4d98b95dc52fb6ce54495bb_b03f5f7f11d50a3a_6.1.7601.21693_none_223376243cd12b7e.manifest
     winsxs\manifests\x86_netfx-mscordacwks_b03f5f7f11d50a3a_6.1.7601.17587_none_ff8490d1c3813994.manifest
     winsxs\manifests\amd64_win7-microsoft-wind..oyment-languagepack_31bf3856ad364e35_7.1.7601.16492_ko-kr_5a15022f252c077f.manifest
     winsxs\manifests\amd64_microsoft-windows-n..-deployment-netfx20_31bf3856ad364e35_6.2.7600.16513_none_9adfccf5ffc9e41e.manifest
     winsxs\manifests\msil_system.design_b03f5f7f11d50a3a_6.1.7601.22126_none_72d98b83d969693a.manifest
     winsxs\manifests\msil_system.directoryservices.resources_b03f5f7f11d50a3a_6.1.7601.17966_en-us_0dbb286c9035e5e2.manifest
     winsxs\manifests\msil_system.directoryservices.resources_b03f5f7f11d50a3a_6.1.7601.22126_en-us_f6e983aea9e0dada.manifest
     winsxs\manifests\x86_microsoft-windows-ie-htmlactivexcompat_31bf3856ad364e35_9.4.8112.16443_none_2fdb70c12a1e1e73.manifest
     winsxs\manifests\x86_microsoft-windows-ie-ieproxy_31bf3856ad364e35_9.4.8112.16443_none_a89ae7d964e5586a.manifest
     winsxs\manifests\x86_microsoft-windows-i..nternetcontrolpanel_31bf3856ad364e35_9.4.8112.16443_none_a7a5a98a6c2d4c7c.manifest
     winsxs\manifests\x86_microsoft-windows-ie-ieproxy-legacy_31bf3856ad364e35_9.4.8112.16443_none_c4b8662176f5e118.manifest
     winsxs\manifests\x86_microsoft-windows-ie-setup-support_31bf3856ad364e35_9.4.8112.16443_none_de3cb89e78ce0573.manifest
     winsxs\manifests\wow64_microsoft-windows-ie-directxtransforms_31bf3856ad364e35_9.4.8112.16443_none_16a5985f88b7019d.manifest
     winsxs\manifests\wow64_microsoft-windows-ie-datacontrol_31bf3856ad364e35_9.4.8112.16443_none_92e6723aa73c93da.manifest
     winsxs\manifests\wow64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.8112.16443_none_e381b5efb531f87f.manifest
     winsxs\manifests\x86_microsoft-windows-ie-extcompat_31bf3856ad364e35_9.4.8112.16443_none_551baf7cf0eec21f.manifest
     winsxs\manifests\wow64_microsoft-windows-ie-behaviors_31bf3856ad364e35_9.4.8112.16443_none_bba2cdfef920c97e.manifest
     winsxs\manifests\x86_microsoft-windows-ie-lowreg_31bf3856ad364e35_9.4.8112.16443_none_c0b8357bfe359ea8.manifest
     winsxs\manifests\wow64_microsoft-windows-scripting-jscript_31bf3856ad364e35_9.4.8112.16443_none_01bf31e6fe374643.manifest
     winsxs\manifests\x86_microsoft-windows-i..tocolimplementation_31bf3856ad364e35_9.4.8112.16443_none_1a54f6f7bc27cdeb.manifest
     winsxs\manifests\x86_microsoft-windows-ie-ratings_31bf3856ad364e35_9.4.8112.16443_none_dffe41ce770ff6cc.manifest
     winsxs\manifests\x86_microsoft-windows-i..ersandsecurityzones_31bf3856ad364e35_9.4.8112.16443_none_cd4f1b55f11ea758.manifest
     servicing\packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.mum
     servicing\packages\Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.mum
     servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.mum
     servicing\packages\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.cat
     servicing\packages\Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492.cat
     servicing\packages\Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0.cat
     servicing\packages\Package_for_KB2522422_SP1~31bf3856ad364e35~amd64~~6.1.1.0.cat
    From the SFC scan
    Code:
    2013-04-03 01:53:50, Info                  CSI    0000044d [SR] Repairing 42 (0x000000000000002a) components
    all of which failed - because of the lack of the proper manifest and package files.

    I'll post a fix protocol later, but it could take a while
      My Computer


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

    I'm having trouble sourcing an update for IE9 that is giving many of the errors found. It may be an update that's been withdrawn, or I may just be missing it in my search.

    We'll go with what I've found so far....


    I've uploaded a file - j22aa.zip - to my SkyDrive at Noel's SkyDrive
    Please download and save it.
    Right-click on the downloaded file, and select Extract all…
    Extract to the default location - which will create a new folder j22aa in the same place.
    Open this folder - there should be two folders inside it (Manifests, and Packages)

    Copy the content of the Packages folder to the folder
    C:\Windows\Temp\CheckSur\Servicing\Packages

    And the content of the manifests folder (.manifest files) into this folder:

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

    Now run the CheckSUR tool again (it may take a while)

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


  4. Posts : 18
    Windows Enterprise 64bit
    Thread Starter
       #4

    Thank you very much for your NoelDP, I have finished the CheckSUR tool again after copying your files.

    It appears the file got a little bit longer, but some of the stuff you sent no longer appears on the list.
      My Computer


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

    Great - the file has done what it was supposed to do, and cleared the decks a bit :)

    Now I'll have to concentrate on the 18 Watchlist errors and see where they get us.

    back a bit later.
    ... just for reference....
    Code:
    Checking Package Watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-NetFx2-ServerCore-OC-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-NetFx2-ServerCore-OC-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-Printing-ServerCore-Package~31bf3856ad364e35~amd64~~0.0.0.0 Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Package Missing 0x80070002 Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~~0.0.0.0 Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~uk-UA~7.1.7601.16492 Package registry presence failed, possibly an orphaned package on package watchlist
    Checking Component Watchlist
    (f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 msil_system.windows.forms_b77a5c561934e089_6.1.0.0_none_0a57c6e724b6dfa9 Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 msil_system.windows.forms_b77a5c561934e089_6.1.0.0_none_0a57c6e724b6dfa9 Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86 Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86 Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86 Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
    (f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86 Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0 Package registry presence failed, possibly an orphaned package on package watchlist
      My Computer


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

    We'll deal with the Component list first.

    Please open an Elevated Command Prompt, and run the following commands

    Code:
     
    REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc" >>%userprofile%\desktop\npwcom.log
    REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86" >>%userprofile%\desktop\npwcom.log
    REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\msil_system.windows.forms_b77a5c561934e089_6.1.0.0_none_0a57c6e724b6dfa9" >>%userprofile%\desktop\npwcom.log
     
    .
    That should create a file on your desktop 'npwcom.log'
    Please attach it to your reply.
    Last edited by NoelDP; 03 Apr 2013 at 08:07. Reason: correct overwrite
      My Computer


  7. Posts : 18
    Windows Enterprise 64bit
    Thread Starter
       #7

    Attached is the 'npwcom.log'
      My Computer


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

    Argh - a typo on my part

    Please try again with the *corrected* commands above!
      My Computer


  9. Posts : 18
    Windows Enterprise 64bit
    Thread Starter
       #9

    Hey no problem, here is the new file
      My Computer


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

    That's more like it! :)
    The results are as expected
    Now comes the difficult and dangerous bit.

    How confident are you in Regedit?
    We have to manually adjust permissions before we make changes - and then adjust them back afterwards.
    I'm OK doing this fix for myself - but I've never tried talking anyone through it on the forums.

    There are two ways
    1) If you're reasonably confident, you can do the whole thing manually, and individually (possibly the best way)
    2) If you're not confident, then we can limit your involvement to one permissions change before running a registry file. and one permissions change after.

    Your choice.
      My Computer


 
Page 1 of 5 123 ... LastLast

  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 21:19.
Find Us