SCCM 2007 2012 Support for Windows 10 Anniversary Update 1607

To manage Window 10 1607 (anniversary update), we need to have SCCM current branch. SCCM 2007 and SCCM 2012 can’t support Windows 10 1607 version?  This information was already there in Microsoft’s last years blog post. The ConfigMgr SCCM 2012 Supported Configuration article on TechNet only lists support for Windows 10 Enterprise LTSB 2015. I don’t know for sure whether Microsoft support ONLY core management of Windows 10 1607 (no OSD and new features) with SCCM 2007 and 2012. If you look at the history they support the core management features of new Windows operating systems however they won’t support the new features and OSD. Whether this is true for Windows 10 1607? I don’t know .. As per the below blog released on 2015, only Windows 10 1507 and Windows 10 1511 are supported with SCCM 2012.

“SCCM 2012 supports Windows 10 version 1507 (build 10.0.10240) and 1511 (build 10.0.10586) for the lifecycle of these builds. Any new Windows 10 CB/CBB builds released in the future will not be supported With ConfigMgr 2012 and will require System Center Configuration Manager current branch for supported management.” More details – here.


Some  more useful Links of Windows 10 1607 in the below list :-

How to download the Windows ADK for Windows 10 1607 anniversary update?, visit the Hardware Dev Center

How to download Windows 10 1607 Anniversary update from MSDN and VLSC ? the Volume Licensing Service Center (for Volume License customers) and from the MSDN Subscriptions Center (for Visual Studio/MSDN subscribers).

How to download Windows 10 Anniversary Update 1607 for your home machines?  you can get the Windows 10, version 1607 update today from Windows Update or Windows Update for Business. If you are not getting latest updates from your Windows 10 machine then try installing – Windows 10 update history utility from here. 

By when Windows Servicing of Windows 10 1607 will be available in  ConfigMgr SCCM CB 1606? You can get the Windows 10, version 1607 update on August 16th.

How to download Windows 10 Anniversary update for Free ? Download Free Windows 10 Enterprise Evaluation to test Windows 10 1607 free for 90 days.

When will be Windows 10 Enterprise LTSB 2016 media available ? beginning October 1st.

Reference – here


About Author 

Anoop is Microsoft MVP and Veeam Vanguard ! He is a Solution Architect on enterprise client management with more than 13 years of experience (calculation done on the year 2014) in IT. He is Blogger, Speaker and Local User Group Community leader. His main focus is on Device Management technologies like SCCM 2012,Current Branch, Intune. He writes about the technologies like SCCM, SCOM, Windows 10, Azure AD, Microsoft Intune, RMS, Hyper-V etc...

    Find more about me on:
  • googleplus
  • twitter
  • facebook
  • linkedin
  • youtube
Posted in: ConfigMgr (SCCM), Windows 10


  1. Have you seen any issue with Windows 10 1607 not submitting Hardware/software Inventory with SCCM 1602? We have been testing several 10 1607 and upgrade and fresh builds and none of them seem with report back where are all our Win 10 RTM and 1511 work fine.

    • Chris Roberts says:

      Hi Eric,

      We’re seeing exactly the same issue on SCCM 1606. Working with MS now to work out what is going on but this is a real pain. We see the HW inv leave the client, just doesn’t get processed by the MP at all.


    • Chris Roberts says:

      We’re currently seeing exactly this issue in our environment on SCCM 1606. Working to find a solution at the moment but wondering if we’re seeing a bug here. Another person has posted a thread on technet about this as well.

    • Chris Roberts says:

      Hi Eric/Anoop,

      Just come off a call with Premier Support and we have a work around for this, but not entirely happy with the workaround. At the least it will allow us to run the HW Inventory while we work out why this is happening.

      To implement this you need to change the following registry key:

      HKLM:\SOFTWARE\Policies\Microsoft\Windows NT\CurrentVersion\EFS\EfsConfiguration – change the value from 1 to 0. Reboot the system.

      This will change the Encryption File System to enabled (yes, 0 does equal enabled). More about this is available here:

      The big change you have is that your end users can suddenly encrypt files and folders on their system. They’ll come running when their system crashes and they can’t retrieve the data as well. I’m keeping this as a workaround at the moment so we can continue testing with Windows 10 1607 release. Will see what else we can dig up and keep up the pressure on MS Premier Support.

      Have also posted this workaround here

Leave a Comment and Contact Anoop