none
IE 10 and 11 error install failure ERROR: "Neutral package installation failed"

    Question

  • This is a 2008 R2 physical server with all available patches installed and SFC recently run.

    00:00.000: ====================================================================
    00:00.000: Started: 2014/01/16 (Y/M/D) 11:52:19.750 (local)
    00:00.000: Time Format in this log: MM:ss.mmm (minutes:seconds.milliseconds)
    00:00.016: Command line: "C:\Users\{user}\Desktop\IE11-Windows6.1-x64-en-us.exe"
    00:00.016: INFO:    Setup installer for Internet Explorer: 11.0.9600.16428
    00:00.016: INFO:    Previous version of Internet Explorer: 9.0.8112.16526
    00:00.016: INFO:    Checking if iexplore.exe's current version is between 11.0.9600.0...
    00:00.016: INFO:    ...and 11.1.0.0...
    00:00.016: INFO:    Maximum version on which to run IEAK branding is: 11.1.0.0...
    00:00.016: INFO:    iexplore.exe version check success. Install can proceed.
    00:00.016: INFO:    Operating System: Windows Server: 6.1.7601 (Service Pack 1)
    00:00.016: INFO:    Trying to extract ID: SetupDownloadList.txt (0) as "SetupDownloadList.txt"
    00:00.016: INFO:    Trying to extract ID: HardwareBlockingList.xml (0) as "HardwareBlockingList.xml"
    00:00.016: INFO:    Trying to extract ID: 7006 (0) as "IE11-neutral.Extracted.cab"
    00:00.219: INFO:    Trying to extract ID: 5501 (1033) as "Spelling_en.msu"
    00:00.546: INFO:    Extracted Spelling dictionary for en to C:\Windows\TEMP\IE182A.tmp\Spelling_en.msu.
    00:00.546: INFO:    Trying to extract ID: 5502 (1033) as "Hyphenation_en.msu"
    00:00.562: INFO:    Extracted Hyphenation dictionary for en to C:\Windows\TEMP\IE182A.tmp\Hyphenation_en.msu.
    00:00.562: INFO:    Trying to extract ID: 7128 (1033) as "IE11-support.cab"
    00:01.467: INFO:    PauseOrResumeAUThread: Successfully paused Automatic Updates.
    00:01.810: INFO:    Updated Download list, Hardware Blocking list, and no reboot policy files successfully downloaded and extracted for use.
    00:01.826: INFO:    Launched program to check hardware: "C:\Windows\TEMP\IE182A.tmp\IE11-SUPPORT\IEXPLORE.EXE" /CheckHardware "C:\Windows\TEMP\IE182A.tmp\IE11-support\HardwareBlockingList.xml"
    00:01.919: INFO:    Hardware support check succeeded. Installation will continue.
    00:01.919: INFO:    Windows 7 operating system detected.
    00:01.919: INFO:    Service pack major: 1
    00:01.919: INFO:    Service pack minor: 0
    00:01.919: INFO:    Service pack name:  Service Pack 1
    00:01.935: INFO:    Version Check for (KB2834140) of C:\Windows\System32\d3d11.dll: 6.2.9200.16570 >= 6.2.9200.16570 (True)
    00:01.935: INFO:    Version Check for (KB2670838) of C:\Windows\System32\api-ms-win-downlevel-user32-l1-1-0.dll: 6.2.9200.16492 >= 6.2.9200.16426 (True)
    00:01.935: INFO:    Version Check for (KB2639308) of C:\Windows\System32\Ntoskrnl.exe: 6.1.7601.18247 >= 6.1.7601.17727 (True)
    00:01.966: INFO:    Version Check for (KB2533623) of C:\Windows\System32\api-ms-win-security-base-l1-1-0.dll: 6.1.7601.18229 >= 6.1.7601.17617 (True)
    00:01.966: INFO:    Version Check for (KB2731771) of C:\Windows\System32\conhost.exe: 6.1.7601.18229 >= 6.1.7601.17888 (True)
    00:01.966: INFO:    Checking for correct version of C:\Windows\Fonts\segoeui.ttf.
    00:01.966: INFO:    Version Check for (KB2786081) of C:\Windows\System32\taskhost.exe: 6.1.7601.18010 >= 6.1.7601.18010 (True)
    00:01.982: INFO:    Version Check for (KB2888049) of C:\Windows\System32\drivers\tcpip.sys: 6.1.7601.18254 >= 6.1.7601.18254 (True)
    00:02.013: INFO:    Version Check for (KB2882822) of C:\Windows\System32\tdh.dll: 6.1.7601.18247 >= 6.1.7601.18247 (True)
    00:54.258: INFO:    Waiting for 0 prerequisite downloads.
    00:54.258: INFO:    The neutral pack was not successfully downloaded from the internet. Installation will continue using the extracted package.
    00:54.258: INFO:    Waiting for 0 language pack downloads.
    00:54.258: INFO:    Language pack downloads completed. (exit code = 0xffffffff (4294967295)).
    00:54.273: INFO:    No reboot logic message NrApiStart(0), lParam=0x002a2778 returned 0x00000000.
    00:54.492: INFO:    No reboot logic message NrApiScan(1), lParam=0x00000001 returned 0x00000000.
    00:54.492: INFO:    No reboot logic message NrApiStartInstall(4), lParam=0x00000001 returned 0x00000014.
    00:54.492: INFO:    Installing with the extracted package. C:\Windows\TEMP\IE182A.tmp\IE11-neutral.Extracted.cab
    00:54.492: INFO:    Launched package installation: C:\Windows\SysNative\dism.exe /online /add-package /packagepath:C:\Windows\TEMP\IE182A.tmp\IE11-neutral.Extracted.cab /quiet /norestart
    01:21.792: INFO:    Process exit code 0x00000002 (2) [The system cannot find the file specified. ]
    01:21.792: ERROR:   Neutral package installation failed (exit code = 0x00000002 (2)).
    01:21.792: INFO:    No reboot logic message NrApiInstallDone(7), lParam=0x00009c59 returned 0x00000000.
    01:21.792: INFO:    No reboot logic message NrApiStartFinish(11), lParam=0x00000000 returned 0x00000000.
    01:21.807: INFO:    No reboot logic message NrApiFinish(12), lParam=0x00000000 returned 0x00000016.
    01:21.807: INFO:    Waiting for Active Setup to complete.
    01:21.807: INFO:    Waiting for Active Setup to complete. ({89820200-ECBD-11cf-8B85-00AA005B4383})
    01:26.815: INFO:    Waiting for Active Setup to complete. ({89820200-ECBD-11cf-8B85-00AA005B4383})
    01:31.823: INFO:    Waiting for Active Setup to complete. ({89820200-ECBD-11cf-8B85-00AA005B4383})
    01:37.298: INFO:    Waiting for Active Setup to complete. ({89820200-ECBD-11cf-8B85-00AA005B4383})
    01:42.306: INFO:    Waiting for Active Setup to complete. ({89820200-ECBD-11cf-8B85-00AA005B4383})
    01:47.314: INFO:    Waiting for Active Setup to complete. ({A509B1A7-37EF-4b3f-8CFC-4F3A74704073})


    • Edited by strhow Thursday, January 16, 2014 6:38 PM typo
    Thursday, January 16, 2014 6:30 PM

