LandzDown Forum

Security => Security Alerts & Briefings => Topic started by: Corrine on August 12, 2025, 06:13:38 PM

Title: Microsoft August 2025 Security Updates
Post by: Corrine on August 12, 2025, 06:13:38 PM
The Microsoft August 2025 security updates have been released and consist of 107 new CVEs to Microsoft products.

Of the Microsoft CVEs released, 12 are rated Critical, 1 is rated Moderate, 1 is rated Low, and the rest are rated Important in severity. At the time of release, one is listed as being publicly known and none are listed as under active attack.

The security updates apply to the following products, features and roles: Windows and Windows Components, Office and Office Components, Microsoft Edge (Chromium-based), Azure, GitHub Copilot, Dynamics 365, SQL Server, and Hyper-V Serve.

Information regarding known issues with KBs included in the security updates can be found at the bottom of the page at August 2025 Security Updates - Release Notes - Security Update Guide - Microsoft (https://msrc.microsoft.com/update-guide/releaseNote/2025-Aug).

Recommended Reading: See Dustin Childs review and analysis in Zero Day Initiative -- The August 2025 Security Update Review (https://www.zerodayinitiative.com/blog/2025/8/12/the-august-2025-security-update-review).
Title: Re: Microsoft August 2025 Security Updates
Post by: Corrine on August 24, 2025, 06:33:59 PM
Reports say Windows 11 update is bricking drives — is yours on the list? (https://www.msn.com/en-us/technology/hardware-and-devices/reports-say-windows-11-update-is-bricking-drives-is-yours-on-the-list/ar-AA1L7xjL?ocid=BingNewsSerp)

QuoteMicrosoft released Windows 11 version 24H2 security update KB5063878 on August 12, 2025. It notably fixed delays signing into new Windows 11 devices, caused by "certain preinstalled packages," but it also arrived with a couple of issues.

Some users reported an installation error with code Ox80240069, which Microsoft says was caused by attempts to deploy the update through Windows Server Update Services (WSUS). This issue was patched and should no longer be a problem.

However, that doesn't seem to be the only issue with the KB5063878 update. A follow-up report from X user @Necoru_cat (aka Nekorusukii) demonstrates something a lot more serious than an installation error.

See the referenced article for additional information.