none
MSIE installaton failure - via WSUS RRS feed

  • Question

  • Hey Folks,

    Wondering if there is someone who can pinpoint an issue we're having rolling out Internet Explorer v11 for Windows 7 at my company?

    Situation is that we approved it in WSUS Monday (07/07) and it proceeded to fail installing on PCs royally.

    Did some digging and found prerequisite info here: http://support.microsoft.com/kb/2847882/en-us . Have followed this and used my own PC as a testbed. Missing were the "Platform Update" (2670838) and supposedly the "Segoe UI symbol font" (2729094). Installed the platform update without incident. However, when attempting to install the symbol font, the standalone installer informed me that the update was already installed. Can find nothing about it listed in my installed updates - AND the IE v11 installer complains that the font update is missing.

    Took things a little further and used the /uninstall switch of 2729094 standalone package to remove from Windows whatever it thought was present. Then the installer proceeded to install this update, rebooted, and it is now in the list of installed updates.

    Below is the most recent snippet I have from C:\Windows\IE11_main.log. I did note the the KB2729094 package seems to be a "v2". wondering if that add'l info in its string is somehow throwing off the IE v11 installer?

    Have not yet looked into the WMI message below, but wanted to post this out there in hopes that the answer exists... thanks!!

    -Tom W.

    00:00.000: ====================================================================

    00:01.170: Started: 2014/07/08 (Y/M/D) 18:19:46.399 (local)

    00:01.232: Time Format in this log: MM:ss.mmm (minutes:seconds.milliseconds)

    00:01.279: Command line: "C:\Windows\SoftwareDistribution\Download\Install\IE11-Windows6.1-x86-en-us.exe" /WSUS

    00:01.341: INFO:    Setup installer for Internet Explorer: 11.0.9600.16428

    00:01.435: INFO:    Previous version of Internet Explorer: 9.0.8112.16555

    00:01.529: INFO:    Checking if iexplore.exe's current version is between 11.0.9600.0...

    00:01.575: INFO:    ...and 11.1.0.0...

    00:01.607: INFO:    Maximum version on which to run IEAK branding is: 11.1.0.0...

    00:01.638: INFO:    iexplore.exe version check success. Install can proceed.

    00:01.669: INFO:    Operating System: Windows Workstation: 6.1.7601 (Service Pack 1)

    00:01.700: INFO:    Trying to extract ID: SetupDownloadList.txt (0) as "SetupDownloadList.txt"

    00:01.747: INFO:    Trying to extract ID: HardwareBlockingList.xml (0) as "HardwareBlockingList.xml"

    00:01.794: INFO:    Trying to extract ID: 6006 (0) as "IE11-neutral.Extracted.cab"

    00:03.307: INFO:    Trying to extract ID: 5501 (1033) as "Spelling_en.msu"

    00:03.541: INFO:    Extracted Spelling dictionary for en to C:\Windows\TEMP\IE13D3E.tmp\Spelling_en.msu.

    00:03.572: INFO:    Trying to extract ID: 5502 (1033) as "Hyphenation_en.msu"

    00:03.619: INFO:    Extracted Hyphenation dictionary for en to C:\Windows\TEMP\IE13D3E.tmp\Hyphenation_en.msu.

    00:03.666: INFO:    Trying to extract ID: 6128 (1033) as "IE11-support.cab"

    00:04.524: INFO:    Launched program to check hardware: "C:\Windows\TEMP\IE13D3E.tmp\IE11-SUPPORT\IEXPLORE.EXE" /CheckHardware "C:\Windows\TEMP\IE13D3E.tmp\HardwareBlockingList.xml"

    00:05.772: INFO:    Hardware support check succeeded. Installation will continue.

    00:05.803: INFO:    Windows 7 operating system detected.

    00:05.834: INFO:    Service pack major: 1

    00:05.881: INFO:    Service pack minor: 0

    00:05.928: INFO:    Service pack name:  Service Pack 1

    00:05.975: INFO:    Version Check for (KB2834140) of C:\Windows\System32\d3d11.dll: 6.2.9200.16570 >= 6.2.9200.16570 (True)

    00:06.006: 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:06.037: INFO:    Version Check for (KB2639308) of C:\Windows\System32\Ntoskrnl.exe: 6.1.7601.18409 >= 6.1.7601.17727 (True)

    00:06.084: 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:06.115: INFO:    Version Check for (KB2731771) of C:\Windows\System32\conhost.exe: 6.1.7601.18229 >= 6.1.7601.17888 (True)

    00:06.162: INFO:    Checking for correct version of C:\Windows\Fonts\segoeui.ttf.

    00:06.193: INFO:    Version Check for (KB2786081) of C:\Windows\System32\taskhost.exe: 6.1.7601.18010 >= 6.1.7601.18010 (True)

    00:06.256: INFO:    Version Check for (KB2888049) of C:\Windows\System32\drivers\tcpip.sys: 6.1.7601.18438 >= 6.1.7601.18254 (True)

    00:06.302: INFO:    Version Check for (KB2882822) of C:\Windows\System32\tdh.dll: 6.1.7601.18247 >= 6.1.7601.18247 (True)

    00:06.349: WARNING: WMI Query verification of the prerequisite download packages failed. Error: 0x80041001 (2147749889)

    00:06.396: INFO:    KB2729094 could not be download is not installed.

    00:06.458: ERROR:   Couldn't create setup troubleshooting shortcut on the desktop. HRESULT: 0x80070002,

    00:06.474: INFO:    Setup exit code: 0x00009C47 (40007) - Required updates failed to download.

    00:06.552: INFO:    Cleaning up temporary files in: C:\Windows\TEMP\IE13D3E.tmp

    00:06.630: INFO:    Unable to remove directory C:\Windows\TEMP\IE13D3E.tmp, marking for deletion on reboot.

    00:06.708: INFO:    Released Internet Explorer Installer Mutex


    JTW

    Wednesday, July 9, 2014 1:55 PM

