locked
IE10 install failes RRS feed

  • Question

  • I am trying to install IE10NL on some clients but every times it has another reason to not install but everytimes it failes. Several times the log shows this (see beneath). Other times another log.

    We are deploying thru System Centre Essentials which uses WSUS to deploy. In system centre essentials for the clients it always shows the error: Installation Failure: Windows failed to install the following update with error 0x80070643: IE10NL. even when IE10NL has succeeded after three times...but this is a problem from sce i believe.

    I have installed all the prerequisites according to this site: http://support.microsoft.com/kb/2818833 and another one i have added myself because that update has also shown in ie10main.log KB2639308.
    The IE10 install starts every day with WIndows updater from client to WSUS server at 13:00 PM, but i have also tried it manually.. 

    I am beginning to think that it is not possible to install IE10NL thru WSUS or whatever because he is missing something in Windows 7 SP1 every time but what do i need this time to succesfully deploy IE10?

    The following i noticed on some clients in IE10main.log:

    00:00.062: Started: 2014/07/17 (Y/M/D) 07:45:17.262 (local)
    00:00.062: Time Format in this log: MM:ss.mmm (minutes:seconds.milliseconds)
    00:00.062: Command line: "C:\Windows\SoftwareDistribution\Download\Install\IE10setupnl.exe" /quiet /passive /update-no
    00:00.062: INFO:    Setup installer for Internet Explorer: 10.0.9200.16521
    00:00.078: INFO:    Previous version of Internet Explorer: 8.0.7601.17514
    00:00.078: INFO:    Checking if iexplore.exe's current version is between 10.0.8100.0...
    00:00.078: INFO:    ...and 10.1.0.0...
    00:00.078: INFO:    Maximum version on which to run IEAK branding is: 10.1.0.0...
    00:00.078: INFO:    iexplore.exe version check success. Install can proceed.
    00:00.078: INFO:    Operating System: Windows Workstation: 6.1.7601 (Service Pack 1)
    00:00.078: INFO:    Trying to extract ID: SetupDownloadList.txt (0) as "SetupDownloadList.txt"
    00:00.093: INFO:    Trying to extract ID: HardwareBlockingList.xml (0) as "HardwareBlockingList.xml"
    00:00.140: INFO:    Trying to extract ID: 6006 (0) as "IE10-neutral.Extracted.cab"
    00:00.327: INFO:    Trying to extract ID: 6010 (1043) as "IE10_x86_NLD.cab"
    00:00.390: INFO:    Extracted NLD language pack to C:\Windows\TEMP\IE1F2C6.tmp\IE10_x86_NLD.cab.
    00:00.405: INFO:    Trying to extract ID: 5501 (1043) as "Spelling_nl.msu"
    00:00.405: INFO:    Extracted Spelling dictionary for nl to C:\Windows\TEMP\IE1F2C6.tmp\Spelling_nl.msu.
    00:00.405: INFO:    Trying to extract ID: 5502 (1043) as "Hyphenation_nl.msu"
    00:00.437: INFO:    Extracted Hyphenation dictionary for nl to C:\Windows\TEMP\IE1F2C6.tmp\Hyphenation_nl.msu.
    00:00.437: INFO:    Trying to extract ID: 5501 (1033) as "Spelling_en.msu"
    00:00.437: INFO:    Extracted Spelling dictionary for en to C:\Windows\TEMP\IE1F2C6.tmp\Spelling_en.msu.
    00:00.437: INFO:    Trying to extract ID: 5502 (1033) as "Hyphenation_en.msu"
    00:00.452: INFO:    Extracted Hyphenation dictionary for en to C:\Windows\TEMP\IE1F2C6.tmp\Hyphenation_en.msu.
    00:00.795: INFO:    Trying to extract ID: 6128 (1043) as "IE10-support.cab"
    00:01.419: INFO:    PauseOrResumeAUThread: Successfully paused Automatic Updates.
    00:01.685: INFO:    Launched program to check hardware: "C:\Windows\TEMP\IE1F2C6.tmp\IE10-SUPPORT\IEXPLORE.EXE" /CheckHardware "C:\Windows\TEMP\IE1F2C6.tmp\HardwareBlockingList.xml"
    00:01.747: INFO:    Hardware support check succeeded. Installation will continue.
    00:01.747: INFO:    Windows 7 operating system detected.
    00:01.747: INFO:    Service pack major: 1
    00:01.747: INFO:    Service pack minor: 0
    00:01.747: INFO:    Service pack name:  Service Pack 1
    00:01.825: WARNING: Checking version for C:\Windows\System32\api-ms-win-downlevel-user32-l1-1-0.dll.  The file does not exist.
    00:01.841: INFO:    Version Check for (KB2639308) of C:\Windows\System32\Ntoskrnl.exe: 6.1.7601.17727 >= 6.1.7601.17727 (True)
    00:01.856: INFO:    Version Check for (KB2533623) of C:\Windows\System32\api-ms-win-security-base-l1-1-0.dll: 6.1.7601.17965 >= 6.1.7601.17617 (True)
    00:01.950: INFO:    Version Check for (KB2731771) of C:\Windows\System32\kernel32.dll: 6.1.7601.17965 >= 6.1.7601.17932 (True)
    00:01.965: INFO:    Checking for correct version of C:\Windows\Fonts\segoeui.ttf.
    00:01.965: INFO:    Version Check for (KB2786081) of C:\Windows\System32\taskhost.exe: 6.1.7601.18010 >= 6.1.7601.18010 (True)
    00:04.836: ERROR:   Couldn't create setup troubleshooting shortcut on the desktop. HRESULT: 0x80070002,
    00:04.883: INFO:    PauseOrResumeAUThread: Successfully resumed Automatic Updates.
    00:04.883: INFO:    Setup exit code: 0x00009C47 (40007) - Required updates failed to download.
    00:05.007: INFO:    Scheduling upload to IE SQM server: http://sqm.microsoft.com/sqm/ie/sqmserver.dll
    00:10.077: ERROR:   SQM Upload failed while uploading "C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Windows\Temporary Internet Files\SQM\iesqmdata_setup0.sqm" with error: 2147500036
    00:10.077: ERROR:   SQM Upload failed while uploading "C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Windows\Temporary Internet Files\SQM\iesqmdata_setup1.sqm" with error: 2147500036
    00:10.077: ERROR:   SQM Upload failed while uploading "C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Windows\Temporary Internet Files\SQM\iesqmdata_setup2.sqm" with error: 2147500036
    00:10.077: ERROR:   SQM Upload failed while uploading "C:\Windows\system32\config\systemprofile\AppData\Local\Microsoft\Windows\Temporary Internet Files\SQM\iesqmdata_setup3.sqm" with error: 2147500036
    00:10.077: INFO:    Cleaning up temporary files in: C:\Windows\TEMP\IE1F2C6.tmp
    00:10.608: INFO:    Unable to remove directory C:\Windows\TEMP\IE1F2C6.tmp, marking for deletion on reboot.
    00:10.608: INFO:    Released Internet Explorer Installer Mutex


    freddie

    Thursday, July 17, 2014 8:33 AM

