Image credit: Microsoft
Break down the key findings, root causes, and practical steps based on the latest reports, while suggesting some workarounds.
Key Test Results
Testing by Windows Latest (and echoed in other outlets) used a virtual machine on the Dev/Beta channel build to compare preloading on vs. off. Here’s a quick summary:
| Metric | Without Preloading | With Preloading | Notes |
|---|---|---|---|
| Idle RAM Usage | ~32-35 MB | ~67 MB | Extra ~35 MB reserved for background instance; negligible on high-RAM systems but adds up on low-spec devices. |
| Launch Time (Idle PC) | ~1-2 seconds | ~0.5-1 second | Faster first open, but difference is only visible in slow-motion (0.25x speed) videos. |
| Launch Time (Under Load) | ~2-3 seconds | ~1-2 seconds | Marginal improvement; still feels “sluggish” compared to Windows 10. |
| Folder Navigation/Context Menu | Slow (1-2s delay) | Unchanged | Preloading doesn’t touch core UI bottlenecks. |
These numbers come from repeatable Task Manager snapshots and video benchmarks. On a 2GB RAM Windows 10 setup (for comparison), File Explorer launches noticeably quicker without any preload—highlighting how Windows 11’s modern UI layers exacerbate the issue.
Why This Happens: The WinUI/XAML Overload

Windows 11’s File Explorer isn’t just a refresh of Windows 10’s Win32-based version. It wraps the legacy core in heavier WinUI 3 and XAML elements for rounded corners, transparency, and Mica effects. This adds rendering overhead:
- Cold Starts Are the Pain Point: Opening Explorer from scratch loads these UI components on-demand, causing hitches.
- Preloading’s Band-Aid: It warms up a hidden instance at boot (via the “explorer.exe” process), but doesn’t optimize the underlying I/O, CPU-bound tasks, or third-party shell extensions (e.g., antivirus context menu handlers).
- No Silver Bullet: As the article notes, actions like right-click menus or folder switching remain laggy because they trigger fresh computations each time.
Microsoft has called this a “pragmatic” step while they “explore” deeper fixes, with the feature set to default on in early 2026 updates. It’s opt-in for now in previews, but expect it to ship broadly unless feedback sways them.
User Reactions and Broader Context
On forums like Reddit’s r/Windows11, the sentiment mirrors the article: frustration with the “RAM tax” for minimal gains, plus calls for Microsoft to revisit the UI stack. Some users praise alternatives like FreeCommander or Total Commander for snappier performance without bloat. Interestingly, a simple F11 (full-screen toggle) hack can sometimes jolt Explorer into faster folder browsing by refreshing the view.
If you’re on an Insider build, you can toggle this easily:
- Open File Explorer.
- Go to View > Options > View tab.
- Uncheck “Enable window preloading for faster launch times”.
- Restart to apply.
For perceived speed boosts without preloading:
- Disable Animations: Settings > System > About > Advanced system settings > Performance Settings > Adjust for best performance (or uncheck “Animate controls and elements inside windows”).
- Turn Off Transparency: Settings > Personalization > Colors > Transparency effects (off).
- Audit Extensions: Use tools like ShellExView (free from NirSoft) to disable non-Microsoft context menu items—they’re often the real culprits.
- Upgrade Hardware?: If on HDD or <8GB RAM, switching to SSD helps more than any software tweak.
This feels like another symptom of Windows 11’s “modernization” push prioritizing aesthetics over efficiency—echoing complaints about the Settings app or Widgets. Microsoft seems aware (they’ve acknowledged Explorer slowness publicly), so watch for 25H2 or later updates. If you’re hitting these issues daily, third-party explorers might be worth a spin until then. What setup are you on—Insider build, or stable? I’d love to hear if tweaks like these help!
Source: Windows Latest