Share This Post

Windows 10

Microsoft Finally Comes Clean on October Blue Screens

Without offering an apology, Microsoft has issued a KB article to briefly explain this month’s big updating faux pas. Instead the company says “they are aware” of it and “they have corrected” the situation:

Windows devices may fail to boot after installing October 10 version of KB4041676 or KB4041691 that contained a publishing issue

 

  1. WSUS/SCCM Administrators that synced the October 10th update (KB4041676 or KB4041691) before 4pm PDT October 10 may still have these KBs cached.
  2. WSUS/SCCM managed devices that downloaded the October 10 KB4041676 or KB4041691 update with publishing issues and have devices in a pending reboot state.
  3. WSUS/SCCM managed devices that installed the October 10 KB4041676 or KB4041691 update and are unable to boot and/or may land on a recovery screen.

 

Guess what? Consumer devices weren’t affected. If a computer or device was configured to get updates directly from Microsoft Update, there weren’t any problems. The problems only occurred for “managed devices” or those computers that are being properly maintained in a corporate setting. For a company that is turning its attention completely to businesses and shedding any semblance of consumer services, Microsoft’s continual lack of attention to update quality here is unforgiveable. If this were a one-off issue, it wouldn’t be a big deal. But, for the last couple years, the number of monthly flaws in updates have caused customer pain and mistrust.

I’m calling for a renewal of Trustworthy Computing – but this time with a keen eye on delivering trustworthy updates on instead of security. Microsoft’s inability to deliver fully trustworthy updates have altered patching policies in ways that keep companies in a state of vulnerability because patching administrators are more afraid of sending business productivity into a screeching halt instead of playing Russian roulette with security and performance updates.

This has gone on too long. Long before Windows 10’s new servicing model was communicated, I said that Microsoft needed to halt operations, take a patching hiatus, and figure out where the quality issues existed and fix them, because it would be too late when a constant stream of updates began delivering. That never happened and here we are where we are.

Microsoft consistently says it listens to customers. Says that some things it delivers is because of customer feedback. But, in truth, customers are left scratching their heads, wondering who Microsoft is actually listening to and if they are only selectively listening and heeding to the things that fit the “refresh” strategy. I tell you what — let’s “Hit Refresh” on the updating and patching processes.

This really needs to be fixed.

Customers need to step up and speak out in a way that gets attention.


Follow me on Twitter

Add me to your Google+ circles

or

Connect with me on LinkedIn

Looking for an awesome, no-nonsense technical conference for IT Pros, Developers, and DevOps? IT/Dev Connections kicks off in San Francisco in 2017!

IT/Dev Connections

Share This Post

A community professional, keynoter, and evangelist who has driven social media and marketing strategies, editorial successes, delivered customer successes and built some of the largest and longest-running online communities. Rod has created, managed and grown small, medium, and mega-sized conferences; run entire editorial teams to deliver record traffic and market leadership; as product manager, directed the success of hundreds of product releases; supported sales and marketing to ensure customer success; developed, run and sold businesses; written thousands of technical articles, white papers, case studies, and technical documentation; hosted and delivered hundreds of attendance shattering webinars and virtual tradeshows; and delivered keynote speeches and sessions at a wide variety of events including conferences, webinars, events, and user groups.

Leave a Reply