Repository navigation
UAC requires elevation prompt every time after reboot OS #13806
Description
Description
After every OS reboot i get UAC elevation prompt for "Docker Desktop Privileged Helper" for program location ["C:\Program Files\Docker\Docker\resources\com.docker.admin.exe" wsl-update].
After restart Docker Desktop i don't get UAC prompt.
Reproduce
- Reboot OS.
Expected behavior
No response
docker version
Client:
Cloud integration: v1.0.35+desktop.5
Version: 24.0.6
API version: 1.43
Go version: go1.20.7
Git commit: ed223bc
Built: Mon Sep 4 12:32:48 2023
OS/Arch: windows/amd64
Context: default
Server: Docker Desktop 4.25.2 (129061)
Engine:
Version: 24.0.6
API version: 1.43 (minimum version 1.12)
Go version: go1.20.7
Git commit: 1a79695
Built: Mon Sep 4 12:32:16 2023
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.22
GitCommit: 8165feabfdfe38c65b599c4993d227328c231fca
runc:
Version: 1.1.8
GitCommit: v1.1.8-0-g82f18fe
docker-init:
Version: 0.19.0
GitCommit: de40ad0docker info
Client:
Version: 24.0.6
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.2-desktop.5
Path: C:\Program Files\Docker\cli-plugins\docker-buildx.exe
compose: Docker Compose (Docker Inc.)
Version: v2.23.0-desktop.1
Path: C:\Program Files\Docker\cli-plugins\docker-compose.exe
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.0
Path: C:\Program Files\Docker\cli-plugins\docker-dev.exe
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.20
Path: C:\Program Files\Docker\cli-plugins\docker-extension.exe
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v0.1.0-beta.9
Path: C:\Program Files\Docker\cli-plugins\docker-init.exe
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: C:\Program Files\Docker\cli-plugins\docker-sbom.exe
scan: Docker Scan (Docker Inc.)
Version: v0.26.0
Path: C:\Program Files\Docker\cli-plugins\docker-scan.exe
scout: Docker Scout (Docker Inc.)
Version: v1.0.9
Path: C:\Program Files\Docker\cli-plugins\docker-scout.exe
Server:
Containers: 2
Running: 0
Paused: 0
Stopped: 2
Images: 2
Server Version: 24.0.6
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: json-file
Cgroup Driver: cgroupfs
Cgroup Version: 1
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8165feabfdfe38c65b599c4993d227328c231fca
runc version: v1.1.8-0-g82f18fe
init version: de40ad0
Security Options:
seccomp
Profile: unconfined
Kernel Version: 5.15.133.1-microsoft-standard-WSL2
Operating System: Docker Desktop
OSType: linux
Architecture: x86_64
CPUs: 12
Total Memory: 899.6MiB
Name: MICHAELHOME
ID: df80417f-325c-47a5-b367-3f50687c814c
Docker Root Dir: /var/lib/docker
Debug Mode: false
HTTP Proxy: http.docker.internal:3128
HTTPS Proxy: http.docker.internal:3128
No Proxy: hubproxy.docker.internal
Experimental: false
Insecure Registries:
hubproxy.docker.internal:5555
127.0.0.0/8
Live Restore Enabled: false
WARNING: No blkio throttle.read_bps_device support
WARNING: No blkio throttle.write_bps_device support
WARNING: No blkio throttle.read_iops_device support
WARNING: No blkio throttle.write_iops_device support
WARNING: daemon is not using the default seccomp profileDiagnostics ID
5EC7FB5E-78B0-408A-929F-8F706FFE9D65/20231124051504
Additional Info
No response
Reacted by rlywtf, Alex Goldobin, rick1906, Silvermind, JeromeGagnonTelus, minzdrav, schulzi66, Glen, Neil Kidd, Sunny and 22 more
Reacted by KernelVonPop
Activity
glen-84 commentedon Jul 28, 2024
I'm seeing this after updating to 4.33.0.
YarosMallorca commentedon Jul 30, 2024
I'm having the same issue
teejay-87 commentedon Jul 31, 2024
Me too, after setting Docker Desktop to start al Windows login.
On my old computer, a year ago or so, it was set this way, but no UAC dialog at login.
tyler36 commentedon Aug 1, 2024
After updating to
4.33.0, I get this popup when I sign-in.It's annoying because I sign-out when I go to meetings or lunch breaks, so I get the popup several times a day.
teejay-87 commentedon Aug 1, 2024
I appears fixed after upgrade to 4.33.1 (maybe related to #14222? that's the only fix mentioned in release notes)
tackarama commentedon Aug 1, 2024
Also started getting this today after upgrade to v4.33.1
Edit:
WSL version: 2.2.4.0
Kernel version: 5.15.153.1-2
WSLg version: 1.0.61
MSRDC version: 1.2.5326
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26091.1-240325-1447.ge-release
Windows version: 10.0.22631.3958
Edit 03/08/2024:
I repeated the build process on an identical Windows machine using "Docker Desktop Installer.exe" v4.32.0.0 & then followed the upgrade to v4.33.1 and got the same UAC error.
I de-installed Docker & reinstalled v4.32.0.0, built my containers & rebooted & (not that surprisingly) I don't get the UAC prompt every time Docker starts.
Mickachouw commentedon Aug 1, 2024
Same here, as @tackarama
Edit : launched wsl --update --pre-release in pwsh, have WSL version: 2.3.14.0 right now, coming from 2.2.4 and new Kernel version for WSL,
Docker Desktop works fine now, but all images are lost ☹ . So good so far ...
tyler36 commentedon Aug 1, 2024
4.33.1fixed issue that was caused by4.33.0, YMMVUPDATE: After the week, the popup was back. Not sure why it didn't display after restarts last week.
NorthNick commentedon Aug 2, 2024
I also have this since upgrading to 4.33.1
ps-tunnelsoft commentedon Aug 2, 2024
with 4.33.1 I am now stuck with endless UAC requests .. it tries to start the engine, stops and asks for UAC again.
if I cancel the UAC, I see that it tries to run the "wsl --update" cmd
edit:
found the issue: wsl update to 2.2.4 was not possible. I had to remove the installation manually and install the update myself. Docker desktop works again now with up to date wsl kernel
27 remaining items
cgtarmenta commentedon Aug 20, 2024
@andrea-reale Yes I've tried the dev build, and got the same error.
RN I'm back in 4.32 and using a custom kernel for WSL as is required by redroid image I'm working on, but i'll try again today in the afternoon to grab better info for you.
cheers.
arnowelzel commentedon Aug 20, 2024
Unfortunately - no it does not :-(
After a few days, Docker Desktop did not start at all with some VM errors (sorry, did not record them) and I went back to version 4.32.0 (completely uninstalled 4.33.1 then reinstalled 4.32.0) - which works ok so far. This is already the second major problem I experienced with Docker Desktop in less than 6 months. Before there was an issue with 4.29.
It seems, upgrading Docker Desktop can be a risky thing and it is always a good idea to keep older versions just in case.
NorthNick commentedon Aug 20, 2024
I have perhaps the same problem as @arnowelzel - the development build worked for a while, but now gives an error when starting Windows, saying "running engine: waiting for the VM setup to be ready: starting WSL engine: bootstrapping in the main distro: context canceled". Docker Desktop then works when started manually so I haven't bothered reporting it before now. It's not completely reliable: maybe one time in 5 a Windows boot completes without the error.
Diagnostics ID: A28AE790-279C-4CA2-89C1-ED7EA701D72E/20240820101832
andrea-reale commentedon Aug 20, 2024
@NorthNick Thanks for uploading and sharing the diagnostics. Unfortunately, you are experiencing a known bug where the
docker-desktopWSL distribution enters an undesired state; the good news is that the fix is included in the upcoming Docker Desktop 4.34.Until then, you can of course keep using 4.32 or work around the bug by:
NorthNick commentedon Aug 20, 2024
@andrea-reale Thanks for the update. I'll try the work around, and just wait for 4.34 if that doesn't work.
cgtarmenta commentedon Aug 21, 2024
@andrea-reale I've the dev build working with the suggested command just a little bit modified:
It is working even with a custom kernel, so many thanks for this.
cheers.
shalafi99 commentedon Aug 22, 2024
@andrea-reale, your dev build solved that Privileged Helper UAC issue for my setup.
WSL version: 2.2.4.0, default kernel.
Thanks
shalafi99 commentedon Aug 23, 2024
Spoke too soon. @andrea-reale, with build 162079 no longer the UAC Helper prompt appears but on the initial start-up (post Windows boot/restart) I get the same issue NorthNick reported in this thread:
Captured Diagnostics ID F7279E79-7518-4A6F-ADA3-C759A0264C75/20240823112248
Some kind of race condition between Docker's and WSL's startup routines?
I confirm this behavior is only present on the first Docker Desktop start-up after Windows is booted/restarted.
If I close that error dialog and try manually again, Docker starts without issue.
To work around it, I disabled Docker's native autostart (in settings) and created a scheduled task to run "C:\Program Files\Docker\Docker\Docker Desktop.exe" a few minutes after the user logon.
glen-84 commentedon Aug 23, 2024
@andrea-reale When will 4.33.2 be released?
theBNT commentedon Aug 26, 2024
does this workaround work for you? it might state that the file is not found but then it worked for me
theBNT commentedon Aug 26, 2024
according to my information from docker support, there is a DD 4.34 release planned for august 29th, keeping fingers crossed :)
shalafi99 commentedon Aug 27, 2024
It did not work at first. I got the same error so to try to get around it further I set up 2 scheduled tasks, one to run "wsl ifconfig" (anything that would need wsl to be up, for that matter) and a few minutes later, the "docker desktop" one.That worked once... on the next Windows restart it failed the same way as before.
Maybe I got 'greedy' to leave each task with only 3 minutes apart from each other :-/ (and task scheduler did not respect that time offset judiciously enough), I will readjust to leave them further separated time-wise and see what happens.
*edit: scratch that... what is working for me is to left "Start Docker Desktop when you sign in to your computer" active and paired with a scheduled task set to run this powershell below, some minutes after the user logon (giving enough time to allow for the WSL related error to happen):
lorenrh commentedon Aug 30, 2024
4.34.0 has been released with a fix for this issue, more information o the release notes.
I'll be closing this issue, but if the problem persists please open a fresh issue!
rfay commentedon Aug 30, 2024
But if you open a fresh issue, please link it here if it's the same behavior, thanks.