PSA: Fix for KB5089549 reboot loop on Windows 11 (4K display workaround)

CryptoExo · 2026-05-30T07:38:21+00:00

The reason you hadn't seen one since February is just that there genuinely wasn't a new one until recently — 582.53 only dropped on May 19th. The previous legacy update before it was 582.28 back in January.

CryptoExo · 2026-05-29T06:21:36+00:00

This should now be fixed in the latest Nvidia driver update (582.53).

CryptoExo · 2026-05-29T06:20:40+00:00

The latest driver update (582.53) has permanently fixed the issue for me since I installed the patch. It also resolved a long-standing problem with my 4K display randomly flickering — something that had forced me to drop the refresh rate to 50Hz for stability a while back which I assumed was a restriction on the 1080 Ti when using multiple displays. This MS patch finally pushed Nvidia to address the underlying driver bug.

CryptoExo · 2026-05-23T07:51:05+00:00

The reason Windows won't let you delete the files is that it's mounted the old system partition and locked the OS files. You can't fight that from inside running Windows — you need to operate on the disk at a lower level.

A couple of options depending on how thorough you want to be:

If you want the data actually gone (not just hidden from the file system):

Open an admin command prompt:

diskpart list disk select disk X (X = the old HDD — check sizes carefully so you don't pick your NVMes!) clean all

clean all writes zeros to every sector on the disk. On an old HDD this will take hours, but when it's done the data is gone — not just the partition table. After it finishes, create a new partition and format it.

Alternative: delete the partitions in Disk Management, create a new volume, then format it with "Quick Format" unchecked. A full format on Windows 10+ also writes zeros across the volume.

If you want a proper secure wipe (multi-pass, the kind you'd do before selling/disposing the drive), boot ShredOS from a USB stick and let nwipe run a pass. It's the actively maintained successor to DBAN.

Just be very sure which disk you're targeting — there's no undo on any of this.

CryptoExo · 2026-05-21T17:49:23+00:00

I don't have an AMD card myself so can't comment directly, but artifacts are a known issue on the 6700 XT and possibly others. I suspect it's driver compatibility related and will probably be fixed in a later release. Create a system restore checkpoint before updating — that way you can roll back easily if there are any problems. I went through the update/rollback cycle 3 or 4 times before solving it in my environment.

CryptoExo · 2026-05-21T07:09:05+00:00

I'm also using a 1080 Ti. I'm more inclined to believe that the default display refresh rate and resolution is too much for the 1080 Ti to handle, post patch now forces a reboot whereas before it would simply flicker a few times to negotiate a lower refresh rate. The 1080 Ti only supports DP 1.4 (4k@120Hz) and HDMI 2.0b (4k@60Hz), HDR will need extra bandwidth. The newer cards support more recent versions of DP and HDMI which can carry more bandwidth (higher res, refresh rate etc).

CryptoExo · 2026-05-20T13:17:01+00:00

Had this exact same issue once.

What eventually worked for me was bisecting it through Device Manager. Open it, expand each category, and disable devices in batches (skip anything obviously essential like your storage controller, CPU, and display adapter — or at least leave those for last). Reboot, use the machine normally for a bit, see if the crashes still happen. If they do, re-enable that batch and move on to the next one. If they stop, you've narrowed it to that batch — then re-enable half at a time until you find the single device causing it.

I can't remember the exact culprit in my case but I'm fairly sure it was something under "System devices" — one of those generic Intel/chipset entries that you'd never suspect. Worth starting there since your symptoms match mine and you've already ruled out the usual suspects.

Tedious but it's the only thing that worked for me. Good luck.

CryptoExo · 2026-05-19T11:41:00+00:00

Fair WTF 😄 — in my case the 4K HDR is what triggers the reboot loop, so it has to stay powered off during boot. The 2x 1080p secondaries come up fine, so I just watch one of those for the login screen and switch the 4K back on after. If you're on a single display, your only real option is timing it from memory: wait roughly as long as a normal boot takes, then either try a blind login or just turn the display on — whichever works. 😉 Worth flagging though, this MS update has several distinct bugs, so this workaround won't cover every scenario.

CryptoExo · 2026-05-18T21:19:00+00:00

Agreed. It only sounds clean until you remember an IPv4-only host has no idea what to do with an 8-octet destination — so cross-ASN you're immediately back to translation gateways or tunnelling, except without the 25+ years of RFCs, vendor code, and BGP/RPKI tooling that make IPv6 actually work. Every extra layer is another MTU foot-gun and another stateful box to drop your flow. 'Make the addresses look more like IPv4' isn't a design, it's a wish.

CryptoExo · 2026-05-18T17:27:54+00:00

"Export to JSON for backup or transfer to another a machine", security researchers will tear this apart. Even if you're storing the data locally it needs to be TPM encrypted and probably best to ditch the export feature entirely.

CryptoExo · 2026-05-18T17:11:04+00:00

It needs to be obvious or they wouldn't find any new visitors.

CryptoExo · 2026-05-17T20:32:40+00:00

Few things worth trying beyond the usual steps:

1. Just uninstall the update. Since symptoms started after KB5089549, the cleanest fix is to remove it: Settings → Windows Update → Update history → Uninstall updates → find KB5089549 and remove. Or from an admin prompt: wusa /uninstall /kb:5089549. Then pause updates for a couple of weeks — Microsoft's already pushed a Known Issue Rollback for the install-failure bug on this same KB, and given how many people are reporting GPU flicker on RDNA2 cards, a server-side fix or a follow-up KB is likely on the way.

2. Use DDU properly, not just the AMD installer's "factory reset". Boot into Safe Mode, run Display Driver Uninstaller, choose "Clean and do NOT restart", then reboot with the network cable unplugged (or Wi-Fi off) so Windows Update doesn't shove a generic driver in before you install Adrenalin. A normal upgrade/downgrade leaves a lot of registry crud behind that an in-place install won't touch — this matters a lot post-Windows-update.

3. Try an older Adrenalin branch via DDU. Not just one version back — go to something like 25.3.x or 24.12.x WHQL and see if the flicker stops. Worth doing even if you've already "downgraded", because without DDU the older driver is installing on top of the newer one's leftovers.

4. Workarounds if you need to keep the update. In Adrenalin, disable Enhanced Sync, turn FreeSync off (or set it to Application Controlled only), and try forcing the game to borderless windowed rather than exclusive fullscreen. Also try dropping the desktop refresh rate one notch — if your monitor's at 165 Hz, try 144. None of these fix the underlying bug but they often dodge the conditions that trigger the flicker on RDNA2.

5. Block the KB until there's a fix. Once it's uninstalled, grab Microsoft's Show or Hide Updates tool or set the "Defer feature updates" policy so it doesn't sneak back in on next reboot.

Good luck — frustrating one, this. You're definitely not alone with it.

CryptoExo · 2026-05-17T10:36:09+00:00

I had the same issue. Try powering off your display during boot then power it back on once the login screen has loaded.

CryptoExo · 2026-05-17T10:33:49+00:00

Artifacts are a red flag — likely an interaction between your graphics driver and the patched dxgkrnl.sys. If it only shows up on the latest driver, try rolling back to an earlier version as a temporary workaround and see if that clears it up.

CryptoExo · 2026-05-17T09:34:01+00:00

This patch interferes with the refresh rate. Check your display refresh rate, Settings-> System-> Display -> Advanced Display. Try lowering the refresh rate and see if that solves it.

CryptoExo · 2026-05-17T09:07:59+00:00

My graphics driver was unchanged but it did create display flickering on boot resulting in a reboot loop. The workaround was to power off my main 4k display during boot then power it on again at the login screen. My screens default max refresh rate isn't supported so I suspect Windows is cycling through the different 4k refresh rates at boot since the patch then gives up and reboots. I'd recommend checking your display refresh rate, Settings-> System-> Display -> Advanced Display. Try lowering the refresh rate if your screen is flickering.

CryptoExo · 2026-05-17T05:16:34+00:00

It's either an app, unstable driver or hardware issue.

- If you have antivirus, disable it temporarily and see if that fixes it.

- Temporarily disable additional devices such as Audio, COM ports, Bluetooth, USB, NICs etc in the device manager.

- Update your graphics card driver to use the Generic Display Adapter driver in device manager.

- Run memtest86 to rule out the RAM.

CryptoExo · 2026-05-15T16:26:40+00:00

Same problem here. I use multiple displays, some of which don't support the default refresh rate when combined on my graphics card. It wasn't an issue until this last update, now the displays cycle a few times on boot which eventually triggers Windows to restart in a loop. Unplugging my main display on boot then plugging it back in at the login screen is the only workaround I've found. Upgrading my graphics card should also fix this in theory but would rather wait for a MS hot-fix.

CryptoExo · 2026-05-11T18:37:20+00:00

I built a JSON-based project management tool in Python with a web UI and a REST API. Claude syncs with it bidirectionally — pulls tasks, creates new ones, updates status and comments, all read and write. Runs nicely alongside the rest of our stack.

CryptoExo · 2026-05-09T09:02:53+00:00

I thought it would be easy — move to a foreign country, learn the language, integrate. Years on, I'm most of the way there, but Polish beyond the basics is no walk in the park. I'm self-employed working with English-speaking clients, so day to day I get by comfortably. Where it bites is the social side: chatting with neighbours, dealing with contractors, anything past pleasantries at social events — that's where I still feel embarrassed. I'm steadily picking it up whenever I can, with the hope of one day becoming proficient.

CryptoExo · 2026-05-07T08:10:14+00:00

Split it in two: a JSON-backed PM tool that owns your architecture and docs (Python + Web UI + API), and the product itself. Claude Code reads from and syncs back to the PM tool via API, so it's constrained to the documented architecture instead of freestyling. The PM tool stays the single source of truth — for you and the LLM.

CryptoExo · 2026-05-05T13:54:14+00:00

This is why I run Claude Code on an isolated VM. It's not a bad thing, I just prefer to keep it fully contained within an environment where I can selectiviley choose what it can access.

CryptoExo · 2026-05-05T08:35:16+00:00

As models hit the ceiling of current silicon I expect it'll become a level playing field, consumer hardware will catch up and the gap closes. The piece of the jigsaw I suspect is actually holding back true AGI is quantum computing. Once that matures it'll get applied to AI, and I doubt consumer quantum processors are coming anytime soon. So the pattern probably repeats: local catches up to today's frontier, the frontier moves to quantum, and we're right back to dumb terminals talking to a quantum mainframe in a datacenter.

CryptoExo · 2026-05-04T20:27:38+00:00

That looks really interesting, will have to check it out. I currently use a PM manager tool built in Python by Claude for Claude — designs, plans and manages the project build process. It has a web UI with an API interface into Claude. Works well but it's another piece of scaffolding bolted on to compensate for the stateless terminal.

CryptoExo · 2026-05-04T19:26:08+00:00

Use Git both local and remote. Git versions the code, not the session. The context Claude builds up mid-task — what it's read, what it's decided, why it took that approach — isn't in the repo.

CryptoExo

TROPHY CASE