Answers

  • GOOD NEWS!!

    Our issue boiled down to a missing registry value and also (2) modifications for good measure:

    First and foremost, we believe that the entirely missing REG_EXPAND_SZ value of "Working Directory" needed to contain "%systemroot%\System32\wbem" within [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM].

    Second (within [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM]. ) we removed "the REG_SZ value for "Repository Directory" and added the same as REG_EXPAND_SZ with a value of "%systemroot%\System32\wbem\Repository" or an absolute path.

    Third, we changed the Logging value from "0" to "1".

    We discovered the 2nd item near the very bottom of this posting: http://blogs.technet.com/b/askperf/archive/2012/03/09/unable-to-connect-to-wmi-locally-win32-the-system-cannot-find-the-path-specified.aspx

    During the course of experimenting with WMIDiag v2.2 (which has a bug in the VBS file - a value of 6.0 must be changed to 6.1 to support Windows versions beyond Vista), we discovered item #s 1 & 3 as recommendations from the output file.

    As a result of these changes and a reboot, our WMI now reports correct system and service dependency information. Our MSIE v11 as dished out by WSUS is now succeeding. We believe that the faulty WMI was not recognizing prerequisite update #KB2729094 as installed when it was, in fact, installed. Addressing WMI failures allowed the MSIE v11 installer to proceed and not error out since KB2729094 is now detected.

    Does it really have to be this many needles in multiple haystacks? Development needs to slooooow down from the frenzy it has become and sanity needs to be given its due!


    JTW

    • Marked as answer by MWave6 Tuesday, October 27, 2015 9:31 PM
    Tuesday, October 27, 2015 9:31 PM

All replies

  • Hi JTW,

    I found two answers that appear to answer your question.

    http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/can-not-get-update-kb2729094-to-go-through/5f9fb2e7-7cad-473f-b236-9cea272ecd40

    - 3 pages

    summary: are you using nortons security? see above for details.

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

    this is an optional update on windows 7. Just uncheck it from the WU list.

    A MVP from the answers forum may chime in. Regards. 


    Rob^_^

    • Marked as answer by Roger LuModerator Monday, August 11, 2014 2:50 AM
    • Unmarked as answer by MWave6 Tuesday, October 27, 2015 9:32 PM
    Thursday, July 10, 2014 1:33 AM
  • Thanks Rob,

    We actually aborted rolling out MSIE v11 and are now resuming same.

    To answer your question, we are not a Norton/Symantec environment. Nor do we use registry cleaners en masse.

    We are still stuck with the same situation. MSIE v11 will abend when being dished out via WSUS. We have several recently deployed PCs on which it succeeded. PCs that have been in service for a few years fail without exception that I've seen.

    Can anyone offer guidance as to where this might be failing? Seems like it should be simpler than this!


    JTW

    Monday, October 26, 2015 9:08 PM
  • GOOD NEWS!!

    Our issue boiled down to a missing registry value and also (2) modifications for good measure:

    First and foremost, we believe that the entirely missing REG_EXPAND_SZ value of "Working Directory" needed to contain "%systemroot%\System32\wbem" within [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM].

    Second (within [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WBEM\CIMOM]. ) we removed "the REG_SZ value for "Repository Directory" and added the same as REG_EXPAND_SZ with a value of "%systemroot%\System32\wbem\Repository" or an absolute path.

    Third, we changed the Logging value from "0" to "1".

    We discovered the 2nd item near the very bottom of this posting: http://blogs.technet.com/b/askperf/archive/2012/03/09/unable-to-connect-to-wmi-locally-win32-the-system-cannot-find-the-path-specified.aspx

    During the course of experimenting with WMIDiag v2.2 (which has a bug in the VBS file - a value of 6.0 must be changed to 6.1 to support Windows versions beyond Vista), we discovered item #s 1 & 3 as recommendations from the output file.

    As a result of these changes and a reboot, our WMI now reports correct system and service dependency information. Our MSIE v11 as dished out by WSUS is now succeeding. We believe that the faulty WMI was not recognizing prerequisite update #KB2729094 as installed when it was, in fact, installed. Addressing WMI failures allowed the MSIE v11 installer to proceed and not error out since KB2729094 is now detected.

    Does it really have to be this many needles in multiple haystacks? Development needs to slooooow down from the frenzy it has become and sanity needs to be given its due!


    JTW

    • Marked as answer by MWave6 Tuesday, October 27, 2015 9:31 PM
    Tuesday, October 27, 2015 9:31 PM