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
Well, thanks for being so nice, John. It is not every day that I see someone that responds "thanks" to "Windows 10 has low quality", even though what I said is not an expression of contempt. It was a technical fact. You see, I've been part of many Microsoft beta programs, and even remember the days of the ill-fated Microsoft Connect. I've been with Microsoft for far too long now, so much so that I have feelings for it. And I am saying this with all the feelings I can commend: Windows 10 could really some quality improvements.
But I am afraid I disagree with Mr. Kerr here. Explanations and justifications are very poor replacements for doing it right in the first place, not to mention that Microsoft has done this a lot before and I am not confident that customers would want to listen anymore. "When to install Windows 10" has become far too serious a conundrum.
What Microsoft should have done:
- Customers must have never been exposed to jargon such as "SAC", "SAC-T", "CB", "CBB" or (most emphatically) "Windows Update for Business". Windows Settings app should have said "Install feature updates when:" (a) "After it reaches general availability" and (b) "After it reaches general availability and is tested for widespread use in organizations".
- There should have been am Upgrade Installer component in charge of getting feature updates that would let users schedule it to download during low-cost hours (e.g. 2 AM to 9 AM, depending on ISP), temporarily pause it, and see its progress. Trying to hide something so as a big full OS upgrade in the background was a supreme mistake on Microsoft's part. Just as no country takes kindly to 4 tonnes of unknown shipment crossing its borders, no user would take it kindly to 4 gigabytes of unannounced executable code entering its computer.
What Microsoft should do now:
Forget jargon and explaining them. Focus on bugs. If they are addressed swiftly, nobody cares what you refer to as SAC or SAC-T; for them, they are good enough anyway. If they are not addressed swiftly, no amount of explanation would improve customer satisfaction. All explanation does is to drain Microsoft resources on writing and explaining stuff.