Windows 11 security update scanning and repairing system vulnerabilities

Windows 11 Fixed 570 Security Flaws: What PC Users Need to Know

By Geoffrey Wenger Published July 20, 2026

Category: Tech Tips

Tags: Microsoft Security Updates System Stability Windows 11 Zero Day

Microsoft’s July 2026 security release drew attention for addressing roughly 570 vulnerabilities, a huge number that sounds alarming at first. It does not mean every Windows 11 computer carried 570 exploitable flaws. The release covered Microsoft’s wider product ecosystem and reflected faster vulnerability discovery alongside security risk. Here is what the update means, why installing it matters, and how home users and small businesses can prepare without creating unnecessary problems.

What the 570 Fixes Really Mean

Microsoft’s July 2026 Patch Tuesday release addressed about 570 vulnerabilities across its supported products. That made it one of the company’s largest monthly security releases and far bigger than the 137 vulnerabilities reported in July 2025.

At first glance, that jump looks terrible. It needs context, though.

Microsoft did not uncover 570 new flaws inside every Windows 11 computer. The total included vulnerabilities affecting Windows, Microsoft Office, SharePoint, SQL Server, Azure-related components, developer tools, server products, and other Microsoft technologies.

Even the Windows-related flaws did not apply equally to every PC. Some affected a certain feature, processor type, Windows edition, or optional service. A Hyper-V flaw, for example, may not matter on a home computer that never uses virtualization. The same is true for weaknesses tied to server roles or business-only tools.

Windows still accounted for a large part of the release. Microsoft corrected problems involving the Windows kernel, NTFS, Remote Desktop, BitLocker, Windows Media, Win32k, the Print Spooler, Active Directory services, and other key components.

For Windows 11 versions 24H2 and 25H2, the main cumulative security package is KB5101650. It moves version 24H2 to OS Build 26100.8875 and version 25H2 to Build 26200.8875.

Windows 11 version 23H2 receives its July fixes through a different update, KB5099414.

So, the useful question is not whether your computer personally contained 570 flaws. It is whether Microsoft fixed weaknesses that attackers could use against an unpatched system. In several cases, the answer is yes.

Why Patch Totals Keep Growing

Windows is not one simple program. It is a massive collection of drivers, services, networking tools, security controls, compatibility layers, user-interface features, and hardware support components.

Microsoft has to keep all of it working across thousands of possible hardware and software combinations. That includes processors, graphics cards, storage drives, printers, network adapters, business programs, accessibility tools, security products, and older applications that people still rely on.

Every supported feature adds more code. More code means more places where a hidden weakness may exist.

Security researchers are also getting better at finding those weaknesses. Modern vulnerability testing uses automated code analysis, fuzz testing, behavioral monitoring, and artificial intelligence to inspect software at a scale that human teams could never manage alone.

Microsoft has developed an AI-assisted security system called MDASH. It uses more than 100 specialized AI agents to inspect code, compare findings, test whether a possible flaw is real, and reduce false alarms.

That does not mean AI independently discovered all 570 vulnerabilities. Human researchers, Microsoft engineers, security firms, and coordinated disclosure programs still do much of the work.

AI tools can speed things up, however. They can examine obscure sections of code, compare findings from several models, and help researchers decide which suspicious results deserve a closer look.

As those tools improve, large Patch Tuesday totals may become more common. Oddly enough, that may be a sign of better detection rather than proof that Windows is suddenly becoming less secure.

The harder question is whether Microsoft can test and deliver so many fixes without causing widespread stability or compatibility problems.

How Serious Were the Flaws?

A vulnerability count tells only part of the story. It does not show how likely a flaw is to affect your computer or how difficult it would be for an attacker to use.

Some vulnerabilities require the attacker to already have local access. Others depend on the user opening a harmful attachment, visiting a compromised website, connecting to a hostile server, or installing untrusted software.

The possible damage also varies. One flaw might expose limited information. Another could let an attacker bypass a security feature, gain higher account privileges, steal credentials, damage files, or run malicious code.

Remote code execution flaws usually receive more attention because they may allow an attacker to run code on another computer. Still, the term does not always mean an attack happens with no user action. In some cases, the victim must open a specially prepared file or interact with harmful content first.

The July 2026 release included dozens of Critical-rated vulnerabilities and three publicly disclosed zero-day flaws. Two of those zero-days were reportedly being exploited before Microsoft released the fixes.

A zero-day is especially concerning when criminals are already using it against real systems. Once a patch becomes public, other attackers can compare the old and new files to see what Microsoft changed. That may help them create attacks aimed at computers that remain unpatched.

Microsoft lists vulnerability details in its Security Update Guide, where users and administrators can filter issues by product, severity, impact, and exploitability.

The release does not mean every Windows 11 computer faced hundreds of immediate attacks. It does mean that some of the corrected weaknesses posed a genuine risk, especially on systems connected to the internet and used for email, banking, customer data, or business records.

Why Update Size Can Be Misleading

