Chipp.in Tech News and Reviews

If you’ve ever cursed at your monitor as a forced reboot hijacked your workday or at the massive integration of AI features into every nook and cranny of the Windows operating system, Microsoft finally have a message for you: they get it and want to do something about it.

Last week, the tech giant announced a fundamental pivot in its Windows 11 development strategy, promising to prioritize system stability and user control over flashy, unavoidable features.

Driven by months of user feedback and mounting community frustration, Windows and devices head Pavan Davuluri outlined a course correction that switches from aggressive AI integrations and a “Microsoft knows best” attitude towards restoring lost trust by focusing on restoring customizations and putting an end to deeply disruptive updates.

The main areas that Microsoft plans to improve

Here is a bulleted summary of the key changes that Microsoft announced on its Windows blog. They can be divided into the groups “user interface & customization”, “scaling back intrusive features”, “Windows updates & reliability”, and “performance upgrades”.

Windows Updates & Reliability

• Control: Users will get more control over Windows updates, including the ability to skip updates during initial device setup, shutting down or restarting without installing updates, or pausing updates for longer periods.
• Reboots: Microsoft is shifting towards a single reboot per month scheme to avoid too many disruptions.
• Stability: Engineers will focus on reducing system-level crashes, improve driver quality, and improve connection stability of devices and connections.

Scaling back intrusive features

• AI: Microsoft is reducing Copilot entry points in apps and plans to focus on useful integrations only.
• Widgets: Quieter defaults and simpler settings to minimize distractions.
• Notifications: System notifications will be reduced.

User interface & customizations

• Taskbar: Microsoft plans to restore moving the taskbar to the top and sides of the screen. The compact taskbar is also making a comeback.
• Start Menu: The recommended section will be more relevant and get clear options to customize or turn off.
• Setup: Microsoft promises quieter and more streamlined initial setups that have fewer pages and require less reboots.

Core performance updates

• File Explorer: Microsoft plans to improve File Explorer performance significantly, enable faster copying/moving of large files, improve search, and reduce screen flicker.
• Responsiveness: Core apps, including the Start menu, move to WinUI3 to improve latency. Performance will be “more consistent”.
• Efficiency: Baseline memory footprint will be reduced.

Closing Words

Ultimate, Microsoft’s announcement reads like a long due apology, without actually apologizing. The true test will lie in the execution. Windows Insiders will be among the first to see some of the quality-of-life improvements that Microsoft promised to deliver, while everyday users may have to wait until the end of year or even longer before the changes land on their systems.

If Pavan Davuluri and his engineering team can truly deliver on a faster, cleaner, and less intrusive operating system over the coming year, Microsoft could regain some of the trust that it lost.

Microsoft confirmed a new Windows issue on March 12th, 2026 that prevents access to files on the main c: drive of the system and blocks certain applications from launching.

The issue affects certain Samsung devices that run Windows and have installed the February 2026 security updates or newer updates for Windows 11, version 24H2 or 25H2 systems.

Here are the details:

• Affected Windows versions: Windows 11, version 24H2 and 25H2
• Affected devices: Only certain Samsung devices.
• Originating update: KB5077181 (25H2 and 24H2)

Affected users may get the error message “C:\ is not accessible – Access denied” after installation of the update on affected devices. This prevents access to files on the drive and will also block some applications from launching. Microsoft mentions Outlook, Office apps, web browsers and system utilities specifically.

The problems do not require specific user actions. They occur during common actions, such as trying to access files, starting programs, or performing administrative tasks. Furthermore, users may also be blocked from elevating privileges, uninstalling, updates, or collecting logs due to permission failures.

Microsoft says that it is investigating the issue and that it suspects that the Samsung Share application is causing the issue. There is no workaround at the time of writing, but uninstalling the update — if possible — may resolve the issue. However, this leaves the system open for potential attacks, as it won’t have the February and March 2026 security issues patched anymore.

Affected users and administrators may want to keep an eye on the Windows 11 release information page. Microsoft will update the page when it has a workaround or a solution.

If February 2026 was the sprint, March is a marathon of essential infrastructure updates.

Microsoft’s third Patch Tuesday of 2026 has arrived, addressing 84 vulnerabilities in total. While the total count is typical, the release demands close attention: it contains two publicly disclosed zero-day vulnerabilities and eight critical flaws affecting a wide range of enterprise products, including SQL Server, Office, and Azure components.

Here is the breakdown of what you need to know, what to patch first, and what might break.

The March 2026 Patch Day overview

Executive Summary

