I encountered an issue while updating Docker Desktop on my Windows 11 system. The application closed unexpectedly during the update process, and afterward, I noticed that Docker Desktop had been completely deleted. To help understand and resolve this issue, I am providing the following details:
Docker Version: 4.42.0-195023
Operating System: Windows 11
That will not be enough unfortunately. Docker Desktop would not be completely uninstalled just because an upgrade fails. It could be broken, but not completely uninstalled. Unless an antivirus or some security-related software does it. And if it is completly reinstalled, there is not much to do, but I really doubt that it is the case.
You can check what files would need to be removed when uninstalling Docker Desktop and see if anything is still there
And you can open windows services and look for docker there too.
You can check if any antivirus or any software is installed on your machine that could have done this. And you can try the troubleshooting guide which will work only if the diagnostics tools is still there
But that guide also shares where logs files are, so you can do that too. If nothing helps, but you can collect logs, you can share here, or on GitHub
If you can even run the diagnistics, upload the diagnostics ID and share your ID on GitHub, the Docker staff can analyze that too
thank you for quick response. Yeah you’re right docker desktop not completely uninstalled just because an upgrade fails. But the problem when it broke, it’s not show up any app exe or click button for start. But also I don’t have any antivirus things and security-related software apps programs things. Also I’m a developer, that problem is It’s been around for a long time. Docker didn’t fix it. And I’ll make a diagnose and make a issue for that. Thank you
Also I wanna make sure for the security, is there any consider sharing the diagnostics ID to on github. Is there any security concern about for sharing diagnostics ID or logs?
so I marked it as solution because your answer helps me to solve this problem indirectly, i.e. I will run the diagnostics and report it as an issue. So that could be the solution to the problem.
I don’t think the logs would contain any private data like container names or container logs, but if you want to be sure that only Docker can read it, you can contact Docker Support if you have a subscription
If you have a paid Docker subscription, select Contact support. This opens the Docker Desktop support form. Fill in the information required and add the ID you copied in step three to the Diagnostics ID field. Then, select Submit ticket to request Docker Desktop support.
If you don’t have a paid Docker subscription, create an issue on GitHub:
I know the diagnostics ID is part of a URl which could probably be figured out by anyone who knows the ID, but if they don’t know the Id, it would be pretty hard to guess such a long hash.