locked
Win 10 feature update won't run, says that my WSUS 3.0 SP2 Console isn't compatible RRS feed

  • Question

  • Win 10 feature update won't run, says that WSUS 3.0 SP2 Console (client, I assume) on my workstation isn't compatible with the upgrade.

    My current Win 10 is Version 1607 (Build 14393.1944)

    The "about's" on my WSUS client say "Update Services Version: 10.0.14393.347" and "Management Console 3.0 Version 1607 (OS Build 14393.1944)"

    Win 10 update process wanted to uninstall my WSUS client, but I stopped it because then I wouldn't have anything to use to talk to my WSUS server.

    Help is appreciated, thank you, SC

    Tuesday, January 2, 2018 10:44 PM

Answers

  • Hello,

    It turns out that my WSUS server is already 2012, and WSUS there seems to be new enough. Have now switched over to RSAT tools in Win10 Pro for administering WSUS. Uninstalled old 3.0 SP2 client (from when my machine was Win 7), but fragments were still left in ProgramFiles\Update Services. Once I got rid of those (which took some searching!), 1709 Win 10 upgrade ran OK. Thanks everyone for reading.

    • Marked as answer by SteveCRO2 Monday, March 26, 2018 4:35 PM
    Monday, March 26, 2018 4:35 PM

All replies

  • Hello,

    Based on my knowledge, to be able to use WSUS to manage and deploy Windows 10 feature updates, you must have WSUS 4.0, which is available in the Windows Server 2012 R2 and Windows Server 2012 operating systems. In addition to WSUS 4.0, you must install the KB3095113 and KB3159706 patches on the WSUS server.

    If you plan to deploy Windows 10 your environment, yet are still using WSUS 3.2, then we strongly recommend considering a migration sooner rather than later.  WSUS 3.2 cannot today and will not in the future be able to fully support Windows 10 servicing (specifically feature updates), and in order to experience the true vision for Windows as a service, you'll need to use WSUS 4.0 or later.

    Regards,

    Yan


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

    • Proposed as answer by AJTek.caMVP Wednesday, January 3, 2018 4:14 AM
    Wednesday, January 3, 2018 2:03 AM
  • WSUS 3.0 will only allow 'Updates' to a Windows 10 Version (so 1703 updates will work, 1709 updates will work, etc) however the Feature Upgrades from Windows 10 Versions to new Versions (1703>1709 for instance) is not supported.

    If you have an imaging system, you could get by with imaging your Windows 10 Versions, and then use WSUS 3.0 to supply them with updates within their Version, however this would be a work-around for the short-term. If you plan on having Windows 10 in your network, it's HIGHLY recommended to get a Server 2012 or 2016 license and run WSUS on there for the Windows As a Service (WaaS) idealistic approach


    Adam Marshall, MCSE: Security
    http://www.adamj.org
    Microsoft MVP - Windows and Devices for IT

    Wednesday, January 3, 2018 4:19 AM
  • Hello,

    It turns out that my WSUS server is already 2012, and WSUS there seems to be new enough. Have now switched over to RSAT tools in Win10 Pro for administering WSUS. Uninstalled old 3.0 SP2 client (from when my machine was Win 7), but fragments were still left in ProgramFiles\Update Services. Once I got rid of those (which took some searching!), 1709 Win 10 upgrade ran OK. Thanks everyone for reading.

    • Marked as answer by SteveCRO2 Monday, March 26, 2018 4:35 PM
    Monday, March 26, 2018 4:35 PM