The number of security fixes does not directly control the size of a Windows update.

One correction may require Microsoft to replace a very large system file. Meanwhile, dozens of smaller fixes may involve only a few code changes inside files that Windows already needs to update.

Windows 11 monthly security updates are cumulative. Each package contains the latest corrections plus earlier changes needed to bring the system to the current servicing level.

That helps computers that missed a previous update. Instead of installing every missed monthly package one at a time, Windows can use the newest cumulative update to catch up.

Microsoft also uses servicing methods that reduce unnecessary downloads by transferring certain differences between old and new files. Even so, packages in the Microsoft Update Catalog may look large because they are designed for manual installation, business deployment, or offline use.

Several things can affect installation time:

The Windows version and current build.
The speed of the processor and storage drive.
The amount of free space on the system drive.
The number of previous updates the PC missed.
The programs and services running in the background.
Whether Windows must update recovery or servicing components.

A newer PC with a fast solid-state drive may finish quickly. An older computer with limited storage or a mechanical hard drive can take much longer.

The progress bar may also sit at the same percentage for several minutes. That can be frustrating, but it does not automatically mean the update has frozen.

When Should You Install the Update?

Most supported Windows 11 users should install the July 2026 security update promptly. Several corrected vulnerabilities were already being exploited, so delaying the update for weeks adds unnecessary risk.

Promptly does not mean forcing the package onto a computer when Windows Update is holding it back.

Microsoft temporarily stopped offering KB5101650 to certain Dell computers that used affected Intel Innovation Platform Framework drivers. Those systems could experience unexpected shutdowns, reduced performance, excess heat, and rapid battery drain.

The issue did not affect every Dell computer or every PC with an Intel processor. It was tied to specific hardware and driver combinations.

Microsoft uses safeguard holds to stop updates from reaching devices with known compatibility problems. When such a hold applies, the update may not appear in Settings even though other computers can install it.

Before assuming something is wrong, check Microsoft’s Windows release health dashboard.

Do not immediately download KB5101650 from the Update Catalog simply because Windows Update is not offering it. A manual installation could bypass a safeguard that was placed on the computer for a good reason.

For systems that receive the update normally, installation is usually the right move. Save your work, make sure important files are backed up, and allow enough time for the restart.

A compatibility issue affecting a limited group of devices is not a reason for everyone else to avoid the update indefinitely.

Get Your PC Ready First

Most cumulative updates install without a major problem. Even so, a few minutes of preparation can make recovery much easier if something goes wrong.

Start by saving open documents and restarting the computer. This clears pending file operations and gives Windows Update a cleaner starting point.

Next, open Settings > System > Storage and look at the free space on the system drive. A nearly full drive can slow the computer, interfere with temporary installation files, and increase the chance of an update failure.

Back up anything you cannot easily replace. That may include family photos, financial records, schoolwork, business documents, client files, and active projects. Keep the backup on another physical drive or through a reputable cloud service.

You can also create a restore point. Microsoft provides detailed system restore point instructions, but the basic process is simple:

Search for Create a restore point from the Start menu.
Select the Windows system drive.
Choose Configure and enable System Protection if needed.
Select Create and give the restore point a clear name.

A restore point can reverse some driver, registry, application, and system changes. It is not a full backup and should not be treated as protection for personal files.

Laptop users should plug in the power adapter. Close programs you do not need, and avoid starting the update right before a work deadline, trip, online meeting, or presentation.

It is also smart to know your full Windows account password. A PIN may not work in every recovery or troubleshooting screen.

Update Planning for Small Firms

Small businesses face a tricky balance. Ignoring an important security update is risky, but installing it on every company computer at once can create a different kind of problem.

A staged rollout is usually the better choice.

Start with one or two test computers that represent the rest of the workplace. They should use the same printers, accounting tools, security software, VPN services, shared folders, and specialized equipment found on other systems.

After installing the update, check that:

The computers start, restart, and shut down normally.
Internet and local network connections still work.
Printers, scanners, and shared folders remain available.
VPN and remote access programs connect properly.
Accounting and business software opens without errors.
Performance, heat, and battery use remain normal.
BitLocker does not unexpectedly request a recovery key.

A small company usually does not need weeks of formal testing. One or two business days of normal use may be enough to uncover obvious problems.

Once the test computers appear stable, deploy the update to the remaining systems in smaller groups. Microsoft’s Windows Update for Business documentation explains the controls available to organizations that manage multiple Windows devices.

Businesses using BitLocker should confirm that recovery keys are stored somewhere staff can reach without using the locked computer. A key may be saved in a Microsoft account, Microsoft Entra ID, Active Directory, a password manager, or a protected paper record.

Testing should reduce risk, not become an excuse to postpone security updates forever.

Install the Right Windows Update

Before installing anything, check which version of Windows 11 is running on the computer.

Press Windows key + R, type winver, and select OK. The window that opens will show the Windows version and OS build.

Windows 11 versions 24H2 and 25H2 use KB5101650. To install it:

