Windows 11 idles at 6GB of RAM on 8GB laptops — Microsoft just admitted it

Buy an 8GB laptop with Windows 11 and boot it up. Before you open a single application, the operating system has claimed roughly 6 gigabytes of your total memory. A browser, a messaging app, and a PDF will push you past the boundary where Windows starts swapping memory to disk — and performance falls off a cliff. Microsoft, which set the 8GB minimum recommendation for Windows 11, acknowledged this week that the idle memory footprint is too high.

The primary culprit is WebView2, a Chromium-based web rendering engine that Microsoft ships with Windows 11 and loads at startup. It powers components including the Start menu, Widgets, and parts of Settings — features that could run on far leaner native code but were built on a browser engine for development convenience. Embedding a full web engine into core OS components adds hundreds of megabytes of overhead that appears before the user launches anything.

Pavan Davuluri, Microsoft’s Vice President of Windows and Devices, confirmed the problem publicly and framed memory optimization for 8GB systems as a priority through the end of 2026. The company has already migrated the File Explorer Properties dialog from WebView2 back to native WinUI — a demonstrable reduction in overhead, if a modest one. More components are on the same migration path, though Microsoft has not published a list or committed to specific dates.

The timing of Microsoft’s admission is not coincidental. Consumer RAM prices have risen sharply in 2026 as AI data centers compete for the same DRAM supply, making the upgrade from 8GB to 16GB significantly more expensive than it was a year ago. An 8GB laptop that costs $600 is a different class of purchase from a $900 device with 16GB — a gap that matters in every price-sensitive market where Windows has volume. Selling an operating system that consumes most of its own minimum RAM at idle is a problem Microsoft can no longer defer.

Whether the roadmap will produce measurable results by December is a legitimate question. Microsoft gave no specific performance target — no commitment to, say, idle memory below 3GB by year-end, no timeline for which components would ship native rewrites, and no external verification mechanism. The File Explorer Properties migration is a one-data-point demonstration of intent. Users with 8GB machines now have an acknowledgment, a direction, and a timeframe. They do not yet have a number.

The idle memory problem is not new. Reviewers documented it consistently after Windows 11 launched in 2021, and users on budget hardware have filed feedback for years. What changed is that Microsoft named it publicly, in the context of a global memory shortage that makes ‘buy more RAM’ a more expensive answer than it was before. Apple, whose macOS idles below 3GB on the same 8GB base configuration, has made memory efficiency a visible product advantage — and Microsoft appears to be responding to the comparison.

The File Explorer fix is already shipping. The broader roadmap is not. Microsoft has committed to a direction rather than a destination, a meaningful distinction for anyone buying a standard Windows laptop in the months ahead.

Tags: microsoft, RAM, memory optimization, Pavan Davuluri, WebView2, Windows 11