It's usually about this time, directly after a week of Patch Tuesday releases that I start collecting and collating all the update woes for the month. Usually there's quite a few and by now there's quite a few updates pulled, fixed, and delayed.
But, this month, things seem to be mysteriously quiet. And, it's almost scary. Except for a few very specific 3rd party incompatibilities, June 2015 has seemingly gone off without a hitch. You could attribute it to a small update delivery this month. On June 9, the software company rolled out just eight security updates and only two of them were labeled as critical.
I've kept my ear to the ground and listened to patch administrators do gut-checks with others in the community to see if they were missing something. The "all clear" has been given more than a handful of times. It looks like we've breezed through this month. Still, it's hard not to feel like it’s the calm before the storm and that a silent tsunami is just beyond the horizon. That's just the nature of things dealing with Microsoft's patches.
It's important now more than ever that Microsoft gets its patching quality fixed. Windows 10 will make its public appearance on July 29 for consumers, with business editions rolling out possibly in September. If you've read through the latest information on how patching will work for Windows 10 (catch up HERE) you get a sense that Microsoft has to be working to solve the updated woes it has heaped on customers for the past few years.
After testing internally and externally, Microsoft has plans to deliver updates to consumers first, as a sort of test bed, and then after issues are identified and resolved, will certify the updates as business ready. This should better protect businesses from dealing with failed and incompatible patches, but I don't envy those using consumer editions at all.
But, if this month is any indication, it's possible that Microsoft is already addressing its quality problems.
Nah. Can't be.
What about you? Are you dealing with patching problems this month? Let us know of we've missed something.
