If Microsoft Really Wants To Fix Windows 11, It Should Do These Four Things Asap

Kyle Kucharski/ZDNET

 Sign up for our News Alerts to ne'er miss an update.

ZDNET's cardinal takeaways

• Microsoft's scheme to attraction connected Windows 11 fundamentals is simply a bully first step
• A important adjacent measurement is to betterment nan Windows Insider Program
  
• More transparency astir creation decisions will help, too

Stop maine if you've heard this one: Microsoft releases a caller type of Windows packed pinch caller features and abrupt departures from nan acquainted personification interface, launching it pinch awesome fanfare. Customers respond pinch a operation of "Meh" and "Do not like" and "Ugh." In response, nan CEO makes immoderate guidance changes, and nan caller leaders committedness to get backmost to fundamentals and present what those customers person been asking for.

Am I describing nan guidance to Windows Vista? Windows 8? Windows 11? The correct answer, of course, is "All of nan above."

Also: Microsoft announces sweeping Windows changes - but nary apologies

In this latest installment of nan Windows break-fix saga, Microsoft's Pavan Davaluri, President of nan Windows + Devices business, wrote an unfastened missive to Windows Insiders (and, by extension, to nan billion-plus customers moving nationalist releases), emphasizing nan company's "commitment to quality."

The missive was agelong connected aspirational goals but short connected actual deliverables. Still, it was a measurement successful nan correct direction. 

Making Windows 11 much responsive and consistent? Yes, please. Improving nan baseline reliability of nan OS, drivers, and apps and making nan Windows Update acquisition much predictable, pinch clearer power complete restarts? Absolutely. Being "more intentional" astir really and wherever Copilot AI features are shoehorned into Windows? Finally!

Also: The Microsoft 365 Copilot motorboat was a full disaster

We should commencement seeing nan first examples of those initiatives successful nan adjacent fewer weeks. As agelong arsenic Microsoft is successful progressive listening mode, I'd for illustration to connection immoderate circumstantial suggestions connected really it tin present connected those lofty promises.

1. Make preview builds useful again

It's nary mishap that Davuluri's unfastened missive was addressed to members of nan Windows Insider Program. By definition, those are immoderate of Microsoft's champion customers, nan ones who are astir apt to supply useful feedback and to effort nan merchandise successful real-world usage cases that won't show up successful a testing lab.

Last November, I wrote a little history of nan Windows Insider Program, calling out my vexation pinch its gradual deterioration successful caller years. If you're looking for a logic why Windows 11 improvement has felt disjointed and out-of-sync pinch customers, this is astir apt nan spot to start.

Also: The Windows Insider Program is simply a confusing mess

A twelve years ago, astatine nan commencement of nan Windows 10 improvement cycle, Microsoft launched nan Insider program. It was a very large deal, because it gave firm customers, trainers, and enthusiasts a chance to effort retired a caller Windows type successful nan months earlier it shipped. With a fewer cardinal testers contributing bug reports and telemetry, location was a beautiful decent chance that superior bugs would beryllium squashed quickly, earlier they escaped into nan world.

That each ended successful 2022, erstwhile nan various Insider channels (Release Preview, Beta, Dev, and Canary) became disconnected from nationalist releases. My humble suggestion? Bring backmost those connections.

• The Beta transmission should beryllium a preview of nan adjacent H2 characteristic update, pinch monthly releases that gradually get much polished arsenic nan vessel day approaches.
• The Release Preview transmission should beryllium a preview of what's astir to vessel to nan public, pinch nan extremity of allowing admins to trial an upcoming merchandise to place immoderate problems earlier deploying it widely.
• Leave nan experimentation to nan Dev and Canary channels, which don't person to beryllium tied to a circumstantial release.

That doesn't look for illustration excessively overmuch to inquire for.

2. Decouple value testing from characteristic testing

One of nan astir profoundly counterproductive moves that nan Windows 11 developers made was to move nan Insider Program into a elephantine A-B trial for caller features. The archiving for a freshly released build mightiness spotlight a caller characteristic aliases a alteration successful nan personification interface, but not each tester would spot it. The consequence was wide confusion.

Also: I've been studying Windows telemetry for a decade - here's nan only mounting I move off

If my extremity is to stress-test nan value of a Windows build, this inconsistency drives maine crazy. If my extremity is to understand what's coming successful nan adjacent type of Windows, this inconsistency besides drives maine crazy.

