Microsoft is not to be trusted. The thought of them sending me a new automatic Windows Update overnight and possibly (read likely) breaking my computer, and me waking up to a mini-disaster drives me crazy. Therefore I turn off Automatic Updates, but that created a security concern because the OS stopped getting security patches when I stopped Windows from installing the November Update wayyyy back in 2015 when that was bricking everyone's installs. But I have finally solved the dilemma: the Security Updates themselves can be installed manually, easily, and WAY more safely than you ever believed possible!! - without BRICKING.
You can now have complete control over your OS back, without Microsoft meddling from afar.
If you follow this guide, you can always have the latest security updates. You can also wait up to 1 year for the OS build updates to get fully matured into the stable, non-disaster causing, procedure that it should have always been but never was. Then you can install the new build version when the old one gets retired. The first retirement of the initial build 10240-RTM happens tomorrow May 9th, 2017. In my case since I'm still on original 10240, this means I have until the next month's patch, June 13 2017, to install the 14393 anniversary update build without going out of date. What I am doing here is staying on the "LTSB" (Long term Servicing Branch) for as long as safely possible.
Microsoft is calling Windows 10 "The Last Version of Windows" because it is providing OS updates as a service, over the internet, almost exactly like what Apple can do with their OSX (which has been to multiple "versions", such as 10.11 (El Capitan) - by now).
They did a bad job at explaining exactly how all this works, so I am forced to write this blog.
Fortunately the Microsoft.com website has actually become quite helpful in the past few years, if you know where to look, and is where I obtained all this information from. I am just compiling it here for simplicity.
Each version is a rolling release, built off the last one, leading you to believe Windows 10 is Windows 10 is Windows 10.
THAT IS WRONG!!!1
(not talking about Home/Pro - thats called an Edition -(even those are the same codebase))
Versions of Windows 10 so far:
(sourced from Wikipedia)This site explains it further: https://technet.microsoft.com/en-US/windows/release-info
Find your Version :
Find out which version of Windows 10 you have by doing Start > Run: winver ,or going to the command prompt and type ver and look for the build numbers such as either of 10240, 10586, 14393, 15063, 16184.
1. OS App & Feature Updates:
The chart shows 5 versions. Microsoft only releases these about 1 time a year. You can consider each of these a "branch". Think of Microsoft as using Git/Github/TFS (version control). These refer to what I call "Feature Updates". Every time the OS updates are called stuff like: November Update, Anniversary Update, Creator's Update - they add some new Apps and Features.
You can read about what goes into all the Feature Updates for each of the versions here:
What's new in Windows 10 (all versions)
2. OS Security Updates:
Microsoft releases these exactly once a month (on the 2nd Tuesday of the month - "Patch Tuesday").
Since each of the 5 versions got branched and now have SLIGHTLY different stuff, ideally all need to get patched with the latest security updates, patches, bug fixes, and slight improvements. This is a lot of hard work for Microsoft. Patching 5 branches with the same patch of code is impossible, changes must be made manually to shoehorn the patch into an older OS. This is why, highlighted in blue in the chart above, is May 9th, 2017 - the date they will be "retiring support" for the original build 10240. They will issue the last Security Update (tomorrow), and stop working on it. It has been called the "Long Term Servicing Branch" (a term borrowed from the Linux realm). 2 years. Long Term.
After May 9th 2017, the NEW recommended older LTSB branch will be 1607 Anniversary Update, which should be good for another year or so.
Service Branch Version list (shown)
Pick the VERSION that corresponds to your build number:
When you need to check for updates, bookmark this URL directly: Windows 10 Update History List
How to Download:
When you've clicked on your proper version, you are given a list of updates. Click on the topmost recent one, and it will actually provide a Changelog since the last update, if you want to read through them all.
At the bottom there is a bunch of links, You want this one in red:
|This file size mentioned in blue is supposed to match the following link, but in this case it does not! - k Microsoft.|
Click on the Download button - Make sure you choose x64 for 64-bit OS, or unmarked means 32-bit x86. Then execute the .exe file. (If you chose wrong one by accident no big deal just get the right one).
Microsoft has very fast servers for this.
The update process will start immediately and look something like this:
This is the slim-patcher, not a full "panther Setup". Theres way less chance of killing the operating system, or getting stuck at an Pre-boot Update screen where you can't do your work, however it does still need a reboot.
But for 1 gig of new OS files, this completed relatively fast, in about 5 minutes for me. Now the OS is fully security patched, updated, protected - and not ready to brick itself at the next Windows Update.
They really are cumulative too.