After updating to v4.73.0, I can’t start Docker Desktop, but if I downgrade to v4.72.0, i can.
Have not yet tested downgrading to v4.72, but have the same problem with v4.73.
If I try so tart Docker Desktop from the cli I see the following messages
[BUGSNAG] Loaded! In main process.
Electron binary was executed directly, will delegate to Docker Desktop backends
open Windows binary C:\Program Files\Docker\Docker\Docker Desktop.exe
[7488:0511/205557.343:ERROR:content\browser\network_service_instance_impl.cc:610] Network service crashed or was terminated, restarting service.
[7488:0511/205557.449:ERROR:content\browser\gpu\gpu_process_host.cc:1004] GPU process exited unexpectedly: exit_code=1
What information might be interesting for further investigation?
Just for fun I tried to start it (=v4.73) from an elevated command line - and it started!
I’m puzzled - but maybe this information helps other users?.
Is it safe to assume that you are also on Windows, @wtrungs?
I just updated it on a Mac, and it works like a charm.
Yes, I’m using Docker Desktop with WSL2.
bump. same thing here
Same thing here. Tried killing WSL but no luck. Background processes start but are abruptly terminarted. Diagnosing if Malwarebytes might have something to do with it now as I had a similar issue a week ago with Chrome doing the same thing requiring an exclusion.
Have you guys gave up on testing your patches now?!?
Why would docker now all of a sudden require Administrator elevated permissions, what’s not being disclosed here?
Same here. Downgrading to older version worked. On Windows 11 and WSL2
I updated it on my Windows 11 using the WSL2 backend. Starting the Docker Engine was a couple of seconds slower than I expected, but worked.
Then I stopped Docker Destkop and could not start again when I clicked on the Docker Desktop logo in the menu.
For some reason, docker desktop status command failed with “Is Docker Desktop runnig?” message, but docker deskop start failed with “Docker DEsktop is already running”. Then I checked the logs
docker desktop logs
and tried docker desktop start again. It worked this time. In the logs, I saw some error messages about license files and some timeouts, but Docker DEsktop was already running at that time.
So I restarted the tests and after “Quit Docker Desktop”, I tried to start it again. The GUI did now appear, icon in the notification bar did not appear. docker desktop status gave me the same error as before, although it should return stopped or running I bleieve. But docker desktop start helped again.
Can you also try the command line?
There is an issue on GitHub, but that seems to be different from what I experience. Maybe it helps some of you.
update:
Now I can’t start it either, because it is already running, but the stop command doesn’t finish. I have to move on for now, but I will generate a diagnostic ID later and share with the developers.
@nutbolt9 You are absolutely right - it doesn’t make sens to run Docker Desktop it with Admin-privileges, that’s why i’m puzzled.
In addition I tried @rimelek 's notes, endet Docker Desktop and started it again from a normal command prompt using docker desktop start - and it workded 
Afterwards I stopped Docker Desktop again and tried to start it from the StartMenu - without success 
But docker desktop start still works.
I also tried to stop and start once again, but this time start didn’t work saying it was still running and stop timed out. After that I killed processes manually in the Task Manager and tried docker desktop start again. That worked again.
I reported it also in an internal chat with Docker sharing my diagnostics ID. Hopefully they will figure it out.
Maybe this helps everyone. On Windows 11 Pro I am able to launch desktop 4.73.0 without any problem when I start it from PowerToys Command Palette. For whatever reason this utility must work differently than PowerToys Run or Windows Start. I haven’t tested exhaustively and for all I know it’s pure coincidence and maybe Docker has changed something on their end to fix things. I’m just trying to get on with my day like everyone else. 
Could it be that you just waited long enough for all processes to stop, before trying again? I tried your idea and Docker Desktop started after about 30 seconds, but for starting Docker Engine, it took another 30 seconds.
So I am not sure if Power Toys Command Palette makes a difference, but thank you for sharing it. I will continue testing it later.
@rimelek Nope. I watched all docker procs with Task Manager. I’ve since tried this a few more times and even verified that PowerToys Run doesn’t work but Command Palette does (it was an excuse to try the latter which will replace Run at some point). Yeah, weird. And for me desktop UI starts instantly when I launch it this way, none of the 30s delay that people are reporting.
Not sure if this helps…
PS C:\WINDOWS\system32> wsl --version
WSL version: 2.7.3.0
Kernel version: 6.6.114.1-1
WSLg version: 1.0.73
MSRDC version: 1.2.6676
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.26200.8246
Thanks. I didn’t even know Command Palette existed, so I already learned something. I also got a response from Docker about 40 minutes earlier that they are already working on a patch.
As far as I know - today will be released 4.73.1 and there will be bugfix for that 
Yes, and it is released now. I tested and stopping and starting Docker Desktop worked. I have not tested if after reboot yet, but I will later today.
update:
It worked after reboot too.
Win11 WSL2 same here after updating to 4.73.1 it stopped working and cant even start containers:
Docker Desktop Version 4.73.1 (226574)
In WSL2:
“failed to connect to the docker API at unix:///var/run/docker.sock; check if the path is correct and if the daemon is running: dial unix /var/run/docker.sock: connect: no such file or directory”
Also get “Failed to stop 1 item.” and “Failed to start 1 item.” when trying to stop or start 1 container (1 container inside docker compose group of containters)