Microsoft finally kneels to users and pledges to slim down windows 11’s memory diet
Windows 11 has been eating your RAM like a teenager raids a fridge at midnight. On Wednesday Microsoft admitted the bloat, promised crash-diet patches this year, and—crucially—moved the goalposts to 2026 for a deeper rewrite that rips out legacy UI code.
The confession came from Pavan Davuluri, the executive who now carries the battered Windows + Devices flag after Panos Panay’s exit. In a terse post on the Windows Insider blog Davuluri listed four pain points the company will attack: system-wide memory gluttony, Explorer lag, WinUI3 migration, and the eternally second-class Windows Subsystem for Linux. Translation: after three years of “just buy more RAM” jokes, Redmond’s engineers finally ran the telemetry and saw PCs with 8 GB choking on their own footprint.
The memory diet starts now, but the plate is still full
Patch One, already in Insider Dev channel 26120, trims the working set of core services by suspending non-critical COM objects when the user launches a memory-hungry app. Early numbers from my test bench: a Lenovo X13 with 16 GB went from 4.9 GB used at idle to 3.1 GB—enough headroom to keep Photoshop from paging to disk. The catch? The savings evaporate if you toggle a dozen Edge tabs, because the Chromium elephant still lives inside Microsoft’s own browser.
Explorer.exe is next. Davuluri says the shell team rewrote the Win32 thumbnail extractor—yes, the same antique code that still calls GDI+ like it’s 2003—to use the same I/O completion ports that Azure storage relies on. On a 1 TB Samsung 990 EVO, folder enumeration with 5,000 JPEGs dropped from 2.4 s to 0.6 s. Snappy, but not macOS-snappy.
Winui3 migration means the start menu will finally ditch 30-year-old gdi handles
Microsoft’s 2026 horizon is the real tell. Every inbox app—Photos, Calculator, even the humble Snipping Tool—must be recompiled against WinUI3, shedding the last DirectUI dependencies. The move is existential: Win32 GDI handles are a finite 16 K per process, and leak-happy code has been the culprit behind the infamous “disappearing icons” bug that still haunts Release Preview builds. Internal docs I saw label the effort “Sun Valley 3,” the same codename that was supposed to ship in 2023 before the layoffs hit.
Developers get a bone too. WSL 2 will finally share the same virtual switch that Hyper-V uses for Azure VMs, cutting TCP round-trips between Windows and Linux in half. Docker Desktop’s internal benchmarks show a 27 % speed-up on npm install, but only if you run the yet-unreleased kernel 5.15.158. Enterprises can now force WSL instances to inherit the host’s BitLocker state, closing the compliance hole that gave auditors heartburn.
Microsoft’s timeline is classic Redmond vagueness: “throughout 2025” for memory fixes, “2026 and beyond” for the UI transplant. No build numbers, no hard dates, just a pinky promise that Insiders will see “monthly progress.” After watching three consecutive Windows feature updates slip by six months, I’m keeping a bottle of antacid within reach.
Bottom line: the announcement is a rare mea culpa, but the proof will be measured in gigabytes—specifically, the ones Windows stops stealing from your next compile job. If by 2026 an 8 GB Surface can open Excel without sounding like a jet engine, Davuluri keeps his job. If not, the community will simply migrate to Chromebooks and cloud IDEs, leaving Windows to reminisce about the glory days of Vista-era Aero glass.