Answers

  • Hello!

    Sorry for refresh this old question, but...

    Finally i've got solution in my situation! =)

    I have Windows 2008 Server R2 SP1.

    When i tried to install IE10, i've got this error in CBS.log:

    Failed to find file: amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_6.1.7600.21238_none_a51187a7608a895d\vbscript.dll

    Steps to correct this error:

    1. Download this: "Security Update for Windows Server 2008 R2 x64 Edition (KB2706045)"

    2. Don't try to install, it wouldn't =)

    3. Extract all files:

    AMD64-all-windows6.1-kb2706045-x64_ffc82084794531c27bd4a670408d2c4a4d038ad8.msu /extract:.

    4. Run this:

    dism.exe /online /add-package /packagepath:Windows6.1-KB2706045-x64.cab

    5. Now you can try to install IE10.

    P.S. I think with IE11 problem will be solve in this way too . =)


    Tuesday, June 23, 2015 7:59 AM
  • Thanks for your time. I'm going to engage MS support to get this resolved.
    • Marked as answer by strhow Thursday, January 30, 2014 4:07 PM
    Thursday, January 30, 2014 4:07 PM

All replies

  • Hi,

    Form your log, we consider the culprit is the Neutral package.

    We suggest you manually remove the C:\Windows\TEMP\IE16B6F.tmp file, remove the whole Internet Explorer download package.

    Then download the correct installer version form this article below(Step 4) to reinstall:

    Can't install Internet Explorer 10 in Windows 7 SP1 or Windows Server 2008 R2 SP1

    http://support.microsoft.com/kb/2820688


    Karen Hu
    TechNet Community Support

    Monday, January 20, 2014 9:19 AM
    Moderator
  • all available patches installed


    The last poster I have tried to help who made this claim seems to have been mistaken.  Please use the Powershell method to check yours too (e.g. using ieframe.dll as an example)

    http://answers.microsoft.com/en-us/ie/forum/ie9-windows_7/uninstalling-ie9-does-not-complete/e7d50efe-4e1c-4666-bffa-394c468d6666#LastReply

    Or if you really do have "all available patches" I'm still trying to understand exactly why Greg Ashley's method worked for him (link for that in my first reply in the above thread).

     
    HTH



    Robert Aldwinckle
    ---

    Monday, January 20, 2014 9:53 PM
    Answerer
  • I do not have the folder C:\Windows\TEMP\IE16B6F.tmp. I downloaded and ran the software and got the same result.
    Monday, January 20, 2014 10:13 PM
  • MS update is only offering me IE 10 and 11 to install, no other updates. And I am currently on IE9.

    I found IEFRAME.DLL manually and the version is 9.0.8112.16526

    Also Powershell:

    8.00.7600.16385 (win7_rtm.090713-1255)     C:\Windows\winsxs\amd64_microsoft
    8.00.7600.16385 (win7_rtm.090713-1255)     C:\Windows\winsxs\wow64_microsoft
    8.00.7600.17115 (win7_gdr.120824-0331)     C:\Windows\winsxs\amd64_microsoft
    8.00.7600.17115 (win7_gdr.120824-0331)     C:\Windows\winsxs\wow64_microsoft
    8.00.7600.21313 (win7_ldr.120824-0332)     C:\Windows\winsxs\amd64_microsoft
    8.00.7600.21313 (win7_ldr.120824-0332)     C:\Windows\winsxs\wow64_microsoft
    8.00.7601.17514 (win7sp1_rtm.101119-1850)  C:\Windows\winsxs\amd64_microsoft
    8.00.7601.17514 (win7sp1_rtm.101119-1850)  C:\Windows\winsxs\wow64_microsoft
    8.00.7601.17940 (win7sp1_gdr.120824-0334)  C:\Windows\winsxs\amd64_microsoft
    8.00.7601.17940 (win7sp1_gdr.120824-0334)  C:\Windows\winsxs\wow64_microsoft
    8.00.7601.22099 (win7sp1_ldr.120824-0334)  C:\Windows\winsxs\amd64_microsoft
    8.00.7601.22099 (win7sp1_ldr.120824-0334)  C:\Windows\winsxs\wow64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\System32\ieframe.dll
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\SysWOW64\ieframe.dll
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft

    Monday, January 20, 2014 10:56 PM
  • I found IEFRAME.DLL manually and the version is 9.0.8112.16526


    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft

    That's December (apparently, the latest so far).  For clarity did you increase the width of your Powershell window so you can show the entire path?  Note that the FileVersion is only being represented by a ProductVersion, which is inconclusive.  You can use Insert Code Block to ensure that data is not truncated or wrapped. 

    So, if  ieframe.dll  in %windir% is up-to-date perhaps ieframe.dll was a bad guess and you will have to find some other module there which satisfies the conditions that Greg Ashley had for his procedure?   ; )

     

    Good luck



    Robert Aldwinckle
    ---

    Tuesday, January 21, 2014 5:48 AM
    Answerer
  • Thanks for the tip. I have removed the v8 references.

      

    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\System32\ieframe.dll
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\SysWOW64\ieframe.dll
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\amd64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...
    9.00.8112.16421 (WIN7_IE9_RTM.110308-0330) C:\Windows\winsxs\wow64_microsoft-windows-ieframe_31bf3856ad364e35_9.4.81...

    Tuesday, January 21, 2014 3:59 PM
  • ieframe_31bf3856ad364e35_9.4.81...

    [still not seeing full file path]  


    The Powershell window size is still too narrow.  One thing that may be significant is that your versions are being stored as  9.4.8100.  Oh.  No.  I have that too, even though I'm not using IE9.

    But the most significant thing I imagine is how many you have showing with that common ProductVersion.   FWIW I don't have that.  I have a lot more patches which start with  9.00.8112 but only 2 (1 each) which end with the (WIN7_IE9_RTM.110308-0330)

    Hopefully Karen or someone else knows what the significance of these facts may mean.

    On a different tack you could do what others have done and find out where in CBS.log the problem which is being reported (e.g. via return code) is discovered.  Doing that may help you find a discrepancy which you could list using the above Powershell pipeline (appropriately sized, of course <w>).  Be aware though that there does not seem to be any commonality on the module name found that way.  More importantly, I still contend that the problem being reported is far beyond where the real problem is occurring.   E.g. (I'm imagining) for some reason it gets into a (broken) recovery routine and it is a break there which is being reported, ignoring the real problem which puts you into the recovery routine in the first place.  Again, since I don't know how to "read between the lines" I would be using ProcMon to try correlating all the log messages that are being generated.

     
    HTH



    Robert Aldwinckle
    ---

    • Marked as answer by 暁北Moderator Wednesday, January 29, 2014 2:40 PM
    • Unmarked as answer by strhow Wednesday, January 29, 2014 3:01 PM
    Tuesday, January 21, 2014 6:32 PM
    Answerer
  • My CBS.log shows

    Info                  CBS    Failed to find file: amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_6.1.7600.21238_none_a51187a7608a895d\vbscript.dll [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    I do not have this folder in WINSXS even though I do have a manifest in WINSXS that matches this version number. Still investigating.

    Wednesday, January 29, 2014 3:22 PM
  • My CBS.log shows

    Info                  CBS    Failed to find file: amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_6.1.7600.21238_none_a51187a7608a895d\vbscript.dll [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
    I do not have this folder in WINSXS even though I do have a manifest in WINSXS that matches this version number. Still investigating.

    Great.   So, now what happens if you use the Powershell pipeline with that vbscript  file as its argument (instead of ieframe)?

    PS C:\> cd $env:windir

    PS C:\Windows> DIR -FILTER vbscript.DLL -RECURSE -NAME | get-item | select -expandproperty VersionInfo | sort-object FileVersion, FileName  |  ft FileVersion, FileName -Autosize

    And let's look at the update which is implied by the version implied by that filename:  6.1.7600.21238

    August 2012?

    http://support.microsoft.com/kb/2706045/en-us

    Ah.  The leading 2 means it is an LDR version.  So, it might be a hotfix that you had installed.

    I don't have it?  Ah.  The associated TechNet article indicates my OS is in the "Non-affected software" category.   I have W7sp1 and W8.1.

    And again, I'm finding that this is showing ProductVersion instead of FileVersion for the modules I have installed in  System32 and SysWOW64 so I need to use  get-item  on those modules to infer the actual FileVersion involved there.  (I.e., no clue about the actual version from the File path and the only confirming details are the Length and CreationTime.)   For example, use:

    PS C:\Windows> get-item -path ".\SysWOW64\vbscript.dll" | fl *

     

    HTH



    Robert Aldwinckle
    ---

    Wednesday, January 29, 2014 8:52 PM
    Answerer
  • PS C:\Windows> DIR -FILTER vbscript.DLL -RECURSE -NAME | get-item | select -expandproperty VersionInfo | sort-object FileVersion, FileName  |  ft File
    Version, FileName -Autosize
    
    FileVersion    FileName
    -----------    --------
    5.8.7601.16978 C:\Windows\System32\vbscript.dll
    5.8.7601.16978 C:\Windows\SysWOW64\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_6.1.7600.16385_none_a44ef4f6479809f0\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_6.1.7601.17514_none_a68008be44868d8a\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.16450_none_bcd6d18300a40070\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.16455_none_bcdbd2f5009f7f23\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.16476_none_bcc7336700aed05c\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.16526_none_bcfd44e9008641ce\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.20562_none_bd579ef619c7eed9\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.20586_none_bd46004619d48c17\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.20637_none_bd7d121219ab16e0\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_6.1.7600.16385_none_aea39f487bf8cbeb\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_6.1.7601.17514_none_b0d4b31078e74f85\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.16450_none_c72b7bd53504c26b\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.16455_none_c7307d473500411e\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.16476_none_c71bddb9350f9257\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.16526_none_c751ef3b34e703c9\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.20562_none_c7ac49484e28b0d4\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.20586_none_c79aaa984e354e12\vbscript.dll
    5.8.7601.16978 C:\Windows\winsxs\wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.20637_none_c7d1bc644e0bd8db\vbscript.dll
    
    
    PS C:\Windows> get-item -path ".\SysWOW64\vbscript.dll" | fl *
    
    
    PSPath            : Microsoft.PowerShell.Core\FileSystem::C:\Windows\SysWOW64\vbscript.dll
    PSParentPath      : Microsoft.PowerShell.Core\FileSystem::C:\Windows\SysWOW64
    PSChildName       : vbscript.dll
    PSDrive           : C
    PSProvider        : Microsoft.PowerShell.Core\FileSystem
    PSIsContainer     : False
    VersionInfo       : File:             C:\Windows\SysWOW64\vbscript.dll
                        InternalName:     vbscript.dll
                        OriginalFilename: vbscript.dll.mui
                        FileVersion:      5.8.7601.16978
                        FileDescription:  Microsoft r VBScript
                        Product:          Microsoft r VBScript
                        ProductVersion:   5.8.7601.16978
                        Debug:            False
                        Patched:          False
                        PreRelease:       False
                        PrivateBuild:     False
                        SpecialBuild:     False
                        Language:         English (United States)
    
    BaseName          : vbscript
    Mode              : -a---
    Name              : vbscript.dll
    Length            : 420864
    DirectoryName     : C:\Windows\SysWOW64
    Directory         : C:\Windows\SysWOW64
    IsReadOnly        : False
    Exists            : True
    FullName          : C:\Windows\SysWOW64\vbscript.dll
    Extension         : .dll
    CreationTime      : 1/15/2014 2:37:08 PM
    CreationTimeUtc   : 1/15/2014 7:37:08 PM
    LastAccessTime    : 1/15/2014 2:37:08 PM
    LastAccessTimeUtc : 1/15/2014 7:37:08 PM
    LastWriteTime     : 11/14/2013 5:38:16 PM
    LastWriteTimeUtc  : 11/14/2013 10:38:16 PM
    Attributes        : Archive

    Thursday, January 30, 2014 1:50 PM
  • PS C:\Windows> DIR -FILTER vbscript.DLL -RECURSE -NAME | get-item | select -expandproperty VersionInfo | sort-object FileVersion, FileName | ft File Version, FileName -Autosize FileVersion FileName ----------- -------- 5.8.7601.16978 C:\Windows\System32\vbscript.dll 5.8.7601.16978 C:\Windows\SysWOW64\vbscript.dll

    5.8.7601.16978 C:\Windows\winsxs\amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.16526_none_bcfd44e9008641ce\vbscript.dll

    5.8.7601.16978 C:\Windows\winsxs\wow64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_9.4.8112.16526_none_c751ef3b34e703c9\vbscript.dll PS C:\Windows> get-item -path ".\SysWOW64\vbscript.dll" | fl * VersionInfo : File: C:\Windows\SysWOW64\vbscript.dll InternalName: vbscript.dll OriginalFilename: vbscript.dll.mui FileVersion: 5.8.7601.16978

    ProductVersion: 5.8.7601.16978

    Name : vbscript.dll Length : 420864 DirectoryName : C:\Windows\SysWOW64 Directory : C:\Windows\SysWOW64 IsReadOnly : False Exists : True FullName : C:\Windows\SysWOW64\vbscript.dll

    LastWriteTime : 11/14/2013 5:38:16 PM


    I'd be tempted to try Greg Ashley's trick with this.  E.g. where is the saved copy of 5.8.7601.16978?  So, what would you get if you deleted/renamed vbscript.dll from both  System32 and SysWOW64?  A guess would be that 9.4.8112.16526, the latest GDR version in WinSxS, would be used to replace the missing module.  In fact when you look at the length and time attributes, it seems that you do have the latest for IE9 (e.g. from the December cumulative update), so except for putting the FUBAR FileVersion naming through a different logic path that might not accomplish anything more in terms of getting the problem update installed.  Sure would be nice to have some source and documentation to avoid all this speculation.  Isn't closed source software support wonderful?



    Robert Aldwinckle
    ---

    Edit:  Oops.  I should have left in the latest GDR version for X64 too.  Fixed in an amended quote.

    Edit:  Clarity.  Idea is to delete/rename modules in Sys dir's and see if A) WinSxS version replacement works and B) if it does anything to solve the original problem symptom of not being able to install a higher version of IE.

    Thursday, January 30, 2014 3:07 PM
    Answerer
  • Thanks for your time. I'm going to engage MS support to get this resolved.
    • Marked as answer by strhow Thursday, January 30, 2014 4:07 PM
    Thursday, January 30, 2014 4:07 PM
  • Thanks for your time. I'm going to engage MS support to get this resolved.

    You're welcome.

    BTW others are hoping that you will post your resolution.   ; )

    C.f.

    http://answers.microsoft.com/en-us/ie/forum/ie10-windows_7/error-code-9c57-when-installing-ie11/d7772ab6-1622-4c80-acd3-403d339b1287



    Robert Aldwinckle
    ---

    Thursday, February 6, 2014 8:20 AM
    Answerer
  • Hello!

    Sorry for refresh this old question, but...

    Finally i've got solution in my situation! =)

    I have Windows 2008 Server R2 SP1.

    When i tried to install IE10, i've got this error in CBS.log:

    Failed to find file: amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_6.1.7600.21238_none_a51187a7608a895d\vbscript.dll

    Steps to correct this error:

    1. Download this: "Security Update for Windows Server 2008 R2 x64 Edition (KB2706045)"

    2. Don't try to install, it wouldn't =)

    3. Extract all files:

    AMD64-all-windows6.1-kb2706045-x64_ffc82084794531c27bd4a670408d2c4a4d038ad8.msu /extract:.

    4. Run this:

    dism.exe /online /add-package /packagepath:Windows6.1-KB2706045-x64.cab

    5. Now you can try to install IE10.

    P.S. I think with IE11 problem will be solve in this way too . =)


    Tuesday, June 23, 2015 7:59 AM
  • Hello!

    Sorry for refresh this old question, but...

    Finally i've got solution in my situation! =)

    I have Windows 2008 Server R2 SP1.

    When i tried to install IE10, i've got this error in CBS.log:

    Failed to find file: amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_6.1.7600.21238_none_a51187a7608a895d\vbscript.dll

    Steps to correct this error:

    1. Download this: "Security Update for Windows Server 2008 R2 x64 Edition (KB2706045)"

    2. Don't try to install, it wouldn't =)

    3. Extract all files:

    AMD64-all-windows6.1-kb2706045-x64_ffc82084794531c27bd4a670408d2c4a4d038ad8.msu /extract:.

    4. Run this:

    dism.exe /online /add-package /packagepath:Windows6.1-KB2706045-x64.cab

    5. Now you can try to install IE10.

    P.S. I think with IE11 problem will be solve in this way too . =)


    Thanks, helped me alot.
    Tuesday, August 11, 2015 8:24 AM
  • Hello!

    Sorry for refresh this old question, but...

    Finally i've got solution in my situation! =)

    I have Windows 2008 Server R2 SP1.

    When i tried to install IE10, i've got this error in CBS.log:

    Failed to find file: amd64_microsoft-windows-scripting-vbscript_31bf3856ad364e35_6.1.7600.21238_none_a51187a7608a895d\vbscript.dll

    Steps to correct this error:

    1. Download this: "Security Update for Windows Server 2008 R2 x64 Edition (KB2706045)"

    2. Don't try to install, it wouldn't =)

    3. Extract all files:

    AMD64-all-windows6.1-kb2706045-x64_ffc82084794531c27bd4a670408d2c4a4d038ad8.msu /extract:.

    4. Run this:

    dism.exe /online /add-package /packagepath:Windows6.1-KB2706045-x64.cab

    5. Now you can try to install IE10.

    P.S. I think with IE11 problem will be solve in this way too . =)


    Holy crap!! I've spent two weeks searching forums for why I couldn't get IE11 to install on 3 of my servers (long overdue, don't ask... I inherited a mess, lolol...) and I finally came across this. Voila--- it works! Thank you!
    Tuesday, July 25, 2017 8:27 PM
  • OMG Thankyou I have have spent days trying to get this sorted on our server,finding the same old steps time and time again, this is the real answer to the problem :)
    Friday, March 30, 2018 5:47 PM