Update on WSUS 3.0 SP2 End of Life


As you may have seen, there has been an update to the extended support lifecycle for WSUS 3.0 SP2 (WSUS 3.2).  We received feedback that ending this product’s life in July 2017 would cause a significant disruption for those Windows Server 2008/R2 deployments that planned to rely upon it until January 2020.  As such, the end of life for this product is now January 2020.

For those that currently rely on WSUS 3.2, please use this extension as an opportunity to plan a smooth transition to WSUS 4.0 (Windows Server 2012 or 2012 R2) or even our newest offering (Windows Server 2016) that will be available later this year.  Especially for larger businesses, migrating a WSUS hierarchy is nontrivial, and may take much of the extra time that has been granted for this operation.  We’ve assembled a collection of resources that will help inform your migration efforts; should you have any trouble with the process, feel free to reach out on our TechNet forum for assistance.

Finally, it bears repeating: 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.


Comments (5)

  1. Anthony says:

    I find this interesting that Microsoft seems to want to stop support of a core component of an intergrated feature of a OS that has an end of life in the future.
    This is the trouble when you start baking in features into the OS but don’t want to keep supporting them. Sorry but you have to! Next time think about making the features true add ons that have their own installers and not enbedded in the OS.

    1. Actually, Anthony, it’s not baked into the OS: if it were, then the lifecycle discussion would have been much simpler (as it is with Windows Server 2012/R2). The rub here is that WSUS 3.0 started as an external feature only downloadable via Download Center, and at some point a hotfix allowed you to make this appear as a role in Server Manager. That hotfix was included in Windows Server 2008 R2 SP1, which provided an appearance that the products had merged, when in fact they hadn’t.

  2. Hackers says:

    “As such, the end of life for this product is now January 2020”
    wisdom won!

  3. The Windows Internal Database used by WSUS 3.0 SP2 on Windows Server 2008 R2 is based on SQL Server 2005 which is no longer supported. Is the WID component of Server 2008 R2 still supported, and if so, is there an official document stating that it is, in fact, supported?

    The problem is that WID is being flagged by vulnerability scanners as being an unsupported version of SQL Server 2005. I need official documentation to prove that this is a false positive and won’t require corrective action.

    This is for a federally-regulated institution, and such documentation will be necessary if it is indeed a false positive.

Skip to main content