Urgent => Unexpected error after Windows update

Windows wanted to update. I updated. Reboot. Boom => Docker Desktop says this:

I clicked “Gather diagnostics” but it got stuck there gathering diagnostics for more than 15 mins.

I depend on docker desktop to work. Any help welcome!

  • Restart Docker Desktop and PC.
  • Run wsl --shutdown and wsl --update in PowerShell (admin).
  • Check WSL: wsl -l -v. Unregister stuck distributions: wsl --unregister docker-desktop.
  • Ensure virtualization is enabled (Task Manager > Performance > CPU).
  • Reset Docker: Settings > Troubleshoot > Reset to factory defaults.
  • If diagnostics hang, run: “C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe” gather -upload.
  • Reinstall Docker if needed.

If you want to keep data, DO NOT reset Docker Desktop as suggested in the previous post and I’m not sure about unregistering either, but it is true, the actual data is on a separate disk. Of course if you want to completely reinstall everything, you can try anything.

If gathering diagnostics hangs, you can indeed try rebooting the machine or just killing Docker Desktop, but if it is a work machine I assume you already tried it and I don’t think you could fix the hanging by also trying to upload the diagnostics as that would hang the same way if some endpoint is not available.

If it was triggered by a Windows update, you can check your Docker Desktop version. Maybe you had an old Docker Desktop and the new version of WSl or anything on Windows is not compatible with it.

You can also check GitHub for existing issues

Of course, I can not “Reset to factory defaults” at all. That’s not an expected solution. I have plenty of production data. I can’t also “unregister and re-register” distributions so happily.

Factory default => That’s as hard as “okay, my car is not starting today” - “ah, throw it away and buy a new one”. Even change the base distribution => “Oh, I can’t open the door of my home” - “ah, change your city, go to a new town and buy a new home there”.

And about having tried to restart and so… yes naturally I did.

About docker desktop versions => I have it automatically download things and manually click to install.

Said this:

  • I uninstalled the windows update => Docker desktop worked.
  • After 24h Windows re-prepared the update and this morning I found the PC restarted => SURPRISINGLY Docker desktop worked.
  • But then I saw “there’s a new version of docker desktop” => I updated docker desktop => It fails again with the very same window.

I’m going to reboot again. If it fails I’ll roll back the Windows update again and see.

I confirm:

  • Failiing (from the last post)
  • Rebooted => Failing
  • Uninstalled windows update => Reboot => Docker Desktop works

Docker Desktop version: v4.41.2

I’m happy with rolling back the win update.

@developers => Is it useful for you to take diagnostics out so you can investigate?

Have you tried updating the WSL version?

I remember a situation in the past, where a Windows update made WSL2 stop working with an obscure error message. It started working again, once I installed the latest WSL2 release from GitHub.

Here is link to the current latest release:

The developoers are usually not here. You can find them on GitHub in the repository I linked in my previous message. This is a community forum mainly with community members.

I hope @meyay’s suggestion helps, but if not, I recommend opening a ticket on GitHub and sharing the Windows build version with the developers or any information you can about the Windows update. And yes, you can run a diagnostic with the “-upload” flag and share the diagnostic ID on GitHub. We wouldn’t be able to see your diagnostic data.

Was it the KB5058379 update (May 13th), and do you use bit locker? There’s a bit of a problem with the May 13th Windows update. Trying to avoid interrupting my containers with yet another needless update.

I had the same problem after the windows update, nothing worked and I ended up deleting Docker Desktop and reverting the update which solved the problem. I use Docker to run the a Pi Network Node and not being tech savvy I took a chance. Running Pi Network and Docker on a stripped laptop where all Unnecessary programs and ad ons are removed. I got lucky I guess. Thanks for the insight into this hick up :slight_smile:

Truly IDK what update do I have, as Windows insisted many times in auto-installing even if I had disabled the auto updates. Now it’s been a few days I’m delaying the install by reprogramming each day for a future date.

Also IDK what’s the bit-locker thing.

So to answer your double-question, if you guide me with some tips/steps, I’d be more than happy to answer.