- March 2020 Security Updates release notes
- List of software updates for Microsoft products
- List of the latest Windows Updates and Services Packs
- Security Updates Guide
- Microsoft Update Catalog site
- Our in-depth Windows update guide
- How to install optional updates on Windows 10
- Windows 10 Update History
- Windows 8.1 Update History
- Windows 7 Update History
After 5 years I think if Microsoft does not have a handle on keeping these updates reasonably free of issues that it probably never will. I’ve mostly been OK with these updates but I have not installed them as soon as they are released. I certainly do not install any update that is not required. If your going to Windows update and begging for updates and install anything listed. Your volunteering for a headache and problems. You have agreed to be a beta tester for Microsoft.
I install security updates right away, as I don’t want to volunteer to be exploited by malware.
In over 30 years with Microsoft I have never had an issue with my updates.
Also, if you study the actual numbers involved with OS updates and related issues, Microsoft is not alone in these complex tasks.
I always install updates and in 10 years of doing kind of work I have only seen two times where the udpates have actually caused an issue. I have installed thousands of updates on tens of thousands of servers and workstations updates rarely cause issues.
7 critical vulnerabilities, and I just uupdated last month. ‘ Time speeds up when…
Thanks, Martin, For this ferry helpfull body of work you deliver every mounth!
Thanks martin. Already update security-only using bypass version-four and it works.
The current Servicing Stack Update (SSU) information at
https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV990001
shows what SSU Windows Update should automatically pick up if run today. A home user can confirm this by running Belarc Advisor.
>Windows 10 version 1809: 73 vulnerabilities: 7 critical and 66 important
Since last month? o.O
I didn’t see any comment. Just test if I can see this comment. Need to make sure, is it my browser or is it no comment at all.
At first it’s hidden. After I post the comment I can see all the comment. it’s weird.
If running Windows 7 SSU released in January 2020 (which allows ESU updates to install with BypassESU v4), the new March 2020 Security Only Update and Security Monthly Quality Rollup packages will request a newer SSU (these newer SSUs will render the BypassESU useless). Wait for a new BypassESU version that can workaround this.
I can confirm the “Lite” method to keep receiving Windows 7 updates, found in MDL forums, also works with all March 2020 updates. MUUUUAAAHHHHAAAHHHHHHAAAAAA!
I’m currently downloading this update on 1909. I wonder what is going to happen given the recent issues that came up from the previous optional update. I didn’t try to remove it since I didn’t notice anything suspicious. Will this update override the previous one? Will it fix the problems?
Also, I stay firm on my belief that MS should focus on only fixing things for one month at least, and then improve and introduce new features. Having constantly new features is a bug-fixing nightmare.
That’s why Windows 7 eventually became the best OS ever built. Because they weren’t introducing new features, just fixing bugs and improving the existing ones for long time.
@Deo et Patriae
Windows 8.1 + Classic Shell was and is better than Windows 7 in every aspect imaginable. Metro was the only weakness of Windows 8.1, but it can be turned off, if you know how.
Problem is some hardware doesn’t have support (i.e. drivers, in particular) for Windows 8/8.1.
There are even worse cases: Ryzen motherboards that work only with Windows 7 or 10. I know you will probably say, what? Then, I invite you to Google MSI B450 based motherboards and see their OS support specs.
Yes that was very nefarious of the CPU/GPU/MB makers and MS and that skipping over 8/8.1 for driver support to force more folks onto that 10/Rolling Release madness that’s rolling over its end users on a monthly basis.
But I’ve got a new laptop running 1809 Home and maybe I’ll be forced to install 1909 before 2004 comes in April, if 2004 is going to be forced on me before 1809 goes EOL. But I’m really waiting for the Linux 5.6 Kernel to become available for Linux Mint and better support for my laptop’s Ryzen 3000 series APU’s power management.
I’m keeping the 1809 laptop offline as a March 2019 patch delay option and will keep that laptop offline for another week or so just in case for patch vetting reasons. But really I’ve got 4 other laptops running Linux Mint 19.3 and 7(EOL) dual boot and maybe I’ll mothball the new laptop until Kernel 5.6 is offered for Mint 19.3/later. With all the other things going on I’ve got plenty of time and available laptops that boot into Mint to do most of what I need currently. And 7’s kept around on those laptops for offline only legacy Windows usage.
I’m not going to be a forced BETA tester for the folks in Redmond and It’s only a matter of time before my newest laptop gets Mint/Kernel 5.6 installed alongside 1809/1909, and Kept offline like 7/EOL as well. The Ryzen 3000 series APUs have been on the market since Q1 2019 so a little more time for that support to be fully included mostly by Kernel 5.6 and most issues resolved for getting that laptop running under Mint 19.3/later so I can avoid most of these 10 issues forced upon the 10/Home end users. The old Windows 7 laptops sure are a bit more responsive and boot faster under Mint 19.3 and that’s not so bad for my complete control over my own laptops’ update management unlike 10’s forced madness.
Windows 8.1 here. Message on screen during reboot of KB4541505, “We couldn’t complete the update. Undoing changes”. Anyone else see that?
Prior to that installation attempt KB4540725 which is the SSU for this month installed without a problem.
Well, I fixed it. Error code according to the Reliability Monitor was 0x800F0921. Couldn’t find anything relevant with that code on the web so ran DISM.exe with the Restorehealth flag, downloaded and ran the installer again and lo and behold KB4541505 installed without a hitch. :)
Martin:
Version 1909 & 1909 users got a quick out-of-band security update on TH March 12 – KB4551762
https://support.microsoft.com/help/4551762/
https://www.askwoody.com/2020/heads-up-microsoft-posts-a-fix-for-that-smbv3-security-hole-get-ready-to-install-this-months-windows-patches/
DOH! I meant “1903 & 1909 users”
Per https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2020-0796 I successfully installed KB4551762 using Windows Update, bringing me to Microsoft Windows [Version 10.0.18363.720].
Server KB4494175 and KB4540670 – The error is on server “An existing connection was forcibly closed by the remote host” which we believe is SSL related error. Eventually the job would run correctly but would fail initially and this was causing all kinds of issues. The host server is a MS SQL server which is where we uninstalled the updates. Once we removed the two patches above it seemed to have fixed the issue. I think I got this right I do the security not the IT stuff.
Has anyone seen any issues with the two KB’s above?
Hi Michael,
do you have any update on this issue? We’re having the exact same issue.
Thank you in advance.
Can someone help me clarify this please? Per ” https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirements-for-windows “, are we safe to deploy all updates from March released and also from ” https://portal.msrc.microsoft.com/en-us/security-guidance/advisory/ADV190023 “? There is not binding policy made ready yet by our Active Directory Group Policy team yet at this moment.
I have currently updated my Windows 10 Home to OS Build 18363.753 without any problems at all.