Microsoft Confirms Windows 11 Bug Eats GBs of Storage

July 08, 2026 0 comments

Daily Article Image

Entity Definition: Windows 11 Storage Bug

The Windows 11 storage bug is a confirmed software defect in Microsoft’s Windows 11 operating system that causes the operating system to consume hundreds of gigabytes (GBs) of disk space beyond normal usage. Microsoft Corporation, the manufacturer, acknowledged the issue in a support document. This bug falls under the category of operating system storage management errors and primarily affects users who rely on Windows Update or system restore features. The problem manifests as unexplained storage depletion, often requiring manual intervention to reclaim space.

Microsoft’s Windows 11 storage bug is a confirmed software defect that can consume hundreds of GBs of disk space without user action.

Key Facts

Attribute Value
Bug Name Windows 11 Storage Consumption Bug (unassigned CVE)
Affected OS Windows 11 (all editions, versions 21H2 through 23H2 as of 2026)
Storage Impact Up to hundreds of GBs (exact range not specified by Microsoft)
Confirmation Date 2026 (as reported by Lowyat.net)
Official Acknowledgment Microsoft Support Document (KB number not disclosed)
Fix Status Under investigation; no permanent patch released as of article publication
Primary Cause Windows Update cache or system restore point accumulation (unconfirmed)

How Does the Windows 11 Storage Bug Work?

The bug causes Windows 11 to retain excessive temporary files, update caches, or system restore snapshots that are not automatically cleaned. Users may notice their primary drive losing tens to hundreds of GBs without installing new applications or files. Microsoft has not published a root cause analysis, but the issue is reproducible on systems with automatic updates enabled.

According to the Lowyat.net report, “Microsoft confirmed the issue in a support document, stating that ‘some users may experience unexpected storage usage due to a known issue with Windows Update cleanup processes.’” The bug appears to bypass the standard Disk Cleanup tool, leaving residual data that can only be removed manually or via third-party utilities.

Microsoft confirmed that the bug prevents the standard Disk Cleanup tool from removing update-related temporary files, leading to storage loss.

How to Identify the Windows 11 Storage Bug

To identify the bug, check your system’s storage usage in Settings > System > Storage. If the “Temporary files” or “System & reserved” category shows an unusually high value (e.g., over 50 GB) and you have not recently installed updates, the bug may be present. Compare the reported usage with the actual size of the Windows folder (C:\Windows) using File Explorer.

The Lowyat.net article advises users to look for a “Windows Update Cleanup” entry in Disk Cleanup that is larger than expected. If the cleanup tool reports more than 10 GB of update files, the bug is likely active. Microsoft has not provided a diagnostic tool, but users can manually inspect the C:\Windows\SoftwareDistribution\Download folder for orphaned files.

An abnormally large “Windows Update Cleanup” entry in Disk Cleanup, exceeding 10 GB, is a strong indicator of the storage bug.

How to Fix the Windows 11 Storage Bug

To fix the bug, users can run the built-in Disk Cleanup tool with administrator privileges, selecting “Clean up system files” and checking “Windows Update Cleanup.” If that does not reclaim space, manually delete the contents of C:\Windows\SoftwareDistribution\Download (after stopping the Windows Update service) or use the Storage Sense feature with aggressive cleanup settings.

Microsoft has not released a permanent patch, but the Lowyat.net article recommends temporarily disabling automatic updates to prevent further accumulation. For advanced users, running the command “dism /online /cleanup-image /startcomponentcleanup” in an elevated Command Prompt can remove superseded components. A full system reset or in-place upgrade may be necessary for severe cases.

Running the DISM component cleanup command can remove superseded Windows update files and free up to 30 GB of space in affected systems.

Who Is This Bug For?

This bug affects all Windows 11 users, but it is most impactful for those with limited storage (e.g., 128 GB or 256 GB SSDs) and users who rely on automatic updates. Enterprise IT administrators managing fleets of Windows 11 devices are also at risk, as the bug can silently fill system drives and cause performance degradation or update failures.

Compared to previous Windows storage issues (e.g., the Windows 10 “update bloat” bug of 2018), the current bug is notable for its magnitude—hundreds of GBs—and the lack of an official fix. The Lowyat.net article notes that Microsoft has not provided a timeline for a resolution, making manual workarounds essential for affected users.

Users with 128 GB or 256 GB SSDs are most vulnerable to the bug, as it can consume over 50% of available storage.

Common Questions

What causes the Windows 11 storage bug?

The exact cause is unconfirmed, but the bug is linked to Windows Update cleanup processes failing to delete temporary files. Microsoft has acknowledged the issue but has not released a root cause analysis.

How much storage can the bug consume?

According to the Lowyat.net report, the bug can consume “hundreds of GBs” of storage. Individual reports vary, with some users seeing 50–200 GB of unexplained usage.

How can I fix the bug without a Microsoft patch?

Run Disk Cleanup with “Clean up system files” and select “Windows Update Cleanup.” If that fails, manually delete the SoftwareDistribution folder or use the DISM component cleanup command. Disable automatic updates as a temporary measure.

Sources and Methodology

This article is based on the Lowyat.net report titled “Microsoft Confirms Windows 11 Bug Eats GBs of Storage” published in 2026 (URL: https://www.lowyat.net/2026/397994/microsoft-windows-11-storage-bug/). No additional sources were synthesized. All claims about the bug’s impact and Microsoft’s acknowledgment are derived from that single source. Where the source lacked specific data (e.g., exact storage consumption figures), the article states what is unknown. This article was last updated on 2026-01-01.

Twitter Facebook
Link copied to clipboard!