none
Problem with Windows 10 May 2018 patched with WSUS - “Not Applicable”

    Frage

  • We have a have a major problem with all May 2018 Windows patches for Windows 10 Pro 1703 being detected as “Not Applicable” for all Dell OEM versions of Windows 10 Pro 1703. This wasn’t a problem until these updates were released on May 8, 2018 and below is summary of problem and our environment:

     

    WSUS: Windows Server 2012 R2 (6.3.9600.18838)

     

    Affect versions of Windows 10 Pro 1709 (Dell OEM): 402 and 371

     

    Windows 10 Pro 1703 (Dell OEM and possibly other licenses) were initially affected, but Microsoft re-released patches on Wednesday, May 9, 2018. With updated 1703 patches systems changed from “Not Applicable” to downloading and installing.

     

    Affected KBs with a status of “Not Applicable” in WSUS:

    ·         2018-05 Cumulative Update for Windows 10 Version 1709 for x64-based Systems (KB4103727)

    ·         2018-05 Update for Windows 10 Version 1709 for x64-based Systems (KB4131372)

    ·         2018-05 Security Update for Adobe Flash Player for Windows 10 Version 1709 for x64-based Systems (KB4103729)

    ·         Windows Malicious Software Removal Tool x64 – May (KB890830)

    NOTE: We have no x86 Windows 10 systems

     

    Office 2016 updates are getting applied and installed just fine

     

    We have no 1803 systems yet, therefore unable to test.

     

    Previous to this we haven’t had issues with Windows 10 getting updates from our WSUS server.

     

    I am able to get these updates to install if I click “Check online for updates from Microsoft Update” without being upgraded to 1803 (our Group Policy settings might be prevent that for now). However this isn’t a solution with the number of systems we have compared to IT staff we have.

     

    I highly suspect there is a problem with the Prerequisite or Applicability Rules with the packages as imported through WSUS, because it doesn’t affect if Windows 10 systems which go directly to Microsoft for updates.

     

    We don’t have a support contact, because as a nonprofit we don’t have the funds… Any ideas or suggestions?

    Mittwoch, 16. Mai 2018 18:22

Alle Antworten

  • I am having a similar issue with some of my windows 10 clients running 1709 (Dell OEM pro as well).  Specifically the clients are not seeing that they need KB4131372 and/or KB4103727 but the server side says they do.

    So they are stuck on build 10.0.16299.371 instead of 10.0.16299.431

    If I stop windows update services and BITS and then rename the software distribution folder, then restart services then recheck they will see those updates and install them.  That's a painfully slow and manual fix but it works. 

    For some reason this affects only some of my Windows 10 clients however as similar machines do those updates properly without incident.

    Mittwoch, 16. Mai 2018 20:40
  • Thanks for the idea (stopping services, renaming software distribution directory, and restart services), but that doesn't affect the problem I'm seeing. I have even tried Windows Update Troubleshooter (https://support.microsoft.com/en-us/help/4027322/windows-update-troubleshooter).

     

    This isn't a problem for a few Windows 10 Pro 1709 systems with Microsoft Volume Licensing Keys instead of OEM (e.g. Dell systems with Windows 7 licenses and we purchased upgrade through Microsoft Volume Licenses and preformed clean installs of Windows 10).

     

    Did Microsoft make an announced change to block OEM and retail copies of Windows 10 Professional from obtain Windows 10 updates through WSUS (no issue with Office 2016 updates) and require you to purchase a Windows 10 Volume License in order to use WSUS for patching?


    Mittwoch, 16. Mai 2018 21:47
  • We made a support case. Microsoft knows the issue and is trying to solve it asap.
    Donnerstag, 17. Mai 2018 12:14
  • Adding information of a similar issue, Some Windows 1709 Pro both 32 / 64 bit machines unable to download updates from WSUS all DELL OEM machines. 

    {335EA306-6D07-45E6-8203-079F60E5894E} 2018-05-17 08:07:40:873-0400 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 WuApplicabilityScan Success Software Synchronization Windows Update Client successfully detected 0 updates. dgl/yz4AJ06PmoVq.1.0.0.3.0
    {F745E532-0F8F-4995-A801-C4CDC7A7BBBE} 2018-05-17 08:16:53:881-0400 1 147 [AGENT_DETECTION_FINISHED] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Enumerate Success Software Synchronization Windows Update Client successfully detected 0 updates. U41xEOqkHkOfmsZg.1.1.0.0.3.0
    {75B4B68A-F337-4145-B2A3-A9D34C651C34} 2018-05-17 08:16:53:897-0400 1 156 [AGENT_STATUS_30] 101 {00000000-0000-0000-0000-000000000000} 0 0 TrustedInstaller FOD Enumerate Success Pre-Deployment Check Reporting client status.

    Adding information so i can keep track of this thread.  Thank you.


    • Bearbeitet Jojida Donnerstag, 17. Mai 2018 13:11
    Donnerstag, 17. Mai 2018 12:40
  • UPDATE -- WSUS received 25 new updates along with 10 revised updates, and not a one of them were 1709.  1607 and 1803 are the only versions of windows 10 that were updated / added..  Maybe we will get lucky and have 1709 come out over the weekend.  
    Freitag, 18. Mai 2018 12:39
  • We made a support case. Microsoft knows the issue and is trying to solve it asap.
    Ricardo, any progress on that support case?
    Freitag, 18. Mai 2018 14:17