Microsoft’s optional preview update KB5095093, dropped on June 23, 2026, finally extinguishes an infuriating Windows 11 bug that dragged shutdowns into agonizing minutes-long waits. The fix hones in on the Background Intelligent Transfer Service (BITS)—the engine behind background downloads like Windows Update—which was stubbornly refusing to stop in a timely manner, chaining the entire shutdown sequence to its sluggish pace. Available now for Windows 11 versions 24H2 and 25H2, this cumulative update is a beacon for anyone who has ever stared at a “Shutting down” spinner and wondered if their PC had frozen for good.

Microsoft’s release notes pull no punches: “This update improves the time required for the Background Intelligent Transfer Service (BITS) to stop.” That terse line opens a window into a problem that has quietly plagued Windows 11 since its early days. BITS is supposed to save its state and gracefully exit when the system goes down for a restart or shutdown. But as many users discovered, that “graceful” exit could become an exercise in patience-testing endurance, particularly after a busy Windows Update session or while large downloads were in progress.

A Familiar, Fury-Inducing Delay

Ask any Windows 11 power user what frustrates them most, and slow shutdowns will crack the top ten every time. A shutdown that should take seconds balloons into a full minute or longer. The screen in front of you becomes a passive-aggressive hangout: “Shutting down…” with that little circle spinning, no end in sight. For those on laptops, battery drains unnecessarily. For desktop users, it’s a waste of time that chips away at productivity.

The culprit? Often, it’s a background service that can’t wrap up its affairs. Windows signals all running services to stop, and if one service doesn’t respond within a set timeout, the system kills it. But BITS, tasked with downloading updates, store apps, and other content in the background, was built to be resilient. Abrupt termination risks corrupted transfers or leftover file fragments. So Windows gave BITS a generous window to finish its business, but that window turned into a drag when BITS got stuck in a loop—say, waiting for a network resource that had no intention of responding, or crunching through a large job queue.

Microsoft’s changelog doesn’t detail the technical nitty-gritty, but the fix almost certainly involves teaching BITS to more aggressively checkpoint its in-progress jobs and to release resources faster when a shutdown command arrives. This might mean forcing a quicker resolution of outstanding network connections or reducing the default wait time for individual transfers to fail softly before the service shuts down. Whatever the coding magic, the result is a shutdown that no longer hangs on the lethargy of background download management.

Under the Hood: What BITS Does and Why It Matters

To understand why this fix is a big deal, you need to understand BITS. The Background Intelligent Transfer Service is a Microsoft-designed mechanism for asynchronous, prioritized, and throttled file transfers in the background. It’s what lets Windows Update download gigabytes of patches without choking your workday—it hums along in the background, using idle network bandwidth. When you download from Microsoft Store or stream Windows update files, BITS is often the invisible courier.

During a shutdown, the Service Control Manager sends every service a stop signal. BITS, as a well-behaved service, attempts to save the state of all active transfers so they can resume the next time the system starts. If it takes too long—say, because a transfer is stuck on a non-responsive endpoint—Windows will eventually time out and force-stop it. But that timeout could be up to several minutes, depending on registry settings and system configuration. In many cases, the forced stop leaves behind orphaned temporary files that chew up disk space or cause update failures down the line.

The new improvement likely adjusts the service’s internal stop logic to more quickly recognize hopeless transfers and cancel them, or to batch the state-saving process so it completes in a fraction of the time. This not only speeds up the visible shutdown but also reduces the risk of file corruption from abrupt service termination.

The Update Rollout: How to Get KB5095093

KB5095093 is an optional, non-security preview update—what Microsoft calls a “C” release, typically rolled out in the third or fourth week of a month. It’s intended for seekers: users and IT admins who want to test upcoming fixes before they become mandatory in the next Patch Tuesday. The update will be bundled into the July 2026 cumulative update, which arrives on July 14, 2026, for all users. So if you prefer to wait for the fully baked version, you’ll get it automatically then.

If you’re eager to kick those shutdown delays to the curb now, open Settings > Windows Update, then select “Check for updates.” Under the “Optional updates available” section, look for “2026-06 Cumulative Update Preview for Windows 11 Version 24H2 (or 25H2) for x64-based Systems (KB5095093)” and click Download & install. Alternatively, you can grab the standalone package from the Microsoft Update Catalog, which is handy for deploying across multiple machines.

The update applies to both Home and Pro editions, and it requires about 500 MB of free space. A restart is, of course, mandatory—and hopefully a noticeably faster one.

Version Coverage: 24H2 and 25H2 Only

KB5095093 targets only the two most recent feature updates: Windows 11 24H2 (the broad release from late 2024 that introduced Wi-Fi 7 support, Sudo for Windows, and other features) and 25H2 (the 2025 feature update currently in active servicing). If you’re still on 23H2 or older, this specific fix is not included because those versions are on a different servicing branch. However, users on older versions often report similar shutdown issues when BITS misbehaves; if Microsoft validates this fix with positive feedback, it could be backported to older supported versions in a future update. For now, only the cutting edge gets relief.

It’s worth noting that 25H2 is still in its early lifecycle and has a small but growing user base. This update’s coverage signals Microsoft’s commitment to keeping 25H2 in lockstep with 24H2 for stability fixes, even though 25H2 itself is not yet a mandatory update for most users.

Community Reaction and Early Reports

Since the optional update’s release, early adopters on platforms like Reddit’s r/Windows11 and Microsoft’s own Feedback Hub have been cautiously optimistic. One user reported that a shutdown that previously took 1 minute 42 seconds now completes in 8 seconds. Another admin testing on a fleet of 50 machines noted a dramatic drop in helpdesk tickets about “stuck on shutdown” issues. These are anecdotal, but they align with the targeted nature of the fix.

Some users, however, caution that the update doesn’t magically solve all shutdown woes. If another service—say, a third-party antivirus or a misbehaving driver—is holding things up, the system will still pause until that service responds or times out. The BITS fix only addresses the BITS bottleneck. But given how frequently BITS was the culprit, this update could quietly improve the shutdown experience for millions.

Known Issues and Caveats

Preview updates are not without risk. They are released with the “try it at your own pace” caveat. Microsoft has acknowledged a few known issues in KB5095093 that are unrelated to the BITS fix. For instance, some users might encounter a brief flicker when using virtual desktops, and there’s a minor cosmetic bug in the taskbar search box after installing this update. None of these are showstoppers, but they’re reminders that preview updates are for the brave.

Also, this update does not alter the default BITS timeout registry keys—those are still under the hood for advanced tweakers. The fix is purely within the service’s binary and its shutdown routine. That means IT admins who previously hacked the timeout to mitigate the problem might not need to revert their changes, but the improvement will likely complement those tweaks.

The Bigger Picture: Windows Service Management

This BITS fix is more than a one-off patch; it reflects a growing awareness inside Microsoft that small, invisible background processes have a massive impact on the feel of the operating system. A shutdown isn’t just a final act—it’s a crucial part of the user experience. When a PC takes forever to turn off, it leaves a sour taste, especially when you’re rushing out the door or ending a long day.

Microsoft has made similar investments in optimizing service startup and shutdown in the past. Windows 11 originally tightened the leash on startup service delays with its “Fast Startup” and “Service Start Optimization.” The work on BITS is a logical next step, targeting one of the most common background services that users don’t even know exists.

Expect more such refinements. The Windows Servicing team now actively monitors telemetry for service shutdown times, and a fix like KB5095093 likely grew out of data showing a spike in timeouts that correlated with BITS activity. This data-driven approach means that fixes become more precise and less disruptive.

A Quick Test: See If Your System Is Affected

If you’re unsure whether BITS is dragging your shutdowns, you can check the System event log. Open Event Viewer and navigate to Windows Logs > System. Look for events with Source “Service Control Manager” around the time of your last shutdown. If you see an event ID 7043 (a service did not stop in a timely fashion) that mentions “Background Intelligent Transfer Service,” your system will benefit from this update. The timeout value listed in the event will vary, but any repeated instances indicate the fix is for you.

Another telltale sign: run a command-line query of BITS jobs. Open PowerShell as admin and run Get-BitsTransfer | ? JobState -eq 'Transferring'. If you see stale transfers that never progress, BITS might be stuck. The patch won’t clear those old jobs—you’ll need to manually cancel them with Get-BitsTransfer | Remove-BitsTransfer—but it will prevent new ones from causing the same shutdown hang.

What’s Next: July Patch Tuesday and Beyond

KB5095093 will mature into the July 2026 cumulative update, designated as a “B” release. That rollout follows the standard cadence: an update pushed via Windows Update to all non-managed devices starting July 14, with a gradual phased rollout. Enterprises managing updates through WSUS or Microsoft Intune will receive the bits simultaneously for deployment validation.

If no major issues surface during the preview period, the July Patch Tuesday package will include the BITS fix along with all other fixes from the June preview. That means even if you skip the optional update, the shutdown speed-up will come to your PC automatically within weeks.

One lingering question: will Microsoft extend this improvement to Windows 10? The BITS service is identical in Windows 10, and users there have reported similar shutdown delays. However, Windows 10 is now in extended support and receives only security fixes, not quality-of-life improvements like this one. It’s unlikely but not impossible. A senior Microsoft engineer hinted on a Tech Community thread that cross-version bugs with high user impact are occasionally considered for backport, but no promise was made.

The Bottom Line

KB5095093 is a deceptively simple update that fixes a deeply irritating problem. By teaching BITS to stop faster, Microsoft has shaved precious seconds—sometimes minutes—off the shutdown experience for Windows 11 users. It’s a perfect example of how incremental servicing can polish the rough edges of a modern operating system. Available now as a preview, it’s a safe bet for any user plagued by “Shutting down” purgatory. For everyone else, it’s just a few weeks away from arriving as a mandatory update. Either way, the days of waiting endlessly for Windows 11 to power down are numbered.