To activity astir that gatekeeping, immoderate Insiders usage an unofficial, open-source command-line inferior called ViVeTool, which toggles these hidden experimental features on and off.

So why not let testers who want to tinker pinch features to opt successful to A-B testing? You could moreover archive nan features that each Insider who opts successful is testing, pinch nan action to move from type A to B and backmost again?

3. Ditch Controlled Feature Rollout successful nationalist releases

If you and I some instal nan latest nationalist merchandise of Windows connected hardware that is functionally nan same, we should person an identical experience, right?

Sorry, that's not nan measurement things activity anymore, acknowledgment to Microsoft's "continuous innovation" inaugural and a exertion called "Controlled Feature Rollout."

Here's really Microsoft describes that technology:

Microsoft is committed to delivering continuous invention by releasing caller features and enhancements into Windows 11 much often ... utilizing nan existing Windows monthly update process. Our phased and measured attack whitethorn present caller features utilizing Controlled Feature Rollout (CFR) technology¹, which is besides utilized successful nan Windows Insider Program and pinch Microsoft Edge.

Follow that footnote, and you get this explanation:

¹Using CFR, features whitethorn beryllium gradually rolled out, starting pinch devices that instal nan monthly optional non-security preview release. When we've validated that each characteristic is ready, we'll gradually rotation it retired to caller devices, and yet see it enabled-by-default successful a consequent monthly information update.

As I pointed retired past November, nan extremity down Controlled Feature Rollout seems logical -- making judge changes don't disrupt activity for group moving released versions of Windows. But isn't that nan constituent of nan full Insider program? Doesn't Controlled Feature Rollout mean that each customer moving a released type of Windows is now a personnel of yet different trial channel? So why do my 2 PCs moving nan existent nationalist merchandise of Windows 11 person different Start paper layouts? If I americium a firm trainer, really americium I expected to show nan group successful my people that immoderate of them person a different group of features than their peers and I person nary thought erstwhile their type will change?

And arsenic agelong arsenic I'm asking questions, why are caller features being rolled retired successful what is now called a information update?

If you can't reliably present a characteristic to each customer, it's not fresh for nationalist release. Make those nationalist builds activity nan aforesaid for everyone, arsenic agelong arsenic nan hardware supports it. If 2 machines moving nan aforesaid build of Windows 11 are broadside by side, they should person nan aforesaid features disposable to them.

4. Disclose much of nan 'why' down decisions

When Steven Sinofsky took complete arsenic caput of Windows improvement aft nan disappointing and chaotic Windows Vista release, 1 of nan things he introduced was a blog called "Engineering Windows 7" -- aliases E7, for short. It was published from August 2008 done February 2010. (A mostly complete transcript is available connected nan Internet Archive, courtesy of Sinofsky, for those who are curious.)

Those pages person agelong since been purged from Microsoft's servers, but this unsigned post from 2008 connected nan Windows Experience blog somehow survived:

The Engineering Windows 7 blog is designed to create an unfastened chat about how we're making nan adjacent type of Windows – presently codenamed Windows 7 – and to create a inheritance of knowing for nan engineering decisions made in bid to vessel Windows 7. [emphasis successful original]

Engineering nan adjacent type of nan astir utilized operating strategy to-date is simply a very analyzable package project. Why? Because Windows has a very ample personification guidelines and that personification guidelines is very diverse.  Planning nan adjacent type of Windows (and yet processing it) is simply a immense under-taking arsenic it requires Microsoft to study and understand nan needs for each types of customers that usage Windows today. On nan Engineering Windows 7 Blog, you tin expect a 2 measurement chat connected really those customer needs are balanced retired to present Windows 7 into nan hands of customers.

The 1 point you won't find connected nan Engineering Windows 7 Blog is awesome merchandise announcements. The attraction is to simply talk nan engineering of Windows 7.  

The E7 blog was genuinely revolutionary, pinch elaborate discussions from engineers and merchandise designers of why they made decisions connected really to build what became Windows 7. It was besides refreshingly free of nan marketing-speak that defines truthful overmuch of what gets published connected Microsoft's Windows blogs today. Most importantly, that blog accomplished thing crucial: It said straight to skeptical customers who were convinced that Microsoft had changed their favourite characteristic for purely arbitrary reasons.

If nan group building Windows want to person customers that they're listening to feedback, bring backmost that level of method transparency. Just show nan trading group to support their hands disconnected it.