There was another issue related to elevation. Someone wrote it would likely be fixed in 4.72. The issue is still open, but if it was fixed (I don’t see it in the release notes), it is possible that it introduced a new issue.
New installations of Docker Desktop for Windows have a choice between per-user (Beta) or all-user installs.
It is for new installations, but I can imagine it breaking something for updates.
I also updated my Docker DEsktiop on Windows, but I didn’T experience the linked issue either and I had 4.58. Upgrading to 4.72 worked without any problem.
If you have no data in Docker Desktop, you could try reinstalling. That would confirm that new installations works.
Or you can open a new ticket on GitHub and link the one I linked above as possible related issue.
But I have many projects running on Docker with multiple containers. If I download a new release and install it, would it just update Docker, or would it erase everything?
Yep that does the trick nicely, thanks. I’m not sure why it’s not prompting the elevated UAC prompt for it to update this time though? Previous updates all went through OK.
Not sure, but I thought you would also uninstall the old version first. You wouldn’t lose anything if you don’t store data on the container filesystems and use bind mounts instead of local volumes or local volumes with a custom host path in a WSL distro where WSL integration is enabled. That way you don’t depend on data stored in Docker Desktop and you could recreate everything if you have compose files. Just an idea for the future.
It is not important now. Running Docker Desktop as administrator was a good idea.
I found the solution was to navigate to the file in ApData and run it as admin. It installed the new version but my existing docker set-ups remained in place.