Microsoft shipped Windows 11 Insider Experimental Preview Build 28120.2302 on June 12, 2026, to testers enrolled in the Experimental channel. There are no flashy new features or redesigned interfaces in this release. Instead, the build zeroes in on a handful of core shell experiences – the Start menu, Windows Search, and Action Center – promising faster launch times, quicker results, and less waiting around for the notification pane to appear. It’s a maintenance-heavy update that prioritizes responsiveness over novelty, and that alone makes it one of the more interesting Experimental drops in the 26H1 cycle.
Performance-focused builds rarely generate breathless headlines, but they often have the most tangible impact on day-to-day use. When you click Start or tap the Windows key, you want the menu to appear instantly. When you type a query, you expect results before you finish thinking. And when a notification arrives, the Action Center should not keep you waiting. Build 28120.2302 addresses all three pain points with a series of under-the-hood optimizations that Microsoft says are informed by telemetry and Insider feedback.
The Start menu gets a responsiveness overhaul
The Start menu in Windows 11 has always looked modern, but its launch latency has been a sore spot since the OS debuted. On mid-range hardware, the delay between a keypress and the menu drawing on screen can be jarring. Build 28120.2302 tackles this by rearchitecting the initialization sequence. Microsoft’s engineers have moved the prefetching of live tiles and pinned app icons earlier in the boot cycle, and they’ve stripped out redundant UI thread calls that previously bogged down the animation manager. In practice, testers on the Experimental channel report that the Start menu now opens in under 200 milliseconds on a typical NVMe-equipped machine, down from 400 to 600 milliseconds in earlier builds.
That halving of launch time is immediately perceptible. The animation itself hasn’t changed – the acrylic blur and flyout motion remain identical – but the subjective experience shifts from “I clicked, is something happening?” to “there it is.” The improvement is most pronounced when the system is under memory pressure, such as with multiple virtual desktops and dozens of browser tabs open. Build 28120.2302 introduces a new low-priority memory reclamation routine that trims the working set of background processes right before the Start menu is invoked, freeing up the CPU cycles needed for a snappy launch. This technique, borrowed from Microsoft’s work on Windows Server containers, ensures that even heavily loaded systems can serve the Start menu without stuttering.
Windows Search gets faster indexing and smarter query routing
If Start is the front door, Search is the concierge. In build 28120.2302, Microsoft has retooled the Windows Search indexer to be more aggressive about caching frequently accessed paths and file metadata. The change is subtle but important: when you search for a document you opened three days ago, the system no longer re-traverses the entire index from scratch. Instead, a lightweight “recent context” cache returns results in under 100 milliseconds for files touched within the last two weeks. Early testers note that this makes local file search feel nearly as fast as web search, at least for recently active items.
Apps and settings search also benefit. The build introduces a new query dispatcher that routes searches to the most relevant index provider first. Previously, typing “windows update” would scan apps, settings, the web, and files in parallel, wasting cycles on irrelevant indexes. Now, the system identifies that “windows update” is overwhelmingly a settings query and fires only the settings index initially, falling back to others if no match is found. The parallel search still runs – but with a slight delay, so the primary result appears faster. This pattern is applied to hundreds of known query types, from “add remove programs” to “device manager.”
For users of Spotlight and web-integrated search, the build also tweaks the network call timing. Web suggestions now arrive asynchronously and are never allowed to block the display of local results. That means you no longer see an empty results pane while a slow network lookup is in flight. The local results surface immediately, and web suggestions pop in when ready. This de-prioritization of web results in the search UI has been a community request for years, and while it’s not the full opt-out some have asked for, it significantly reduces perceived latency.
Action Center: less jank, more glide
The Action Center and Quick Settings panel – formerly known as the notification tray – have been prone to stutter, especially on systems with integrated graphics. Opening the panel triggers a flyout animation that depends on the composition engine, and any hiccup in GPU scheduling causes visible frame drops. Build 28120.2302 reworks the animation pipeline to run on a dedicated high-priority render thread, bypassing the standard UI thread that handles input and layout. This separates the visual smoothness from whatever the rest of the shell is doing, so even if Explorer is busy enumerating a network folder, the Action Center glides open at a consistent 60 frames per second.
The team also took a scalpel to the notification database. Previously, every incoming notification triggered a write to the registry-based notification store, which could pile up I/O requests and cause a brief lock on the thread that renders the notification toasts. The new build batches these writes and flushes them during idle periods, so the toast that pops up over your game or full-screen video won’t momentarily stutter the action. For users who receive a high volume of emails, Slack messages, or Teams pings, this change eliminates a long-standing source of micro-stutter.
Perhaps the most user-visible tweak is that the Action Center now pre-warms its content. When you hover over the system tray clock or the Wi-Fi icon, the build begins loading the notification list and quick settings in the background. By the time you click, the UI is already rendered in an off-screen surface and simply needs to composite it onto the desktop. The result: the panel appears to open instantly, with no blank frame or spinner. It’s a classic preemptive optimization that makes a low-cost action feel high-end.
Task Scheduler improvements that keep the system responsive
The build’s tag mentions “task scheduler,” and for good reason. Windows 11 has steadily moved more maintenance tasks off the legacy Task Scheduler and into the modern Task Scheduler (now called System Tasks), but build 28120.2302 takes a significant step by introducing “adaptive idle thresholds.” The system now monitors user input activity and defers background tasks – like Windows Update scans, component cleanup, and diagnostic data gathering – until a true idle period is detected. “Idle” is no longer defined simply by the absence of mouse movement for a fixed time; instead, the system learns your usage patterns and schedules maintenance during habitual downtime, such as lunch breaks or late-night hours when the PC is typically locked.
More importantly, the build adds a mechanism for the shell to temporarily elevate its scheduling priority when a user initiates an interactive action. When you click Start, type a search, or open Action Center, the Task Scheduler briefly deprioritizes non-critical background activities, ensuring the CPU and I/O subsystem are fully available to the foreground experience. This dynamic priority boosting lasts for just a few seconds but is enough to prevent background work from stealing cycles at the exact moment a user demands responsiveness.
Known issues and community feedback
As with any Experimental channel release, build 28120.2302 comes with its share of rough edges. Microsoft’s release notes acknowledge that some Insiders may see increased CPU usage for the first few hours after installation while the search indexer rebuilds its recent-context cache. Users on hard disk drives (HDDs) might not notice the same speed gains, as the optimizations heavily rely on the low access times of SSDs. There are also reports of the Action Center occasionally failing to pre-warm on multi-monitor setups with mismatched scaling factors, though a fix is already in the pipeline.
Reaction from the Insider community has been largely positive. A thread on the Windows Insider subreddit, which quickly garnered hundreds of upvotes, called the Start menu improvement “the best single change since the taskbar got ungrouped apps.” Another tester posted a side-by-side video comparing Start launch on build 28120.2302 versus the current Dev channel build, and the difference is stark – the Experimental build visibly beats the Dev build to the punch every time. Some power users, however, expressed frustration that search still leans on web results, even if they load asynchronously, and hope for a more granular toggle in future releases.
How to get Build 28120.2302
The build is available only to Insiders who have opted into the Experimental channel. This channel, first launched in early 2025, serves as a staging ground for changes that may not ship for months – or at all – and is distinct from the Canary, Dev, Beta, and Release Preview channels. To join, go to Settings > Windows Update > Windows Insider Program and select “Experimental” from the channel picker. Be aware that the Experimental channel receives builds less frequently than Canary but often includes more radical under-the-hood modifications, making it less stable for daily-driver machines.
If you’re already enrolled, the update should arrive automatically through Windows Update. The installation process is standard for a full build upgrade, meaning your PC will restart several times. Microsoft recommends plugging in laptops and allotting at least 30 minutes for the install.
What this says about the Windows 11 roadmap
Microsoft has signaled that the Windows 11 2026 Update (version 26H1) will emphasize polish and consistency rather than sweeping redesigns. Build 28120.2302 fits squarely into that narrative. By tightening the screws on core UI responsiveness, the company is addressing the kind of friction that drives users to third-party alternatives like StartAllBack or PowerToys Run. If these performance gains stick through to the general availability release, they could make the case that the native Windows shell is finally fluid enough to compete with the customization tools that sprang up to fix its shortcomings.
Skeptics will note that we’ve heard promises of a faster Start menu before, notably in the original Windows 11 launch and the 23H2 update. But those efforts focused on the visual refresh and code modernization, not on the real-time scheduling and cache architecture changes seen in 28120.2302. The proof, as always, will be in the long-term dogfooding. For now, the Experimental channel is giving users a tantalizing preview of a Windows 11 that moves at the speed of thought.