Open Settings.
Select Windows Update.
Choose Check for updates.
Allow Windows to download and install the update.
Restart the computer when prompted.

Windows 11 version 23H2 uses KB5099414 instead. After installation, version 23H2 should report OS Build 22631.7376.

Whenever possible, get security updates directly through Windows Update. Avoid third-party websites offering Windows patches, installers, or update utilities.

The Microsoft Update Catalog is a legitimate Microsoft service, but it is mainly intended for administrators, offline installations, and advanced troubleshooting. Most home users do not need it.

Do not turn off the computer while the update is being installed. The percentage display may pause for a while, especially on an older machine.

If the installation fails once, restart the PC and check Windows Update again. A single failed attempt does not always point to a serious system problem.

Check That the Update Installed

After Windows restarts, open Settings > Windows Update > Update history. Look under Quality Updates for the July 2026 cumulative update.

Windows 11 version 25H2 should report Build 26200.8875 after KB5101650 is installed. Version 24H2 should report Build 26100.8875.

You can check the build number by pressing Windows key + R, entering winver, and selecting OK.

PowerShell offers another option. Open Windows Terminal or PowerShell and enter:

Get-HotFix -Id KB5101650

The command may return details about the installed update. However, Get-HotFix does not always list every modern Windows package, so Update History and the reported OS build are more dependable.

If the update repeatedly fails to download or install, Microsoft’s Windows Update troubleshooter may help identify common problems.

Once installation is confirmed, use the computer normally. Watch for repeated crashes, missing hardware, unusual heat, rapid battery drain, printing problems, network trouble, or programs that suddenly refuse to open.

One slow restart is not necessarily a warning sign. Windows may still be finishing background servicing, search indexing, app optimization, or a security scan.

A repeated pattern matters more than one brief slowdown. Write down any error codes before trying repairs or removing the update.

How JENI® Helps With PC Upkeep

JENI® does not replace Windows Update, Microsoft security patches, antivirus software, or a proper backup. Windows security fixes must still come from Microsoft through supported update channels.

JENI® can help with the maintenance work that surrounds an update. Its Windows tools use native operating-system functions to inspect and repair system files, address certain Windows servicing problems, remove unnecessary temporary data, and create local reports.

That may be helpful when a computer has limited free space, damaged Windows components, or other maintenance issues that interfere with normal operation.

The order still matters. Back up important files, install official Microsoft updates, restart when asked, and confirm the new Windows build afterward. Maintenance software should support that process, not try to bypass it.

JENI® runs on demand and is designed without background monitoring or telemetry. It does not independently patch Microsoft vulnerabilities, and it cannot promise that every cumulative update will install without trouble.

The strongest approach is a simple combination: current backups, enough free disk space, official Windows updates, routine system care, and attention to known compatibility notices.

July 2026 Update FAQs

Did Windows 11 contain 570 flaws?

No. The total covered vulnerabilities across Microsoft’s larger product ecosystem, not 570 flaws present on every Windows 11 computer. Many applied only to certain products, features, editions, or system setups.

Does every PC need KB5101650?

No. KB5101650 applies to Windows 11 versions 24H2 and 25H2. Windows 11 version 23H2 uses KB5099414, while other Windows releases receive different packages.

Should I install it manually?

Not simply because it is missing from Windows Update. Microsoft may be withholding the update because a safeguard hold applies to your hardware, software, or drivers.

Can the update erase personal files?

A normal cumulative update is not designed to delete personal files. Important data should still be backed up because installation failures, storage problems, and hardware issues can happen without warning.

Can I remove a bad update?

Windows may allow a recent cumulative update to be removed through Update History or the recovery environment. Removal should usually be temporary because it exposes the computer to the security flaws that the update corrected.

What Larger Patch Cycles Signal

Huge Patch Tuesday totals may become more common as Microsoft and independent researchers improve their ability to find hidden vulnerabilities.

That does not remove concerns about update quality. Any change to a complex operating system can create a driver conflict, installation problem, performance issue, or unexpected compatibility failure.

Microsoft has to match faster discovery with careful testing, staged delivery, safeguard holds, and clear recovery options.

The 570 figure is not proof that Windows suddenly developed hundreds of new security holes in July. Many of those flaws had probably existed for some time. They were recently discovered, reported, classified, or prepared for coordinated repair.

Finding a hidden weakness and fixing it is better than leaving it buried in software that millions of people use every day.

Microsoft explains how cumulative releases and managed deployments work in its broader Windows update documentation.

For home users, the right response is neither panic nor permanent update avoidance. Back up important data, keep enough free disk space, respect compatibility holds, install security updates promptly, and make sure the computer works normally afterward.

Small businesses should add staged testing, application checks, and easy access to BitLocker recovery information.

The headline number is dramatic. It is not the only number that matters. What matters more is whether Microsoft can turn faster vulnerability discovery into dependable protection and whether users install that protection before attackers find the computers still waiting.