none
IE 10 via WSUS

    Question

  • Having a problem with IE 10 showing as not applicable for my windows 7 sp1 workstations after revision 203 was released 10/8/2013.  Before with revision 202 my workstations were reporting properly that they needed IE10.  I had even deployed to one school.  Before the revision I was seeing about 7 thousand workstations needing the update.  The 712 still reporting needing the update are off line, and that number has been going down as they come online.  Any ideas would be appreciated.

    Friday, October 11, 2013 3:11 PM

Answers

All replies

  • Hi,

    Based on my research, Internet Explorer 10 with WSUS will be automatic Installed. 

    Please refer to the below link for more details:

    Internet Explorer 10 Delivery Through Automatic Updates:

    http://technet.microsoft.com/en-us/ie/jj898508.aspx

    Regards,

    Yan Li


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Monday, October 14, 2013 6:59 AM
    Moderator
  • Having a problem with IE 10 showing as not applicable for my windows 7 sp1 workstations after revision 203 was released 10/8/2013.

    I'm seeing the same thing. Must be a problem with metadata.

    Regards
    Rolf Lidvall
    Swedish Radio (Ltd)



    • Edited by Rolf Lidvall Monday, October 14, 2013 7:38 AM edit
    Monday, October 14, 2013 7:28 AM
  • The same situation here. On my Windows 7 SP1 clients is IE 9 installed.

    I approved IE 10 for installation after october patchday, but the clients are reporting "not applicable" and they don't install it.

    All other updates from october patchday are installing fine. I think, there must be a problem with the correct detection of the updates.

    I hope MS will fix this soon. If someone got a solution, please respond.

    Thanks

    Monday, October 14, 2013 8:46 AM
  • Hi,

    Based on my research, Internet Explorer 10 with WSUS will be automatic Installed. 

    Please refer to the below link for more details:

    Internet Explorer 10 Delivery Through Automatic Updates:

    http://technet.microsoft.com/en-us/ie/jj898508.aspx

    Regards,

    Yan Li


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

    Hi Yan Li

    This does not help. I approved IE10 manually on wsus server for the client group, but the clients don't detect the update. They say "no Updates Available", if I trigger "check for updates".


    Monday, October 14, 2013 8:50 AM
  • Having a problem with IE 10 showing as not applicable for my windows 7 sp1 workstations after revision 203 was released 10/8/2013.  Before with revision 202 my workstations were reporting properly that they needed IE10.  I had even deployed to one school.  Before the revision I was seeing about 7 thousand workstations needing the update.  The 712 still reporting needing the update are off line, and that number has been going down as they come online.  Any ideas would be appreciated.

    What other updates are Not Installed on these systems? Get them fully patched with other Operating System updates, and then we can make some intelligent sense of what might be impacting applicability of IE10.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Monday, October 14, 2013 7:18 PM
    Moderator
  • This does not help. I approved IE10 manually on wsus server for the client group, but the clients don't detect the update. They say "no Updates Available", if I trigger "check for updates".


    There's a BIG difference between an update that is Not Applicable and an update that is Needed but not reported by the WUAgent as "available". The key word here is available and this scenario has been discussed dozens of times in this forum previously.

    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Monday, October 14, 2013 7:20 PM
    Moderator
  • The answer might be in this document, particularly "Step 2" I could imagine:

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

    Regards
    Rolf Lidvall
    Swedish Radio (Ltd)


    Tuesday, October 15, 2013 8:24 AM
  • The answer might be in this document, particularly "Step 2" I could imagine:

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

    Hi Rolf

    Yes that's indeed the problem. In my case, KB2670838 is missing on the clients. After manually installing it, and "Check for updates" pressed, Internet Explorer 10 will be offered for installation as missing update.

    KB2670838 is missing, because it's classified as "Feature Packs" on WSUS and we don't synchronize "Feature Packs" in our WSUS configuration.

    Thanks a lot for your help.

    Patrick

    • Proposed as answer by jmh08 Tuesday, November 19, 2013 1:55 PM
    Tuesday, October 15, 2013 12:48 PM
  • Patrick, no problem, only glad to help! And thanks for the feedback.

    Regards
    Rolf Lidvall
    Swedish Radio (Ltd)



    • Edited by Rolf Lidvall Tuesday, October 15, 2013 1:25 PM edit
    Tuesday, October 15, 2013 12:56 PM
  • KB2670838 is missing, because it's classified as "Feature Packs" on WSUS and we don't synchronize "Feature Packs" in our WSUS configuration.

    Yet another great case study on why ALL CLASSIFICATIONS (Except Drivers) should be selected for synchronization on every WSUS Server.

    How can you possibly know what you're missing if you don't know what you're missing? :-)


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Tuesday, October 15, 2013 5:11 PM
    Moderator
  • I'm having the same problem. All pre-reqs are installed. IE10 shows not applicable. Was working fine until recently, probably up until the 203 revision on 10/8/13, as you stated. Have you figured this out?

    Thanks!

    Alex

    Wednesday, October 16, 2013 4:33 PM
  • No not yet.  I broke down and put in a call to MS support.  Will be working with them today.  I'll post the results.
    Thursday, October 17, 2013 1:21 PM
  • Excellent! Looking forward to your reply :) Thank you!

    Alex

    Thursday, October 17, 2013 4:39 PM
  • Any information? I face the same problem. 
    Wednesday, October 23, 2013 9:40 AM
  • OK, folks sorry it's taken so long to reply.  I had already verified the installation of the prerequisites listed in http://support.microsoft.com/kb/2820688/en-us and the updates that superseded those prereqs.  But still no luck.  Working with MS we manually installed IE10 then looked at the install log c:\windows\IE10_main.log and found the below entries.  I bolded and underlined the one that is listed as false.  I approved that update and as it installs I'm starting to see IE10 needed numbers starting to increase.  So not completely sure at this point, but looks like this was my issue.  So suggest if you're having a similar issue to do a manual install then check the ie1--main.log file to see what prereqs had to be installed.  So a couple of folks had the correct answer in that it was a prereq problem, I just didn't know how to determine what was missing.  Thanks to all for the assistance.

    00:03.073: INFO:    Version Check for (KB2834140) of C:\Windows\System32\d3d11.dll: 6.2.9200.16492 >= 6.2.9200.16570 (False)
    00:03.120: 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.16492 (True)
    00:03.151: INFO:    Version Check for (KB2639308) of C:\Windows\System32\Ntoskrnl.exe: 6.1.7601.18229 >= 6.1.7601.17727 (True)
    00:03.198: 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:03.245: INFO:    Version Check for (KB2731771) of C:\Windows\System32\kernel32.dll: 6.1.7601.18229 >= 6.1.7601.17932 (True)

    Wednesday, October 23, 2013 4:16 PM
  • I approved that update and as it installs I'm starting to see IE10 needed numbers starting to increase.

    So, to my original question on October 14th, "What other updates are Not Installed?", the answer was: KB2834140, and presumably that information was available from the WSUS console.

    If the update was previously Not Approved, and approving it caused it to install and then those systems started reporting IE10 as needed, then it seems that KB2834140 must have been previously reported as needed, or else the WUAgent would not download and install it.


    Lawrence Garvin, M.S., MCITP:EA, MCDBA, MCSA
    SolarWinds Head Geek
    Microsoft MVP - Software Packaging, Deployment & Servicing (2005-2013)
    My MVP Profile: http://mvp.microsoft.com/en-us/mvp/Lawrence R Garvin
    http://www.solarwinds.com/gotmicrosoft
    The views expressed on this post are mine and do not necessarily reflect the views of SolarWinds.

    Friday, October 25, 2013 10:26 PM
    Moderator
  • The answer might be in this document, particularly "Step 2" I could imagine:

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

    Hi Rolf

    Yes that's indeed the problem. In my case, KB2670838 is missing on the clients. After manually installing it, and "Check for updates" pressed, Internet Explorer 10 will be offered for installation as missing update.

    KB2670838 is missing, because it's classified as "Feature Packs" on WSUS and we don't synchronize "Feature Packs" in our WSUS configuration.

    Thanks a lot for your help.

    Patrick


    Hi Rolf, thanks . Plattform Update was missing....now we can deploy IE10. Thanks you made by day (Honestly I try find IE11 in WSUS ....)
    Tuesday, November 19, 2013 1:56 PM
  • > Thanks you made by day (Honestly I try find IE11 in WSUS ....)

    No problem, it took IE10 about six months to be released to WSUS so I wouldn't hold my breath regarding IE11 anytime soon.


    Rolf Lidvall, Swedish Radio (Ltd)

    Tuesday, November 19, 2013 2:26 PM
  • OK, folks sorry it's taken so long to reply.  I had already verified the installation of the prerequisites listed in http://support.microsoft.com/kb/2820688/en-us and the updates that superseded those prereqs.  But still no luck.  Working with MS we manually installed IE10 then looked at the install log c:\windows\IE10_main.log and found the below entries.  I bolded and underlined the one that is listed as false.  I approved that update and as it installs I'm starting to see IE10 needed numbers starting to increase.  So not completely sure at this point, but looks like this was my issue.  So suggest if you're having a similar issue to do a manual install then check the ie1--main.log file to see what prereqs had to be installed.  So a couple of folks had the correct answer in that it was a prereq problem, I just didn't know how to determine what was missing.  Thanks to all for the assistance.

    00:03.073: INFO:    Version Check for (KB2834140) of C:\Windows\System32\d3d11.dll: 6.2.9200.16492 >= 6.2.9200.16570 (False)
    00:03.120: 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.16492 (True)
    00:03.151: INFO:    Version Check for (KB2639308) of C:\Windows\System32\Ntoskrnl.exe: 6.1.7601.18229 >= 6.1.7601.17727 (True)
    00:03.198: 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:03.245: INFO:    Version Check for (KB2731771) of C:\Windows\System32\kernel32.dll: 6.1.7601.18229 >= 6.1.7601.17932 (True)

    This is what fixed it for us.  We had already previously approved all the prerequisites from MS's article on that, but sometime they stopped updating our clients.

    I approved KB2834140 and now IE 10 is installing correctly.  Thanks jag1328 for posting this fix!

    Friday, February 14, 2014 6:29 PM
  • I can't believe MS made this so difficult. Stupid!

    I had made sure one by one these "prerequisites" are installed, but still my workstations just don't this IE10 from WSUS server. Fuck off! that is all I want to say.

    18 hours 16 minutes ago