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

    Domanda

  • 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?

    mercoledì 16 maggio 2018 18:22

Risposte

  • On May 21, Microsoft released 2018-05 Update for Windows 10 Version 1709 for x64-based Systems (KB4132650) via WSUS, which is a service stack update and is detected as needed by all of our 1709 systems. Once installed then our 1709 systems are reporting in properly regarding the status of needing or installation of May 2018 updates for 1709 (including 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), and 2018-05 Security Update for Adobe Flash Player for Windows 10 Version 1709 for x64-based Systems (KB4103729)).

     

    Microsoft also recently released KB4103714 for 1709 systems, which increases the OS Build to 16299.461 to the Microsoft Catalog, but not WSUS. I was able to import KB4103714 (2018 Cumulative Update for Windows 10 Version for x64-based Systems) into WSUS. If KB4132650 (service stack update) is installed, then this new update, KB4103714, is being detected as needed by all of 1709 systems.

     

    At this point it appears that Microsoft corrected this detection issue for 1709 systems with KB4132650 service stack update) released via WSUS yesterday. I will need to install these updates on systems outside of a small test group to confirm Microsoft has resolved this problem.

    • Contrassegnato come risposta Scott Kraft mercoledì 30 maggio 2018 18:27
    martedì 22 maggio 2018 18:00

Tutte le risposte

  • 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.

    mercoledì 16 maggio 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?


    mercoledì 16 maggio 2018 21:47
  • We made a support case. Microsoft knows the issue and is trying to solve it asap.
    giovedì 17 maggio 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.


    • Modificato Jojida giovedì 17 maggio 2018 13:11
    giovedì 17 maggio 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.  
    venerdì 18 maggio 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?
    venerdì 18 maggio 2018 14:17
  • We made a support case. Microsoft knows the issue and is trying to solve it asap.

    Ricardo, any progress on that support case?

    Microsoft confirmed, the issue has fixed.
    martedì 22 maggio 2018 11:03
  • fixed by what? 

    1709 CU KB4103727 still fails downloading even if the new SSU KB4132650 is installed.
    In my view something prevents the correct download of the CU.

    Using the the described way here and after a reboot KB4103727 gets installed as expected.

    There is a new CU which was released on May 21st which is not present on WSUS and therefore I do not know if the issue is fixed with the latest CU release for 1709

    martedì 22 maggio 2018 12:17
  • In the first test (today) the cumulative update installed successfully. After some extra tests we also got the failures again. We contacted Microsoft again and we are waiting for an actionplan.

    martedì 22 maggio 2018 13:33
  • On May 21, Microsoft released 2018-05 Update for Windows 10 Version 1709 for x64-based Systems (KB4132650) via WSUS, which is a service stack update and is detected as needed by all of our 1709 systems. Once installed then our 1709 systems are reporting in properly regarding the status of needing or installation of May 2018 updates for 1709 (including 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), and 2018-05 Security Update for Adobe Flash Player for Windows 10 Version 1709 for x64-based Systems (KB4103729)).

     

    Microsoft also recently released KB4103714 for 1709 systems, which increases the OS Build to 16299.461 to the Microsoft Catalog, but not WSUS. I was able to import KB4103714 (2018 Cumulative Update for Windows 10 Version for x64-based Systems) into WSUS. If KB4132650 (service stack update) is installed, then this new update, KB4103714, is being detected as needed by all of 1709 systems.

     

    At this point it appears that Microsoft corrected this detection issue for 1709 systems with KB4132650 service stack update) released via WSUS yesterday. I will need to install these updates on systems outside of a small test group to confirm Microsoft has resolved this problem.

    • Contrassegnato come risposta Scott Kraft mercoledì 30 maggio 2018 18:27
    martedì 22 maggio 2018 18:00
  • Let me guess: you have a WSUS on a 2012R2

    ...

    Microsoft Update Catalog tells me that our WSUS on a 2016 Server is not compatible :)

    So after installing the latest SSU which works like a charm the first CU KB4103727 from May 8th still fails.
    I can get it to install by using the reset mentioned in my pervious post.

    All in all not so good.

    mercoledì 23 maggio 2018 10:30
  • Markus, yes, I am using WSUS is on Windows Server 2012 R2 (6.3.9600.18838)

    mercoledì 23 maggio 2018 16:29
  • Microsoft is still investigating the issue. We are also using WSUS on 2016 servers. Also we can't import the new update.
    giovedì 24 maggio 2018 07:40
  • At this moment the issue is still there. We really hope the 2018-06 can be installed on 1709 without issues. When connecting with our WSUS 2016 environment this update can't still be downloaded and installed:

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

    The only workaround (which we don't accept) is this one:

    Create a GPO with the following batch script:

    net stop wuauserv

    if exist c:\Windows\SoftwareDistribution ren c:\Windows\SoftwareDistribution SoftwareDistribution.old

    net start wuauserv

    martedì 5 giugno 2018 11:46
  • Hi Scott!

    Did you get this one resolved? 
    I have a same problem with dell and lenovo systems. Most of them are installed using volume key, and 1803 update shows "unnapplicable" for them. If I change the installation key from MAK to OEM, 1803 update starts install almost immediatly. 

    lunedì 18 giugno 2018 10:56
  • Hi Kari,

    Please see the marked solution for details, but approving the service stack update (KB4132650) via WSUS and allowing it to be installed solved the problem I had. If you can't find KB4132650 in WSUS via searching, then you might need to import this update into WSUS KB4132650.

    Scott


    martedì 19 giugno 2018 16:45
  • Thank you for your reply Scott. The KB4132650 is installed on the win10 1709 computers, but 1803 is still "not applicable" for them.
    mercoledì 20 giugno 2018 07:06
  • We aren't running 1803 yet due to numerous unresolved bugs and I am not aware of any service stack update for 1803 (I check https://support.microsoft.com/en-hk/help/4284835 for information on like service stack updates). I suggest that you create a new post just for your problem with 1803 and see if you can get support.
    mercoledì 20 giugno 2018 16:41
  • Thanks, I've already done that with no luck :-(

    https://social.technet.microsoft.com/Forums/en-US/0e337c65-c7e7-4ac2-b457-d944bc3b2ca1/1803-most-of-the-computers-quotnot-applicablequot?forum=winserverwsus

    mercoledì 20 giugno 2018 20:09