Showing posts with label thurrott. Show all posts
Showing posts with label thurrott. Show all posts

Friday, October 14, 2016

Microsoft's flawed update strategy


Let's talk about updates.  Specifically, lets talk about updates in the context of Windows 10.

When Microsoft launched Windows 10 it was supposed to be the cure-all to the Woes of Windows.  It was to be everything to everybody regardless of your chosen device.  It would be the gateway to what you wanted to do instead of the sandbox (or litter box) for the things you HAD to do.

When it works it can be all that.  Unfortunately, it really isn't.

I've listened to the pundits and Microsoft apologists for over a year now.  How they go on touting its merits while in the same breath decrying their frustrations.

Simply put, Microsoft can't be trusted with the power Windows 10 gives them.

I've had my own frustrations with it having seen my production machine blue screen for no apparent reason over a dozen times in the past year.  In the 3 years prior the same machine running Windows 7  may have done it twice.



I'm tired of constant updates churning in the background while I'm trying to do actual work.  Sick of waiting 15 minutes for a system shutdown because Windows decided it was time to do some housekeeping.

My eyes bleed at the sight of full event logs warning of failed telemetry connections.  All because I refuse to turn my daily workflow into an episode of The Truman Show.  Spybot Anti-Beacon takes care of that but the price is endless bitching.

My PC is not a lifestyle device, my data under my and nobody else's purview. I expect to control my own environment.  I have no use for Cortana.  Quite simply, I don't have the buying or search habits to make it or anything like it benefit me.  Meaning I have no reason to be so forthcoming.

Am I a troglodyte?  Hardly, I just prefer to not have Microsoft curating my search results or my computing habits for that matter.  Even if they do consider it a "Feature."

But Microsoft doesn't see it that way.

The best example is the update process.  It's common knowledge that Windows 10 has essentially taken away your ability to exercise any disposition of updates.  Even if they brick your device.

Take the recent update that disabled millions of webcams.  We've come to find out that it was all due to one lone Microsoft Engineer who took the unilateral action to remove a codec without bothering to pass it through Q&A.  ( Thurrott said that on Windows Weekly 487 BTW)

I appreciate employee empowerment and all.  It works great for the auto industry in fact most auto workers have the power to stop an entire assembly line if they see a problem.  What comes next is a structured process to address it.  

But nobody makes the ultimate call by themselves.  Unless they work for Microsoft that is.  Where one poorly executed update can be unleashed on millions of devices worldwide without as much as a peer review.

If you're using Windows 10 there's no doubt you've spent at least a few minutes observing the update process.  It's all very clandestine: even the event logs won't provide you any illumination as to what's going on.  You just sit and watch that screen, cross your fingers, and hope the update goes well as it reboots 2, 3, 5 times...



The latest atrocity?  The endless loop of death from KB3194496 that for many users will never install correctly without first manually applying an out of cycle patch ( <--that links to it BTW) 

We reap what we sow and the crop is a load of manure.  In the old days we could just simply uncheck the update once we found out it was problematic.  Today we have to beg the good graces of Microsoft to acknowledge the problem in the first place.  Meanwhile our workflows and production goes to hell while Microsoft whitewashes it's official response.

I could care less what Microsoft's "telemetry" is telling them about the severity of the issue.  If they can't get a patch right why should I trust their telemetry as an indicator of anything?

Laissez-faire may be great for Free Market policy wonks but it's got no place in a platform that 20% of the planet relies on to actually accomplish something.

The user base should demand that the next patch they release give us back control of the update process.  At this point it's obvious Microsoft can't be relied upon to do it themselves.  

Here's a proposition...

I'll meet you half way Microsoft.  Let the users curate their own patches but turn off Cortana or the Store while it's disabled.  

I think that's a fair compromise and for those invested in the Microsoft way of doing things, it would be a reminder to turn the updates back on when the inevitable storm has passed.




Monday, January 13, 2014

9 comes after 8 and that's Windows' new name

Leo Laporte may have officially proclaimed the death of Windows 8 last year but Microsoft made it official this week.  The operating system previously known as "Threshold" has a real name, "Windows 9" and a real release target, April 2015.

According to Paul Thurrott, Windows 9 is meant to be everything Windows 8 wasn't.  For one thing, the desktop will regain its prominence as will the Start Menu.  Metro 2.0, as it's called, will be somewhat deprecated as more of a windowed app instead of a GUI mandate.

The bones have been rolled and the Shaman was right, Windows 8 couldn't succeed in spite of its futuristic aspirations.  It's not that Windows 8 is a flawed operating system, it's not and its performance and security underpinnings are second to none in the Windows world.  But that GUI...That collection of pulsating tiles that consumers were forced to swipe away just to get to their email spelled doom for the Windows known as 8.

Metro isn't a bad idea and I still hold firm to the belief that one day we'll see a workforce happily swiping, typing and talking to their monitors as easily as they send a text message now.  I get it Microsoft.  You were trying to push the concept of a Kiosk operating system that was not only visually attractive but with all those annoying menu bits out of the way. 

Microsoft saw how consumers eschewed scrolling down menus and tiny keyboards on their smart devices for simple taps and swipes.  The proof still exists with the success of Apple and Android devices while Blackberry languishes for all but the most faithful.

But it didn't translate well to the office.  With a stated 25 million copies sold with most of those likely pre-installs on new PC's (whose sales numbers were already suffering,)  Windows 8 just wasn't going to fly with the bean counters.

Incompatibility with legacy applications, an interface inconsistent with current workflows and no real justification to move from windows 7.  When you consider that many businesses are still just in the throes of moving off of XP, the  picture becomes clear.

Windows 8 was an operating system ahead of its time if not its market.  Consumers may be used to scratching and tapping away at their smart devices but not their PC's.  They still expect that "legacy" experience and that translates to corporate America as well. 

That's why 8 failed, If the Fortune 1000 isn't buying it, you just have to call a Microsoft operating system dead. 

Windows 9 is a pullback from the brink.  Still, in the long run the great experiment will cost them little.  There was no upstart, no competition waiting in the wings to unseat the giant from its throne.  Apple? the enterprise is more nuisance than market to them.  Expect OSX to disappear into an API for IOS within the next 10 years.  Linux?  If corporate customers won't tolerate a tightly integrated kiosk experience they won't stomach the wild West of an open source operating system either. 

At this point the best thing Microsoft could do to advance Windows is to split the development  between consumer and business releases again.  If you want one interface across all "consumer" devices then by all means do it.  Let it grace the likes of phones, tablets and yes, consumer PC's.  Just don't try to force it down corporate America's throat.

People don't like to be forced to do anything.  They need time to get used to it.  Windows 95 brought the desktop to the next step in its evolution.  It was more about clicks than menus and command lines.  Consumers got used to that and were soon demanding the same from their business PC's.  Thus came Windows 2000 which was really just windows NT with a facelift and some beefier networking bits. 

It was all about the interface and customers both corporate and consumer asked for it.  

That's the key, consumers have to feel like it's their choice.  If they want to be told what's good for them they'll buy an IPAD.