Microsoft released KB 3095113 to enable future Windows 10 feature upgrades. Whether you will deploy upgrades or not, you need to know what this hotfix does and how not applying it can break WSUS.

Update: We have a new post about the broken Windows 10 upgrade classification.

Windows 10 completely changed the traditional wipe and reload method for OS upgrades by releasing regular feature upgrades. These upgrades are not your simple monthly updates or combined cumulative updates. Each new release brings new features, deeper management, and a new version number. In essence, the upgrades affect the entire OS build – not the individual components that normal updates apply to.

The first major update, Windows 10 1511, will be released to WSUS within two weeks. Deploying this update gives you an easy and automated way to take existing Windows 7, 8.1, and 10 clients to this latest OS build. To do this, though, your WSUS install will need to be patched with KB 3095113. Even if you don’t plan on deploying this upgrade, you will probably want to install this patch so that WSUS won’t break in the future.

The Upgrades classification missing from SCCM 2012 R2

The Upgrades classification missing from SCCM 2012 R2

What is KB 3095113, and how do I know if I need it?

Windows 10 1511 and future upgrades rely on two core WSUS changes. The first change adds a new update content file type. The second change provides a new Upgrades WSUS classification. Both of these are handled by KB 3095113. While you read the rest of this guide, register and download the KB 3095113 hotfix here.

KB 3095113 applies to WSUS 4.0 instances running on Windows Server 2012 or 2012R2. Additionally, Server 2012 R2 will need the Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update: April 2014 (2919355) update installed as well. Due to the age of this perquisite update, most servers should already have it.

If you are running an earlier version of WSUS, you technically don’t have to worry about this, as Microsoft will not support these feature upgrades on those older WSUS versions. This lack of support includes SBS 2011. Regular patch Tuesday security updates (and the like) will still be deployable by these older versions of WSUS for the Windows 10 operating system.

How will not installing KB 3095113 break WSUS 4.0?

As discussed above, KB 3095113 adds the components (and classification) needed to deploy future feature upgrades. To quote the WSUS product team blog, “WSUS [4.0] may be able to see the Windows 10 1511 feature upgrade even if it can’t properly download and deploy the associated packages.”

The Upgrades classification available in WSUS 4.0

The Upgrades classification available in a patched WSUS 4.0

If a WSUS administrator checked the Upgrades classification under Product and Classifications without having this hotfix installed, the WSUS database would be populated with unusable data. In order to deploy upgrades in the future, this data would need to be removed. At the time of this writing, the steps for cleaning up this mess are not available from Microsoft.

Microsoft’s recommended guidance is that, if you ever intend to deploy Windows 10 and take advantage of these upgrades, you will have to install this patch first. Even though the update is a technically a hotfix, the WSUS team states, “We have tested it the same as we would any Windows Update release, so there is no reason to wait to install the update on your WSUS 4.0 servers.” Personally, I would install it regardless of current Windows 10 deployment plans. This bit of prevention can save you a headache later. If you still haven’t downloaded the hotfix, you can do so here.

What do you think of the Microsoft OS upgrade plan? Will you be installing this hotfix and deploying Windows 10 1511?

Update: We have a new post about the broken Windows 10 upgrade classification.

  1. Avatar
    Michael 8 years ago

    At the moment the download link for the hotfix is not available.

    “Sorry, the page you requested is not available.
    The page you were looking for is currently not available. The address may not be correct, or there may be a temporary problem with this site.”

  2. Avatar Author

    Hey Michael – that Microsoft link should be back up now – just tested it on my machine.

  3. Avatar

    Will this hotfix eventually be pushed out to the standard Windows Update channel? Only reason I’m asking is that we don’t currently have any 2012/R2 WSUS boxes (still on 2K8R2 – no comment) but when I eventually get around to deploying one, will I have to remember to manually install this hotfix? Or if I just fully patched the server with WSUS service installed, I’ll be okay?

  4. Avatar

    Err I just read the following on technet blog,

    “For your convenience, we’ll be releasing the update more broadly to DLC and Catalog, as well as to WSUS itself, in the first quarter of 2016. ”

    So that answers my question!

  5. Avatar
    bcweis 8 years ago

    So… patientally waiting for the way to repair for those of us that clicked the magic checkbox before installing the hotfix… I manually added the MIME types required to IIS, and now the downloads make their way to clients, but the installation fails. I wonder if I remove the WSUS role, then re-add it, apply the hotfix before first sync, if that would do it. (I assume yes, but it’s a lot of work).

  6. Avatar Author

    I would wait for the KB to be released (should be any day).

  7. Avatar
    Reafidy 8 years ago

    Is there a fix out yet for those of us who didn’t install KB 3095113 prior to downloading the updates?

  8. Avatar Author

    No word yet…

  9. Avatar
    Rodrigo Fronza 8 years ago

    Hi Joseph
    I installed KB3095113, in my WSUS console in classifications shows the “Upgrades” option, ok.
    Now in my SCCM 1511 console in Point Software Update does not provide the option of it, seeing the log Wsyncmgr.log see no synchronization error.
    Within the log this way:
    sync: Starting WSUS synchronization
    sync: synchronizing WSUS categories
    sync: synchronizing WSUS updates
    sync: synchronizing WSUS updates, processed 78 out of 78 items (100%)
    Done synchronizing WSUS Server SCCM01.server.local
    SyncGracePeriod not set, use default 120000
    You have any idea?

    Grateful for the attention

  10. Avatar
    Michael 8 years ago

    Any word from Microsoft how to fix the wrong entries in the database if we downloaded these updates before applying the fix?

  11. Avatar Author

    I haven’t seen any updates from the WSUS team about this.

  12. Avatar
    FCW 8 years ago


    The entry in the Comments Section by “This Drove me Mad” 26 Jan 2016 4:28 PM on explains how to fix Wrong entries in the Database.

    It worked successfully for me.

  13. Avatar
    Steve C 8 years ago

    If you did sync the upgrades before installing the KB… Technet have provided a powershell fix:

  14. Avatar Author

    Thank you both for the updates!

  15. Avatar
    Thinh 8 years ago


    Do i need to install 3095113 on all servers where WSUS role is installed for only on the server with WSUS database?


  16. Avatar Author

    I am unsure as I don’t have a test environment setup in this manner. I don’t think it will hurt to do so though.

Leave a reply

Your email address will not be published. Required fields are marked *


© 4sysops 2006 - 2023


Please ask IT administration questions in the forums. Any other messages are welcome.


Log in with your credentials


Forgot your details?

Create Account