locked
Can't upgrade from IE8 to either IE9 or IE10 RRS feed

  • Question

  • I have a Windows 2008 R2 Standard server.  I had to dowgrade IE9 to IE8 which was successful, but now I cannot successfully upgrade either IE9 or IE10.  Whenever I try, I get the following
    message.

    Internet Explorer did not finish installing
    For more information, see the Internet Explorer Troubleshooter

    I've gone through all of the recommendations, installed all of the updates and
    still no success.  I've turned off my AntiVirus program, but still no good.  I've waited days and tried again with no success

    I'm hoping that you can help me to get either IE9 or IE10 installed.

    Thursday, February 6, 2014 5:01 PM

Answers

  • Hi,

    What version is your OS? 64bit or 32bit?

    Locate to %WINDIR%\servicing\Packages , and check if there exist any components related to IE 9 or IE 10.

    Type cd %WINDIR%\servicing\Packages in cmd, press Enter and then dir Microsoft-Windows-InternetExplorer-*.*.mum

    If there exist, please uninstall them and reinstall again.

    You can attempt to manually download and install IE 9.

    http://windows.microsoft.com/en-us/internet-explorer/ie-9-worldwide-languages


    Andy Altmann
    TechNet Community Support

    • Marked as answer by Cloud_TS Tuesday, February 25, 2014 3:24 AM
    Sunday, February 9, 2014 5:24 AM
  • I found the IE9 installation log and am including it below.  It exits with an Process exit code 0x0000007E (126) [The specified module could not be found.  Does this provide any additional clues?

    It's the same cause with a new code.  Note that "the specified module" is not specified?  That's the same problem that everyone else who tries to diagnose these symptoms has, trying to find some specific details which can explain the symptom.  So then you look into some of the other logs and their entries from the same events, such as the already mentioned CBS.log, and then you find that it is an indication that your WinSxS doesn't have a file that the install process thought it should have.  But if you look more closely you will see that what is happening has nothing to do with your install but some kind of recovery from a failure of it.  So far, I don't think anyone has been able to unravel their symptoms back far enough to know why that is happening, e.g. why a recovery procedure is being invoked.   However, it is surprising how often at this stage that it is found that the poster's maintenance is not current, so for this reason I think it is useful to go through that analysis.

    Otherwise, if you want to try to go further than that you should run ProcMon to capture a trace of all of the various diagnostics that are being made, e.g. so you can see how they all correlate.  Note that another advantage of having a ProcMon trace is that you will also have any preceding registry and file accesses, which may help people who don't have access to source or support documentation to be able to try to "read between the lines" and perhaps understand what the log messages really signify.



    Robert Aldwinckle
    ---

    • Marked as answer by Cloud_TS Tuesday, February 25, 2014 3:24 AM
    Sunday, February 9, 2014 6:19 AM
    Answerer

All replies

  • Hi,

    how many times did you have to reboot the machine?

    Start>Event Viewer.... the upgrade from 8 to 10 may require a number of reboots and incremental windows updates.


    Rob^_^

    Friday, February 7, 2014 12:19 AM
  • The system was rebooted after each update session so that all of the updates would be applied and made functional.  Since then, the system has been rebooted at least once.  I've tried to upgrade IE from IE8 to just IE9, but it gives me the same results, exactly.  I'm tempted to uninstall IE8, reboot  the system, then try to install IE9,but I'm concerned that if I do that, I won't have IE at all.

    Friday, February 7, 2014 3:38 PM
  • I've checked the Event Viewed and found that each time I tried to upgrade IE8 to IE9 I received three informational entries all of which were associated with Restart Manager:

    1. Starting Session 1 (Event ID 10000)

    2.  Machine restart Required (Event ID 10005)

    3.  End Session 1 (Event ID 10001)

    The previous reboots were all soft boots, so I shut the server down and performed a hard boot.

    Then tried to install IE9 again, with the same negative results

    Level Date and Time Source Event ID Task Category Log Computer
    Information 2/7/2014 11:44 Microsoft-Windows-RestartManager 10001 None Application RBASLANCDC002.bouchard.local Ending session 1 started ‎2014‎-‎02‎-‎07T16:44:37.471876600Z.
    Information 2/7/2014 11:44 Microsoft-Windows-RestartManager 10005 None Application RBASLANCDC002.bouchard.local Machine restart is required.
    Information 2/7/2014 11:44 Microsoft-Windows-RestartManager 10000 None Application RBASLANCDC002.bouchard.local Starting session 1 - ‎2014‎-‎02‎-‎07T16:44:37.471876600Z.
    Friday, February 7, 2014 4:44 PM
  • Internet Explorer did not finish installing
    For more information, see the Internet Explorer Troubleshooter

    Really?  What did that show?   People with this symptom who want to try a diagnostic tack have had to go into CBS.log with (AFAIK) inconclusive results.  Otherwise reinstalling the OS seems to be the most effective one with the least effort.  Typically the symptom seems to indicate unrecoverable corruption in the WinSxS cache.

    See this thread where we are hoping there may yet be a more positive resolution.

    http://social.technet.microsoft.com/Forums/ie/en-US/4481f143-8f0d-46a5-a023-b04ab3e1a5a1/ie-10-and-11-error-install-failure-error-neutral-package-installation-failed?forum=ieitprocurrentver

     
    FYI



    Robert Aldwinckle
    ---

    Saturday, February 8, 2014 3:58 PM
    Answerer
  • I found the IE9 installation log and am including it below.  It exits with an Process exit code 0x0000007E (126) [The specified module could not be found.  Does this provide any additional clues?

    00:00.000: Started: 2014/02/07 (Y/M/D) 11:44:33.166 (local)
    00:00.016: Time Format in this log: MM:ss.mmm (minutes:seconds.milliseconds)
    00:00.016: Command line: "C:\Users\administrator.BOUCHARD\Desktop\IE9-Windows7-x64-enu.exe"
    00:00.016: INFO:    Setup installer for Internet Explorer: 9.0.8112.16421
    00:00.016: INFO:    Previous version of Internet Explorer: 8.0.7601.18305
    00:00.016: INFO:    Checking if iexplore.exe's current version is between 9.0.6001.0...
    00:00.016: INFO:    ...and 9.1.0.0...
    00:00.031: INFO:    Maximum version on which to run IEAK branding is: 9.1.0.0...
    00:00.031: INFO:    iexplore.exe version check success. Install can proceed.
    00:00.031: INFO:    Trying to extract ID: 7006 (0) as "IE9-neutral.Extracted.cab"
    00:00.109: INFO:    Trying to extract ID: 5006 (0) as "IE9-support.cab"
    00:00.640: INFO:    Operating System: Windows Server: 6.1.7601 (Service Pack 1)
    00:00.640: INFO:    Windows 7 operating system detected.
    00:00.640: INFO:    Service pack major: 1
    00:00.655: INFO:    Service pack minor: 0
    00:00.655: INFO:    Service pack name:  Service Pack 1
    00:00.671: INFO:    PauseOrResumeAUThread: Successfully paused Automatic Updates.
    00:04.197: INFO:    The neutral pack was successfully downloaded from the internet. Installation will continue using the downloaded package.
    00:04.212: INFO:    No reboot policy and supplemental files successfully downloaded and extracted for use.
    00:04.228: INFO:    No reboot logic message NrApiStart(0), lParam=0x00366630 returned 0x00000000.
    00:04.555: INFO:    No reboot logic message NrApiScan(1), lParam=0x00000001 returned 0x00000000.
    00:04.555: INFO:    No reboot logic message NrApiStartInstall(4), lParam=0x00000001 returned 0x00000014.
    00:04.555: INFO:    Installing with the downloaded package. C:\Windows\TEMP\IE94D93.tmp\IE9-neutral.Downloaded.msu
    00:04.665: INFO:    Launched package installation: C:\Windows\system32\dism.exe /online /add-package /packagepath:C:\Windows\TEMP\IE94D93.tmp\IE9-neutral.Downloaded\Windows6.1-KB982861-x64.cab /quiet /norestart
    00:04.680: INFO:    Process exit code 0x0000007E (126) [The specified module could not be found. ]
    00:04.680: ERROR:   Neutral MSU installation failed (exit code = 0x0000007e (126)).
    00:04.680: INFO:    No reboot logic message NrApiInstallDone(7), lParam=0x0000007e returned 0x00000000.
    00:04.680: INFO:    No reboot logic message NrApiStartFinish(11), lParam=0x00000000 returned 0x00000000.
    00:04.680: INFO:    No reboot logic message NrApiFinish(12), lParam=0x00000000 returned 0x00000016.
    00:04.711: INFO:    PauseOrResumeAUThread: Successfully resumed Automatic Updates.
    00:06.147: INFO:    Setup exit code 0x0000007E (126) [The specified module could not be found. ]
    00:06.162: INFO:    Cleaning up temporary files in: C:\Windows\TEMP\IE94D93.tmp
    00:06.193: INFO:    Unable to remove directory C:\Windows\TEMP\IE94D93.tmp, marking for deletion on reboot.
    00:06.193: INFO:    Released Internet Explorer Installer Mutex

    Saturday, February 8, 2014 10:59 PM
  • Hi,

    What version is your OS? 64bit or 32bit?

    Locate to %WINDIR%\servicing\Packages , and check if there exist any components related to IE 9 or IE 10.

    Type cd %WINDIR%\servicing\Packages in cmd, press Enter and then dir Microsoft-Windows-InternetExplorer-*.*.mum

    If there exist, please uninstall them and reinstall again.

    You can attempt to manually download and install IE 9.

    http://windows.microsoft.com/en-us/internet-explorer/ie-9-worldwide-languages


    Andy Altmann
    TechNet Community Support

    • Marked as answer by Cloud_TS Tuesday, February 25, 2014 3:24 AM
    Sunday, February 9, 2014 5:24 AM
  • I found the IE9 installation log and am including it below.  It exits with an Process exit code 0x0000007E (126) [The specified module could not be found.  Does this provide any additional clues?

    It's the same cause with a new code.  Note that "the specified module" is not specified?  That's the same problem that everyone else who tries to diagnose these symptoms has, trying to find some specific details which can explain the symptom.  So then you look into some of the other logs and their entries from the same events, such as the already mentioned CBS.log, and then you find that it is an indication that your WinSxS doesn't have a file that the install process thought it should have.  But if you look more closely you will see that what is happening has nothing to do with your install but some kind of recovery from a failure of it.  So far, I don't think anyone has been able to unravel their symptoms back far enough to know why that is happening, e.g. why a recovery procedure is being invoked.   However, it is surprising how often at this stage that it is found that the poster's maintenance is not current, so for this reason I think it is useful to go through that analysis.

    Otherwise, if you want to try to go further than that you should run ProcMon to capture a trace of all of the various diagnostics that are being made, e.g. so you can see how they all correlate.  Note that another advantage of having a ProcMon trace is that you will also have any preceding registry and file accesses, which may help people who don't have access to source or support documentation to be able to try to "read between the lines" and perhaps understand what the log messages really signify.



    Robert Aldwinckle
    ---

    • Marked as answer by Cloud_TS Tuesday, February 25, 2014 3:24 AM
    Sunday, February 9, 2014 6:19 AM
    Answerer