How to ensure you're running a stable Windows 10 version

http://www.infoworld.com/article/3148676/microsoft-windows/woodys-win10tip-wait-for-a-stable-version.html
 
TL/DR;
 
Here are the versions of Windows 10 to date:

• 1507 -- the original version of Windows 10, codenamed Threshold 1, OS build 10240
• 1511 -- the "Fall Update" later renamed "November Update," codenamed Threshold 2, OS build 10586
• 1607 -- the "Anniversary Update," codenamed Redstone 1, OS build 14393

And the widely expected (and already named, internally):

• 1703 -- the "Creators Update," codenamed Redstone 2, OS build not yet determined

If you're in charge of your own updates, it would behoove you to wait for the "Current Branch for Business" designation until you upgrade your system. Cynics say that Microsoft is using individual Win10 users (both Home and Pro) to test upgrades on millions of machines before certifying them fresh for businesses. I would have a hard time arguing with that characterization.
We've seen the cycle twice to date, in the transition from 1507 to 1511, and in the move from 1511 to 1607. Here's how the dates have gone:

• Version 1507, released July 29, 2015, was immediately declared Current Branch for Business, as the first of its kind.
• Version 1511 released Nov. 12, 2015, was promoted to CBB on April 8, 2016. It spent 148 days in consumer-level testing.
• Version 1607 released Aug. 2, 2016, promoted to CBB on Nov. 29, 2016. It took 119 days before reaching the higher level.

Jim Roseberry
FWIW, I haven't run any version of Win10 that I found unstable.

Regardless, if you are a pro, you should consider your business first.  Why be a beta tester with your bread and butter?
 
Big companies with IT departments test operating system updates thoroughly in-house before rolling them out into production. 
 
You don't miss out on anything by waiting and staying one release behind.  Except, maybe problems that will get fixed before you update ...
 

Jim Roseberry
The Anniversary Update caused some issues...
That's somewhat par-for-the-course when dealing with older hardware - where there are no further driver updates.

 
You raise a good point here.  Many folks do attempt to update with their older hardware.  They do not have personal IT experts advising them if they should or not.  It's often been said that maybe it's better to buy new hardware with the OS pre-installed and tested on that generation of hardware.  Or just keep running what you have, as long as it is supported. 
 
The big change that I see here with Windows 10, is that it's like a new OS release each time they roll out a major annual feature release.  That is problematic for anybody to figure out where their drivers get left behind, until they stop working anymore ...

Windows 10 Release 1607 just graduated to CBB status 10 days ago, so should be considered as stable for business now.  I guess that means it's fully patched after you apply any current roll-up patches.

I take the "CBB" status to be for business systems and not for individual users.  I am a retired LAN/WAN Network and Hardware Help Desk Manager for a Federal Government Agency.  My area of responsibility was all our Agency field offices, basically west of the Mississippi to the Rocky Mountains.  We never implemented any software update, whether it was an OS update or an applications software update until it was tested and certified by our Computer Analyst department.  The agency had large IBM mainframes for the network (running VTAM/CICS) and the same with those, any update that IBM or whoever issued was certified before it was released to the production systems (and even then there were tests before the production systems were put back on line).  Lots of $$$ can be affected if computer systems are down or not working correctly or in our case the field offices were automated to the point if their computers were down they may as well lock the doors and go home.
 
If someone is running a commercial recording studio and relying on computers, I would have at least two full computer systems, one for production and another as backup and possibly a third that I could use as a test system. Any updates, whether OS, recording program, device drivers, etc would be first installed on the test system and if all worked then it could be installed on the production system(s).   

That is what I meant, sorry.
 
I've been in electronics and maintenance since 1955 in the Air Force and worked (maintenance) starting in 1966 with RCA Service Co on the Air Force Eastern Test Range, Ascension Island tracking station.  I also worked as a programmer for NASA on the Apollo program.

abacab

Jim Roseberry
FWIW, I haven't run any version of Win10 that I found unstable.

Regardless, if you are a pro, you should consider your business first.  Why be a beta tester with your bread and butter?
 
 

FWIW, we have clients who are rock-stars... and others who are professional composers for TV/Film on tight deadlines.  IOW, They can afford little to zero down-time.
 
Backups and contingency plans are a must... and should be in-place prior to any update being applied.  
 
I've mentioned this before...
When we were kids, my friend's dad used to lecture us about the "six P's".
"Prior planning prevents piss poor performance"
At the time, we didn't get the gravity of what he was saying (young/naive).
 
If you're well prepared, there's no fear of installing updates.
Worst possible scenario, you roll-back... or pop in that cloned boot drive (from the previous configuration).