WUFB Clients are still contacting WSUS for Feature Updates RRS feed

  • Question

  • We're using WUFB to defer security patches and feature updates automatically and WSUS for anything that's not delivered by WUFB. 

    Despite this we're seeing significant numbers of clients showing in WSUS as needing 1903 and recent security updates. Frustratingly some clients are working correctly and are showing in WSUS as needing no updates despite having identical GPOs etc. applied. Any suggestions on troubleshooting why clients aren't going direct to Microsoft? RSOP is showing the right GPOs applied. Check for updates works fine.

    Searching the internet for suggestions hasn't been very fruitful as all I find are people complaining about the opposite problem with clients talking to WUFB when they shouldn't be.

    Thursday, May 23, 2019 1:39 PM

All replies

  • Hi,

    Windows Update for Business is intended for machines running Windows 10 Education, Professional, or Enterprise editions managed in organizations, it is not intended for consumer use. Please check if the Windows version of the client meets the above requirements.

    You are also considering rejecting the Windows 10 version 1903 feature update in WSUS. 


    Please remember to mark as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Friday, May 24, 2019 5:44 AM
  • Hi,

    All of our clients are Pro edition. 

    We're not planning on doing anything different with 1903 to any of the other feature updates, which is partly why I'm keen to solve the issue. I want deployment to occur at a predictable time as defined in the WUFB GPOs, not whenever the local admin remembers to approve the update in WSUS. 

    Friday, May 24, 2019 8:03 AM
  • You should be either using WUfB or WSUS - NOT both.


    Using WUfB in conjunction with WSUS doesn't work as you are experiencing.

    Adam Marshall, MCSE: Security
    Microsoft MVP - Windows and Devices for IT

    Friday, May 24, 2019 10:35 PM
  • It's an option that _should_ work.


    The way we're configured should put us in configuration scenario 3. That's not how clients are behaving however.

    • Edited by Kardrath Tuesday, May 28, 2019 10:47 AM typo
    Tuesday, May 28, 2019 9:56 AM