All replies

  • Hi,

    Regarding to the exit error, this issue can be caused by network bandwidth limitation:

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

    Please check following article to improve the WSUS performance to see what's going on:

    Improve WSUS Download Performance with BITS
    http://technet.microsoft.com/en-us/library/dd939927(v=ws.10).aspx


    Kate Li
    TechNet Community Support

    Friday, July 18, 2014 9:38 AM
  • And what to do with BITS, monitor traffic or another manner of downloading client-server?

    This is a little complicated...
    We do have 100 Mbit connections client-server and downloading updates like IE10NL to client is very fast..

    Must i install BITS to the client or the WSUS server?


    freddie


    • Edited by surfer10 Friday, July 18, 2014 9:58 AM
    Friday, July 18, 2014 9:57 AM
  • 00:01.825: WARNING: Checking version for C:\Windows\System32\api-ms-win-downlevel-user32-l1-1-0.dll.  The file does not exist.

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

    What version of that file does exist?

    C:\Windows>dir/a/b/s api-ms-win-downlevel-user32*

    Perhaps an  sfc  /scanfile=  would fix that symptom?

    In any case, if you found one for the install to find I imagine it would change your symptom, at least for this log output.   ; )

     
    Good luck



    Robert Aldwinckle
    ---



    Friday, July 18, 2014 2:41 PM
    Answerer
  • Setup exit code: 0x00009C47 (40007) - Required updates failed to download.

    @ Kate

    What is the significance of that missing module?   Would the CBS.log (or others) show it trying to be replaced?

    FWIW I always suggest using ProcMon to find, correlate and supplement whatever diagnostics are being produced but if you have access to the source and support documentation perhaps there is an easier way?   <eg>

    TIA

    Robert
    ---



    Robert Aldwinckle
    ---

    Friday, July 18, 2014 2:50 PM
    Answerer
  • 00:01.825: WARNING: Checking version for C:\Windows\System32\api-ms-win-downlevel-user32-l1-1-0.dll.  The file does not exist.

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

    What version of that file does exist?

    C:\Windows>dir/a/b/s api-ms-win-downlevel-user32*

    I did this command on 2 machines which have ie10 already installed and on 1 machine which has not IE10 installed. On all three machines he gives "file not found". So how importand is this file for IE10 to install?

    I can do a lot of tool tricks etc. to recover the machine to install IE10 but there are 200 more machines to deploy, many have the same config...



    freddie


    • Edited by surfer10 Monday, July 21, 2014 7:21 AM
    Monday, July 21, 2014 7:13 AM
  • I have copied several lines out of cbs.log. This is what repeately comes back in the log. I don't know if it has something to do with the IE10 install...

    Session: 30385315_2604441124 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Read out cached package applicability for package: Package_for_KB2729094~31bf3856ad364e35~x86~~6.1.2.0, ApplicableState: 112, CurrentState:112
    2014-07-21 07:21:20, Info                  CBS    Session: 30385315_2604441125 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Read out cached package applicability for package: Package_for_KB2786081~31bf3856ad364e35~x86~~6.1.1.0, ApplicableState: 112, CurrentState:112
    2014-07-21 07:21:20, Info                  CBS    Session: 30385315_2604441126 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Read out cached package applicability for package: Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package-TopLevel~31bf3856ad364e35~x86~~7.1.7601.16492, ApplicableState: 112, CurrentState:0
    2014-07-21 07:21:20, Info                  CBS    Session: 30385315_2604596284 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2014-07-21 07:21:20, Info                  CBS    Session: 30385315_2604751444 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Read out cached package applicability for package: Package_for_KB2859537~31bf3856ad364e35~x86~~6.1.1.3, ApplicableState: 112, CurrentState:0
    2014-07-21 07:21:20, Info                  CBS    Session: 30385315_2604751445 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2014-07-21 07:21:20, Info                  CBS    Session: 30385315_2604751446 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Read out cached package applicability for package: Package_for_KB2871997~31bf3856ad364e35~x86~~6.1.2.5, ApplicableState: 112, CurrentState:0
    2014-07-21 07:21:20, Info                  CBS    Session: 30385315_2605527244 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2014-07-21 07:21:20, Info                  CBS    Session: 30385315_2605527245 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Read out cached package applicability for package: Package_for_KB2839229~31bf3856ad364e35~x86~~6.1.1.0, ApplicableState: 112, CurrentState:0
    2014-07-21 07:21:20, Info                  CBS    Session: 30385315_2605682404 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Session: 30385315_2605682405 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:20, Info                  CBS    Read out cached package applicability for package: Package_for_KB2639308~31bf3856ad364e35~x86~~6.1.1.0, ApplicableState: 112, CurrentState:112
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2659522924 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Read out cached package applicability for package: Package_for_KB2758857~31bf3856ad364e35~x86~~6.1.1.0, ApplicableState: 112, CurrentState:112
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2660143564 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Read out cached package applicability for package: Package_for_KB2813430~31bf3856ad364e35~x86~~6.1.1.4, ApplicableState: 112, CurrentState:112
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2660919364 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Read out cached package applicability for package: Package_for_KB2729094~31bf3856ad364e35~x86~~6.1.2.0, ApplicableState: 112, CurrentState:112
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2660919365 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Read out cached package applicability for package: Package_for_KB2786081~31bf3856ad364e35~x86~~6.1.1.0, ApplicableState: 112, CurrentState:112
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2661074524 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Read out cached package applicability for package: Microsoft-Windows-PlatformUpdate-Win7-SRV08R2-Package-TopLevel~31bf3856ad364e35~x86~~7.1.7601.16492, ApplicableState: 112, CurrentState:0
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2661229684 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2661229685 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Read out cached package applicability for package: Package_for_KB2859537~31bf3856ad364e35~x86~~6.1.1.3, ApplicableState: 112, CurrentState:0
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2661229686 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2661229687 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Read out cached package applicability for package: Package_for_KB2871997~31bf3856ad364e35~x86~~6.1.2.5, ApplicableState: 112, CurrentState:0
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2662160644 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2662160645 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Read out cached package applicability for package: Package_for_KB2839229~31bf3856ad364e35~x86~~6.1.1.0, ApplicableState: 112, CurrentState:0
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2662160646 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Session: 30385315_2662160647 initialized by client WindowsUpdateAgent.
    2014-07-21 07:21:26, Info                  CBS    Read out cached package applicability for package: Package_for_KB2639308~31bf3856ad364e35~x86~~6.1.1.0, ApplicableState: 112, CurrentState:112
    2014-07-21 07:31:24, Info                  CBS    Reboot mark refs incremented to: 1
    2014-07-21 07:31:24, Info                  CBS    Scavenge: Starts
    2014-07-21 07:31:24, Info                  CSI    00000009@2014/7/21:05:31:24.878 CSI Transaction @0x21edb0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000002 and client id [10]"TI6.0_0:0/"

    2014-07-21 07:31:24, Info                  CBS    Scavenge: Begin CSI Store
    2014-07-21 07:31:25, Info                  CSI    0000000a Performing 1 operations; 1 are not lock/unlock and follow:
      Scavenge (8): flags: 00000017
    2014-07-21 07:31:25, Info                  CSI    0000000b Store coherency cookie matches last scavenge cookie, skipping scavenge.
    2014-07-21 07:31:25, Info                  CSI    0000000c ICSITransaction::Commit calling IStorePendingTransaction::Apply - coldpatching=FALSE applyflags=7
    2014-07-21 07:31:25, Info                  CSI    0000000d Creating NT transaction (seq 2), objectname [6]"(null)"
    2014-07-21 07:31:25, Info                  CSI    0000000e Created NT transaction (seq 2) result 0x00000000, handle @0x204
    2014-07-21 07:31:25, Info                  CSI    0000000f@2014/7/21:05:31:25.158 CSI perf trace:
    CSIPERF:TXCOMMIT;44671
    2014-07-21 07:31:25, Info                  CBS    Scavenge: Completed, dis
    2014-07-21 07:31:25, Info                  CSI    00000010@2014/7/21:05:31:25.158 CSI Transaction @0x21edb0 destroyed
    2014-07-21 07:31:25, Info                  CBS    Reboot mark refs: 0
    2014-07-21 07:31:25, Info                  CBS    Idle processing thread terminated normally
    2014-07-21 07:31:25, Info                  CBS    Ending the TrustedInstaller main loop.
    2014-07-21 07:31:25, Info                  CBS    Starting TrustedInstaller finalization.
    2014-07-21 07:31:25, Info                  CBS    Ending TrustedInstaller finalization.


    freddie

    Monday, July 21, 2014 7:20 AM
  • I have copied several lines out of cbs.log.

    Some of those are ancient.  Only 2 of them are from this year.  Try using MBSA to see what it says is going on.  Perhaps these messages are just WU's obscure way of telling you that they aren't needed?  E.g., using the Catalog shows that some those had long chains of Supersedes so who knows if they themselves aren't already superseded by something else?

    BTW please clarify that this is a 32-bit system being updated.

    Also, it might help if you told us which "tricks" you were able to do to get these installed, e.g. in case someone has some automation suggestions for you, if nothing else.

    Since your problem really seems to have more to do with a failure of WU than with a problem with IE this may not be the best forum to be looking for help with it.  However, I will be interested in seeing a resolution for it.

    Good luck



    Robert Aldwinckle
    ---


    Monday, July 21, 2014 1:08 PM
    Answerer
  • Yes it is a Win7 pro 32 bit system. But this is not the first system which failed. Several more with other failed to download etc. in the logging.

    I do not have any trics but i mean what the suggestion  was to to a sfc/scanfile etc. is not the solution because there are to many machines to deploy.

    If it is a WSUS problem then when installing IE 10 manually would not give problems i gueass, so i must try that and see if the problem has something to do with WSUS are with the prerequisites of other updates on the client whcih are not installed.



    freddie

    Monday, July 21, 2014 1:19 PM
  • If it is a WSUS problem then when installing IE 10 manually would not give problems i gueass, so i must try that and see if the problem has something to do with WSUS are with the prerequisites of other updates on the client whcih are not installed.

    Good point.  But the MBSA suggestion could have a similar effect.  E.g. the most common cause of your symptom is corrupted WinSxS so the MBSA would show you how it viewed that.   Also, (as I understand it), the MBSA can be used to report on a set of machines, so you might get some information for whatever patterns you have with your symptom by machine class.



    Robert Aldwinckle
    ---

    Monday, July 21, 2014 2:13 PM
    Answerer
  • Ok. I have run MBSA. There are a lot of security updates that are not approved for the machine but must be installed according to MBSA. I can post the list here but it is a large list....


    freddie

    Tuesday, July 22, 2014 9:40 AM
  •  I can post the list here but it is a large list....


    You could post it to your OneDrive (formerly known as SkyDrive.)


    Robert Aldwinckle
    ---

    Tuesday, July 22, 2014 11:06 AM
    Answerer
  • Can you help me a little bit with onedrive, must i make a account etc? is this free storage?


    freddie

    Wednesday, July 23, 2014 6:09 AM
  • For testing purpose is installed all updates for the client. After a reboot tried IE10 NL install again. Again another error. The error is: The download process for language IE10_X86_NL.cab did not return in the allocated time: 5 minutes.

    I guess he wants to download a language pack file and that is not succeeding within 5 minutes. But why a language pack file because IE10 setup is in the desired language?
    Because IE10 cannot download anything i have installed every update nessesairy for the installation of IE10. Still he comes with another error.

    To see if the error is not WSUS related i have tried the full installer manually. Unfortually he gives the same error then.

    What can i do?

    Never mind above: after a restart IE10 is installed. However now i have installed all updates it is not clear which update is needed for the install and that is exactly what i want to know becaue do not want to install all updates on every client...


    freddie


    • Edited by surfer10 Thursday, July 24, 2014 8:43 AM
    Thursday, July 24, 2014 7:18 AM
  • Added info:

    After succesfully installed IE10 and looking at the log file one difference (among others off course) with the log file of a failed installation is the line:

    c:\windows\system32\api-ms-win-downloevel-user32-l1-1-0.dll: 6.2.9200.16492>=6.2.9200.16492 (TRUE)

    In the log where installations failed this was NOT TRUE, so maybe this is the showstopper? what do i need to install this file of module...?


    freddie

    Friday, July 25, 2014 7:39 AM
  • c:\windows\system32\api-ms-win-downlevel-user32-l1-1-0.dll: 6.2.9200.16492>=6.2.9200.16492 (TRUE)

    In the log where installations failed this was NOT TRUE, so maybe this is the showstopper? what do i need to install this file of module...?

    Commonly recommended:

    Open CMD and run:
    sfc /scannow
    After complete, restart and all is well.


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Friday, July 25, 2014 11:08 AM
  • c:\windows\system32\api-ms-win-downlevel-user32-l1-1-0.dll: 6.2.9200.16492>=6.2.9200.16492 (TRUE)

    In the log where installations failed this was NOT TRUE, so maybe this is the showstopper? what do i need to install this file of module...?

    Commonly recommended:

    Open CMD and run:
    sfc /scannow
    After complete, restart and all is well.

    @ Don

    Do we know that that module is one of the "protected" ones?  (Does /scannow check and repair everything that is in WinSxS?)   What about  sfc  /scanfile=  instead?  Better external diagnostics about this one file in any case I suspect.

    http://technet.microsoft.com/en-us/library/ff950779.aspx

    Another case for using ProcMon to do the necessary reverse engineering to supplement incomplete documentation.



    Robert Aldwinckle
    ---

    Friday, July 25, 2014 1:21 PM
    Answerer
  • @ Don

    Do we know that that module is one of the "protected" ones?  (Does /scannow check and repair everything that is in WinSxS?)   What about  sfc  /scanfile=  instead?  Better external diagnostics about this one file in any case I suspect.

    I don't know for a fact, no.
    On my system, that file is protected/secured to TrustedInstaller (which implies to me that it's fairly rigorously controlled).
    There are many, many references in threads all over, about successfully using SFC to fix this specific problem. (and, as always, there are examples where it didn't help).

    SFC's "scope of operations" seems to have changed over time (from Vista - Win7 - Win8), so I don't think it does cover everything in the GAC (WinSxS) - I don't think that's the scope of SFC.
    On Win8, the use of both SFC and also DISM /restorehealth is sometimes needed.

    Based on observation and some first-hand experience, Windows gets very upset when there are module version mis-matches, and, where I see one mis-match, I'm usually left wondering "are there any others??".
    So, SFC /scannow will check all within its scope, rather than just a single miscreant.

    @ surfer10 - sorry to hear that you are still having troubles with your IE rollout.
    Is it possible that your deployed machines might have a common fault? (perhaps introduced by your imaging/deployment process?)


    Don
    (Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
    This helps the community, keeps the forums tidy, and recognises useful contributions. Thanks!)

    Saturday, July 26, 2014 12:19 AM
  • That indeed is possible. The machines have the same image with minor differences betweed departments...

    But i am also installing IE10 after the images. The images i have updated all the way. After deploying the Images i install IE10 with MDT2012 in a Task Sequence. This installation is successful no problems at all. So i believe there is one or more updates that is missing before the installation of IE10.

    I am no thinking how to update the clients which must have IE10 with the right updates. Thatswhy i would like to know which are missing so i can install them with WSUS / System Centre Essentials to the clients...

    Installing them all is costing to much time to select the WIndows 7 updates and install them....


    freddie

    Monday, July 28, 2014 7:21 AM