• Release Date: March 10, 2026
• Total Vulnerabilities: 84
• Critical Vulnerabilities: 8
• Zero-Days (Publicly Disclosed): 2 (SQL Server, .NET)
• Key Action Item: Administrators must prioritize database and application servers due to the SQL Server elevation of privilege flaw and the .NET denial of service vulnerability. Simultaneously, ensure Office updates are deployed to workstations to prevent potential zero-click remote code execution via the Preview Pane.

Important Patches

• CVE-2026-21262 — Microsoft SQL Server Elevation of Privilege Vulnerability
• CVE-2026-26127 — .NET Denial of Service Vulnerability
• CVE-2026-21536 — Microsoft Devices Pricing Program Remote Code Execution Vulnerability
• CVE-2026-26110 — Microsoft Office Remote Code Execution Vulnerability
• CVE-2026-25187 — Windows Winlogon Elevation of Privilege Vulnerability

Cumulative Updates

Product, Version	KB Article	Notes
Windows 11, Version 24H2 / 25H2	KB5079473	Security updates and non-security changes. Adds built-in Sysmon, Emoji 16.0, and prepares infrastructure for upcoming Secure Boot certificate updates.
Windows 11, Version 26H1	KB5079466	Security updates. Improves how Windows Defender Application Control (WDAC) handles COM objects allowlisting policies.
Windows 10, Version 22H2	KB5078885	Security updates. Includes a GPU stability fix and Secure Boot updates.

Deep Dive: The Critical Vulnerabilities

Microsoft confirmed two publicly disclosed zero-day vulnerabilities are fixed this month. Furthermore, Microsoft fixed several critical remote code execution (RCE) and elevation of privilege (EoP) flaws.

Attackers may exploit the issues on systems that have not been patched to bypass protections, elevate privileges, or execute malicious payloads remotely.

Here is the critical overview:

CVE-2026-21262 (Microsoft SQL Server Elevation of Privilege)

This publicly disclosed zero-day allows an authorized attacker to elevate privileges over a network. Due to improper access control, a logged-in user can quietly elevate to become a full database administrator (sysadmin). With that level of control, they can read, modify, or delete data without user interaction.

CVE-2026-26127 (.NET Denial of Service)

The second publicly disclosed zero-day is an out-of-bounds read flaw in the .NET platform (versions 9.0 and 10.0). It allows an unauthenticated remote attacker to crash .NET applications over the network, resulting in a denial of service for any app running on the affected runtime libraries.

CVE-2026-21536 (Microsoft Devices Pricing Program Remote Code Execution)

Scoring a critical 9.8 out of 10 on the CVSS scale, this is the most severe flaw of the month. It allows remote attackers to execute arbitrary code over the network without privileges or user interaction. Notably, this flaw was discovered by an autonomous AI penetration testing agent. Microsoft notes that the vulnerability has been fully mitigated on their end, requiring no direct action from users.

CVE-2026-26110 & CVE-2026-26113 (Microsoft Office Remote Code Execution)

These type confusion and untrusted pointer dereference flaws in Microsoft Office enable remote code execution when malicious files are processed. They are particularly dangerous because they can potentially allow zero-click exploitation if a user simply views a booby-trapped document in the Outlook Preview Pane.

CVE-2026-25187 (Windows Winlogon Elevation of Privilege)

Discovered by Google Project Zero, this vulnerability leverages improper link resolution in the Winlogon process. A locally authenticated attacker with low privileges could exploit a link-following condition to effortlessly escalate to SYSTEM privileges.

Significant Changes in the March 2026 updates

• Sysmon is now built-in: Previously a manual download from Sysinternals, Sysmon is now included as a native component in Windows 11 for better security auditing and monitoring of malicious activity.
• Secure Boot certificate preparation: Windows systems are receiving infrastructure updates to prepare for the upcoming expiration of Secure Boot certificates, which will begin rotating in June 2026.
• Quick Machine Recovery (QMR) expansion: QMR is now turned on automatically on more hardware. This feature allows administrators to revert endpoints to a working state if a disastrous third-party update takes down the system.
• RSAT on Arm64: Remote Server Administration Tools are finally supported on Windows 11 Arm64 devices, allowing administrators to manage Windows Server environments directly from Arm-powered PCs.

First Steps: Your Patch Tuesday Strategy

• Prioritize the zero-days: Map your exposure and prioritize the two zero-day vulnerabilities, focusing heavily on SQL Server environments and .NET application servers.
• Update Office installations: Deploy Microsoft Office updates to all workstations immediately to mitigate the risk of zero-click remote code execution via the Preview Pane.
• Prepare for Secure Boot changes: Ensure your enterprise environment allows the new Secure Boot allowed Key Exchange Key (KEK) updates to install properly to avoid boot issues in the coming months.