When we first released Windows 10 in July 2015, we tried to explain the process by which servicing worked in what became known as the Current Branch/Current Branch for Business, or CB/CBB. As part of...
Updated May 31, 2018
Version 5.0
Blog Post
I think many were treating waiting for CBB like waiting for the first SP. Unfortunately, this was a doomed strategy. 1511 had a bug that borked systems with Logitech wireless receivers connected during installation. This occurred on all our Logitech systems even though we had the install delayed 8 months from RTM. Then 1709 had a bug that killed Outlook search on any system it was installed on that already had the MSI version of Outlook installed.. That 8 month delay didn't save us their either. We thought the delay would give the team a chance to fix the problems exposed during early adoption. But, that's not what happened. The only thing the 8 month delay did was give us a wealth of historical google results to help us get out of the mess. I personally thought that the CB and CBB naming was very clear and that SAC and SAC-T was very confusing. But, I get what the goal was. You were trying to break that "wait for the first service pack mentality." I too agree that quality needs to be more important. You're proven right the naysayers in my office that wanted to stay on Windows 7. Every time our help desk is knee deep in Windows 10 feature upgrade problems, someone reminds me that the Windows 7 systems are fine.