Cannot install IE10 on Win 7 x64 on Dell Latitude

Page 2 of 5 FirstFirst 1234 ... LastLast

  1. Posts : 18
    Windows Enterprise 64bit
    Thread Starter
       #11

    I like to live on the wild side, let's do this the best way. But please, no typos on this step? :)
      My Computer


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

    It's OK - I'll test this one first! :)

    It's going to take me a while to work up the command file - back later.

    In the meantime, please ensure that you create a System Restore point (preferably two!)
      My Computer


  3. Posts : 18
    Windows Enterprise 64bit
    Thread Starter
       #13

    I like to live on the wild side, let's do option 1. But please no typos this time if it is that dangerous. :)
      My Computer


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



    WARNING - These instructions apply ONLY to this poster, in this thread. Following them on your own machine WILL break things!

    Here's the detailed instructions for the first Key modifications to make - if all goes well, I'll post the other two later

    Open Regedit
    Navigate to the
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect
    key
    and find the
    amd64_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_2b9bb45b11d2fcbc
    subkey
    right-click on the subkey to highlight it and select Permissions

    Click on the Advanced button
    Click on the Owner tab
    highlight 'Administrators' in the box, and click Apply
    put a tick in the 'Replace owner...' box, and click Apply
    Click on the Permissions tab
    highlight Administrators
    Click Edit
    put a tick in the Allow/Full Control box and click OK
    put a tick in the 'Replace all child...' box and click Apply
    Accept the warning
    Click OK twice to get back into Regedit

    in the right pane, look for the following values
    Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1
    Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-4_neutral_LDR
    Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-5_neutral_LDR
    Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-6_neutral_GDR


    Delete each - highlight it and hit the delete button - accept the warning if you're sure you got the right one
    THERE IS NO UNDO OPTION IN REGEDIT!


    Now we have to get permissions back to where they should be....
    right-click on the subkey name again, and select Permissions
    Click on Advanced
    There should be two entries for Administrators
    Highlight Administrators (with Full Control - not inherited) - make sure that the other Administrators entry with Read permissions still exists!
    click Remove
    Click on the Owner tab
    Click 'Other users or groups'
    in the box, type
    NT SERVICE\TrustedInstaller
    and click on 'Check Names' - the entry should change to TrustedInstaller
    click OK three times
    ...and you should be back in Regedit
    Close Regedit, and reboot

    Now run CheckSUR again, and we'll see how you did :)

    Then we'll deal with the other two keys...

    WARNING - These instructions apply ONLY to this poster, in this thread. Following them on your own machine WILL break things!
      My Computer


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

    ... all that just to delete three entries in a database! :)

    I need a drink!
      My Computer


  6. Posts : 18
    Windows Enterprise 64bit
    Thread Starter
       #16

    LOL, If you want just send me the next three lines, i will reuse the permission instructions from the previous post.

    I owe you at least a few few drinks.

    Here is the latest logs, seems to be getting smaller now
      My Computer


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

    Great - that looks fine so far.

    Here's the subkey and value listing....
    Still under the same Key....
    HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect


    Code:
    x86_microsoft-windows-printing-xpsprint_31bf3856ad364e35_0.0.0.0_none_cf7d18d759758b86
    Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-1_neutral_LDR
    Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-2_neutral_LDR
    Package_1_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.2522422-3_neutral_GDR
    Package_2_for_KB2522422~31bf3856ad364e35~amd64~~6.1.1.0.Trigger_1
    
    msil_system.windows.forms_b77a5c561934e089_6.1.0.0_none_0a57c6e724b6dfa9
    Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0.2518869-18_neutral_LDR
    Package_2_for_KB2518869~31bf3856ad364e35~amd64~~6.1.1.0.2518869-19_neutral_GDR
    run another CheckSUR after that, and we'll work on the Watchlist Packages next - same procedure :)
      My Computer


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

    I am going to have to figure out in these logs how you know what to delete. This is fun. Thanks
      My Computer


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

    Well done - that's eliminated the Components errors.
    Before I start you off on the Package errors, we'd better have a backup....
    Open an Elevated Command Prompt, and run the following commands

    Code:
    REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
    REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-NetFx2-ServerCore-OC-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
    REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-NetFx2-ServerCore-OC-WOW64-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
    REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
    REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-Printing-ServerCore-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
    REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\PackageDetect\Microsoft-Windows-UIAnimation-WinIP-Package~31bf3856ad364e35~amd64~~0.0.0.0" >>%userprofile%\desktop\npwpack.log
     
    .
    That will create a new npwpack.log file - which may be big enough to make it worth zipping before uploading (it's 68KB on my test machine)
    Upload it and I'll check things before I post the 'fix list'.
      My Computer


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

    p.s. You've got a very strange idea of fun! :)
      My Computer


 
Page 2 of 5 FirstFirst 1234 ... 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 06:22.
Find Us