Windows 10: Support for RTM build till May 2017

Are you using Windows 10 Build 10240 (the RTM version from July 29, 2015), because your machine fails to install feature upgrade to Anniversary Update (Version 1607). Microsoft has extended support until May 2017. And there is also a trick, to install security patches after May 2017, as well, as you can prolong support for Windows Vista and Windows 8.


Advertising

Background: Windows 10 End of Life dates

Microsoft supported each Windows version fir 10 years, the first 5 years sees mainstream support with bug and security fixes. The last 5 years during life time, a Windows version receives extended support, where Microsoft provides security updates. An overview may be obtained from Microsoft’s Windows lifecycle fact sheet,

But what’s with Windows 10? This operating system is delivered as Windows as a service (SaaS), so the OS will be updated continually via feature upgrades. Microsoft states the end of mainstream support for Windows 10 released in July 2015 to October 13, 2020, and extended support ends at October 14,2025. But this is only valid for Windows 10 Enterprise LTSB.

Support for Windows 10 ends in March or May 2017?

In January 2016 I’ve published the blog post Support for Windows 10 RTM ends March 26, 2017, based on dates, published by Microsoft within an announcements in a blog post Windows 10 v1607 media now available published on January 19, 2017.

With the availability of Windows 10, version 1607 to the VLSC on January 26th, the grace period for Windows 10, version 1507 will begin. That means, after May 2017, Windows 10, version 1507 will no longer be serviced as only the two most Current Branch for Business (CBB) versions are actively serviced. In a first version of this article, Microsoft wrote about a 60 days grace period ending March 26, 2017 (see screenshot below).


Advertising

But recently we leaned, that Microsoft postponed February 2017 patch day to March 2017 (see What’s happened with Microsoft’s February patchday?). And Microsoft also has amended the Technet article Windows 10 v1607 media now available.

Now they just write about a grace period, no 60 day limit is mentioned anymore. Instead they are saying, support for Windows 10 RTM ends in May 2017. In my reading, Windows 10 RTM won’t receive further updates from June 2017 onwards.

But wait, there is an exception …

Ok, there is an Windows 10 Enterprise LTSB for volume license customers. According to Microsoft’s Windows lifecycle fact sheet, main stream support ends October 13, 2020, and extended support ends at October 14,2025. That means, Windows 10 Enterprise RTM (V 1507) LTSB still should receive updates till July 2025.

So you can download cumulative updates for Windows 10 RTM from Microsoft Update Catalog after May 2017 and install the packages manually. BTW: This is a way, to keep a Windows 10 RTM install (V1507, Build 10240) until 2025 up to date (for instance within a vhd install).

Uh, we still can patch Windows Vista and Windows 8

Some users are still using Windows 8 – probably the machines aren’t upgradable to Windows 8.1 for several reasons. Microsoft has ended support for Windows 8, because Windows 8.1 is available.

Blog reader André mentioned within this comment (German), that Windows 8 users are able, to grab updates for Windows Server 2012 from Microsoft Update Catalog and support Windows 8 (Build 9200) with updates.

André mentioned also within this comment (German), that Windows Server 2008 receives updates till January 2020 (same end of life as Windows 7). Extended support for Windows Vista ends in April 2017. But after this period, users can grab security patches for Windows Server 2008 and try to install it under Windows Vista. So the end of life of a Windows Vista machine can be (probably) extended to 2020. I don’t have Windows Vista machines, so just give it a try.

Similar articles:
Support for Windows 10 RTM ends March 26, 2017
What’s happened with Microsoft’s February patch day?


Advertising


This entry was posted in Security, Windows and tagged , , . Bookmark the permalink.

Leave a Reply

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