July tends to be a leisurely month in Home windows and Workplace patch land, and this one’s no exception.
We had a little bit of a thrill July 15 when Outlook stopped working on tens of millions of PCs all around the world, however Microsoft mounted the bug 4 hours later by updating its servers.
People who pay for Home windows 7 Prolonged Safety Updates felt rightfully miffed when the brand new .NET Framework 4.eight patch, KB 4565636, refused to put in. Microsoft took 9 days to repair the bug and re-ship the patch.
We additionally came upon this month that Microsoft’s means of dealing with the newly-reinstituted “optional, non-security, C/D Week” patches runs all around the lot.
The chicken-little cries to “Patch NOW” evaporated into stony silence as July rolled alongside, with one crucial exception: For those who’re operating a Home windows Area Title Server, it is advisable to get it patched. Professional tip: For those who aren’t certain whether or not you’re operating a Home windows DNS, you aren’t.
Outlook goes down for the rely
For those who run Outlook on Home windows, you in all probability couldn’t get it to work for about 4 hours on July 15. There’s been loads of inner finger-pointing inside Microsoft, but it surely appears like the issue stemmed from a foul repair made to Microsoft’s servers. Onerous to consider a crippling bug like that would roll into manufacturing with out elevating an alarm someplace, but it surely did.
Microsoft constructed some fancy new checking mechanism into the newer variations of Home windows-based Outlook. It was working simply tremendous till… anyone modified one thing on Microsoft’s servers. Kaboom. No extra Outlook.
Many of us found that they might use a browser and simply log into their account at outlook.com – the issue was with the Home windows-based model of Outlook. However many additionally found the thrill and frustrations of chasing down yet one more bug.
.NET patch refuses to put in on Win7 machines with paid Prolonged Safety
People who’re paying for Win7 Prolonged Safety Updates weren’t glad when this month’s .NET Framework 4.eight patch refused to put in. There’s a prolonged dialogue concerning the trigger on the Microsoft Solutions discussion board, however the issue was traced to a buggy detection of the incorrect license kind.
9 days later, Microsoft re-issued the patch, saying:
“On July 23, 2020, update KB4565636 v2 was released to replace v1 for .NET Framework 4.8 for Windows 7 SP1 and Windows Server 2008 R2 SP1. The v1 update did not install for customers who had certain ESU configurations. The v2 update corrects the issue for customers who could not install the v1 update.”
Sure, even of us who’re paying for patches get unhealthy ones.
The mess with elective updates
July was going fairly nicely till Microsoft launched its “optional, non-security, C/D Week” patches and the Cumulative Replace Previews for .NET Framework 3.5 and 4.eight on Win10. Microsoft stopped issuing these sorts of patches in March, citing the influence of the COVID scenario. Who wants preview patches gumming up the works today with a pandemic occurring?
Sadly, patching proponents prevailed, and we began getting these “optional” patches once more this month. Win10 1809, 1903, and 1909 received patched, though model 2004 (as of now) didn’t.
It appears just like the .NET preview patches aren’t behaving the identical means because the Win10 preview cumulative updates, resulting in loads of confusion. It now seems that the Win10 model 1903 updates behave in a different way than 1909. It’s a bifurcated – now trifurcated — mess.
To its credit score, although, Microsoft isn’t pushing the preview cumulative updates out to all machines. The main points are unclear, the documentation basically nonexistent, but it surely appears like these complicated “optional, non-security C/D Week” updates are solely being supplied to machines which can be enrolled within the Home windows Insider Launch Preview Channel.
If that holds true for future months’ elective patches, it’s a giant enchancment: Fewer unsuspecting Home windows customers will by accident set up the take a look at patches.
The push to model 2004
Microsoft’s increasing its push to Win10 model 2004, despite many complaints that the two-month-old model simply isn’t but prepared for prime time. Home windows 10 model 1809 customers are getting pressured onto model 2004, despite the fact that 1809 doesn’t attain Finish of Service till November. We even have an energetic rescue mission underway for a Win10 model 1903 person who’s attempting to maintain 2004 off their machine.
With all of the conflicting, overlapping, deprecated, poorly documented patch settings operating round, it’s exhausting to maintain up.
Patching issues? Hit us on AskWoody.com.