![]() Yes, even folks who are paying for patches get bad ones. The v2 update corrects the issue for customers who could not install the v1 update.” The v1 update did not install for customers who had certain ESU configurations. NET Framework 4.8 for Windows 7 SP1 and Windows Server 2008 R2 SP1. “On July 23, 2020, update KB4565636 v2 was released to replace v1 for. Nine days later, Microsoft re-issued the patch, saying: There’s a lengthy discussion about the cause on the Microsoft Answers forum, but the problem was traced to a buggy detection of the wrong license type. NET Framework 4.8 patch refused to install. But many also discovered the joys and frustrations of chasing down yet another bug.NET patch refuses to install on Win7 machines with paid Extended Securityįolks who are paying for Win7 Extended Security Updates weren’t happy when this month’s. Many folks discovered that they could use a browser and just log into their account at – the problem was with the Windows-based version of Outlook. It was working just fine until… somebody changed something on Microsoft’s servers. Microsoft built some fancy new checking mechanism into the more recent versions of Windows-based Outlook. Hard to believe a crippling bug like that could roll into production without raising an alarm somewhere, but it did. There’s been a lot of internal finger-pointing inside Microsoft, but it looks like the problem stemmed from a bad fix made to Microsoft’s servers. If you run Outlook on Windows, you probably couldn’t get it to work for about four hours on July 15. Pro tip: If you aren’t sure whether you’re running a Windows DNS, you aren’t. The chicken-little cries to “Patch NOW” evaporated into stony silence as July rolled along, with one very important exception: If you’re running a Windows Domain Name Server, you need to get it patched. We also found out this month that Microsoft’s way of handling the newly-reinstituted “optional, non-security, C/D Week” patches runs all over the lot. Microsoft took nine days to fix the bug and re-ship the patch. ![]() NET Framework 4.8 patch, KB 4565636, refused to install. We had a bit of a thrill July 15 when Outlook stopped working on millions of PCs all over the world, but Microsoft fixed the bug four hours later by updating its servers.įolks who pay for Windows 7 Extended Security Updates felt rightfully miffed when the new. July tends to be a leisurely month in Windows and Office patch land, and this one’s no exception.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |