The Windows Update That Turned Desktops Black, and What KB5124008 Actually Fixes
For a couple of weeks this September, a decent number of Windows 11 users opened their laptops to a desktop that had gone completely black. Not a crash, not a driver issue, not a monitor problem. The wallpaper itself, the thing sitting behind the icons and the taskbar, had simply stopped being there. Anyone who tried to fix it the obvious way, by going back into Settings and reselecting their picture or slideshow, found that nothing they picked actually stuck. The desktop stayed black no matter what.
The cause turned out to be an optional preview update Microsoft shipped on August 27, 2026, and the fix arrived with this month's Patch Tuesday on September 8. Both are now documented, and the story is a useful, concrete reminder of something easy to forget: the wallpaper on a Windows desktop isn't just a picture file, it's a setting stored and loaded by the operating system itself, and when that storage layer breaks, the picture disappears along with it, regardless of how good the picture was.
What actually happened
The update at fault is KB5120998, an optional, non-security preview update released August 27, 2026 for Windows 11, version 24H2, and Windows 11, version 25H2. Preview updates like this one are opt-in. They go out to people who have turned on "Get the latest updates as soon as they're available" in Windows Update, specifically so early adopters can catch problems before a fix rolls into the following month's mandatory security update. In this case, the preview update introduced exactly the kind of problem it exists to catch.
After installing KB5120998, some desktop personalization settings stopped loading correctly. Microsoft's own description of the issue is specific: desktop background settings could fail to load, and Windows would fall back to a plain black background instead. Other personalization settings were affected too, including slideshow configuration and high-contrast theme choices. The frustrating part, for anyone who hit it, was that manually reselecting a wallpaper in Settings didn't help. The bug prevented the setting from loading correctly regardless of what value was actually stored, so the system kept defaulting back to black no matter what the user picked. Some reports from the same update cycle also mentioned mouse settings behaving oddly, suggesting the preview build had a broader problem with how certain user preferences were being read back after being written.
The fix: KB5124008, September 8, 2026
Microsoft resolved the issue with KB5124008, released as part of the regular, mandatory September 2026 Patch Tuesday cycle on September 8. Unlike the preview update that caused the problem, KB5124008 isn't optional. It's the standard monthly security update, and it brings Windows 11, version 24H2, to build 26100.9445 and Windows 11, version 25H2, to build 26200.9445. Among its listed fixes is the exact issue described above: desktop background and other personalization settings failing to load correctly, including the black background fallback.
KB5124008 also folds in a handful of unrelated fixes from the same update cycle, among them adjustments to how Date and Time settings behave, a fix for Remote Desktop audio redirection, and improved diagnostic logging for the OMA-DM client used in managed and enterprise deployments. None of those are related to the wallpaper bug specifically, they're just part of the same monthly cumulative package, which is standard for how Windows rolls up unrelated fixes into one update rather than shipping each one separately.
If your desktop went black sometime after August 27 and you haven't touched Windows Update since, KB5124008 is the update you're waiting for. It installs the same way any other Patch Tuesday update does, through Settings, Windows Update, and it does not require uninstalling KB5120998 first. Once it's applied, personalization settings load correctly again and a previously configured wallpaper, slideshow, or theme should return without needing to be reconfigured from scratch, since the underlying setting was still stored correctly the whole time. It was only the loading step that was broken.
Why this is a genuinely instructive bug, not just a nuisance
It's worth sitting with why this particular failure mode happened at all. A desktop wallpaper on Windows isn't just an image sitting in a folder. The path to that image, along with the fit mode, slideshow interval, and theme choice, lives in a settings store that Windows reads on login and on demand whenever personalization changes. When that read path breaks, as it did with KB5120998, the operating system has no reliable way to know what the user actually wanted, so it falls back to the safest default it has: nothing, rendered as flat black.
That's a completely different kind of fragility than most people assume a wallpaper has. A photo doesn't get corrupted, a file doesn't go missing, nothing about the picture itself changes. What breaks is the plumbing between the operating system and the setting that points at the picture. We touched on a related piece of that plumbing back when we covered the quieter background-settings fixes bundled into Windows 11 26H2's fall update, and this incident is a sharper, more visible example of the same underlying idea: the Background settings page in Windows has more moving parts than it looks like, and those parts can and do fail independently of anything the user did wrong.
Why a live wallpaper app never saw this problem
If you were running Gloomia during this whole episode, your wallpaper almost certainly kept animating normally the entire time, and it's worth explaining exactly why, rather than just asserting it. Gloomia doesn't hand Windows a static image and ask the Background settings page to display it on a schedule. It runs as its own continuous rendering layer, positioned beneath your icons and windows, drawing every frame itself in real time. It never needs to ask the Windows personalization settings store what picture to show, because there isn't a picture in the first place, there's a scene being rendered live.
That distinction is the same one we walked through in more detail in our comparison of how a live wallpaper actually differs from a screensaver at the settings level, and it's also why a native feature like the DreamScene-style video wallpapers Microsoft has been testing, which we covered in our look at Windows 11's own video wallpaper experiment, still ultimately depends on the same personalization settings pipeline that just broke for millions of people. A feature built directly into that pipeline inherits its failure modes. A separate rendering layer, sitting outside it, doesn't.
None of that is a reason to be careless about backing up your own settings, though. If you rely on Gloomia's own scheduler to rotate between wallpapers across the day, the way we walked through in our guide to Gloomia's scheduler, filters, and photo wallpaper mode, that configuration lives inside Gloomia itself, not inside the Windows settings store this bug affected, so it was never at risk here either. The practical lesson is a general one: the more of your desktop's look that lives in a dedicated app's own configuration rather than scattered across operating system settings pages, the fewer places a single bad update can quietly break it.
What to do if your desktop is still black
If you're reading this because your own desktop is currently black, the fix is straightforward. Open Settings, go to Windows Update, and check Update history for KB5120998 dated around August 27. If it's there and nothing more recent has installed since, check for updates and install KB5124008 when it's offered. You do not need to uninstall the preview update first, and you do not need to reset your personalization settings, since the underlying values were preserved the whole time and simply weren't being read correctly. Once KB5124008 finishes installing and the machine restarts, your previous wallpaper, slideshow, or theme choice should reappear on its own.
If you'd rather not depend on that settings pipeline being fragile again in the future, this is also a reasonable moment to consider whether your desktop background should sit inside Windows' own personalization store at all, or run as an independent layer the way a live wallpaper does. That's not a dig at Windows specifically, every operating system's personalization settings are, at bottom, just another piece of software that can have a bad release. It's simply a reminder that a background running as its own rendering process is one less thing that can go black the next time an update ships before it's fully tested.
The bigger picture: preview updates are doing their job here
It's easy to read a story like this as evidence that Windows Update is careless, but the more accurate reading is close to the opposite. KB5120998 was explicitly an optional preview update, opted into by people who turned on early updates specifically to surface exactly this kind of regression before it reaches the mandatory monthly release everyone else gets. It did its job: the bug was caught, reported, and fixed within roughly two weeks, and it never shipped in the standard, non-optional update path most Windows 11 users are actually on. If you don't deliberately enable "Get the latest updates as soon as they're available" in Windows Update, you were never exposed to this specific bug at all, and you'll simply receive KB5124008 as a normal, working September security update with no black desktop in between.
That's worth remembering the next time a preview update notification shows up. Early updates exist to take a small amount of individual risk in exchange for the wider Windows 11 user base getting a more reliable release the following month. This time, that trade played out exactly as designed, even if it meant a couple of frustrating weeks for the people who opted in.
Frequently asked questions
What exactly caused Windows 11 desktops to turn black in August 2026?
An optional, non-security preview update, KB5120998, released August 27, 2026 for Windows 11 24H2 and 25H2, introduced a bug where desktop background and other personalization settings failed to load correctly. Instead of showing the user's chosen wallpaper, affected machines fell back to a solid black background.
Which Windows 11 versions were affected by the black desktop bug?
Microsoft confirmed the issue on Windows 11, version 24H2, and Windows 11, version 25H2, on any machine that had installed the August 27, 2026 KB5120998 preview update. Machines that skipped that optional update were not affected.
Does KB5124008 fully fix the black desktop bug?
Yes. Microsoft's September 8, 2026 Patch Tuesday update, KB5124008, brings Windows 11 24H2 to build 26100.9445 and 25H2 to build 26200.9445, and its documented fixes include the desktop background and personalization settings failing to load correctly.
Will this bug affect Gloomia or other live wallpaper apps?
No. The bug sat in the personalization settings store Windows itself uses to remember a static wallpaper, slideshow, or theme choice. Gloomia renders its own scene continuously on a separate layer and does not read from or depend on that same settings store, so a Gloomia desktop kept showing its live wallpaper normally even on machines hit by the KB5120998 bug.
Should I install KB5124008 right away?
If you installed the optional KB5120998 preview update in late August and are now looking at a black desktop, yes, KB5124008 is the direct fix and should be installed as soon as it's offered through Windows Update. If you never installed the August preview update, you were never affected by this specific bug, though KB5124008 is still worth installing as the regular September security update.
How do I check if I'm still running the buggy KB5120998 preview update?
Open Settings, then Windows Update, then Update history, and look for KB5120998 dated around August 27, 2026. If it's the most recent update listed and your background settings look wrong, installing KB5124008 through the same Update history page resolves it without needing to uninstall anything first.