You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Docker Desktop Crashed After upgrade 4.90 -> 4.96 #766
Looking at your diagnostics, the root cause is this error during Windows container startup:
Failed to start Windows containers: System.Exception: Path contains symlink: C:\ProgramData\Docker\exec-root\extensions\callback.sock
This has already been identified internally and fixed. The fix will be available in Docker Desktop 4.97, you’re currently on 4.96.0, just before the fix lands, so please look out for the new version and update once available.
In the meantime, here’s a workaround that’s resolved this for other users hitting the same issue:
Right-click the Docker icon in the system tray → Quit Docker Desktop.
note: workaround appears to be required after each windows reboot, callback.sock possibly generated during the startup process of an underlying service.
Activity
fire332 commentedon Oct 21, 2026
Possible duplicate of #729
MarCezG commentedon Oct 22, 2026
Hi @TheDoubleH , thanks for the report.
Looking at your diagnostics, the root cause is this error during Windows container startup:
Failed to start Windows containers: System.Exception: Path contains symlink: C:\ProgramData\Docker\exec-root\extensions\callback.sock
This has already been identified internally and fixed. The fix will be available in Docker Desktop 4.97, you’re currently on 4.96.0, just before the fix lands, so please look out for the new version and update once available.
In the meantime, here’s a workaround that’s resolved this for other users hitting the same issue:
Right-click the Docker icon in the system tray → Quit Docker Desktop.
Open an elevated PowerShell and run:
'''
powershell
Stop-Service com.docker.service
Remove-Item "C:\ProgramData\Docker\exec-root\extensions\callback.sock" -Force
Start-Service com.docker.service
'''
Start Docker Desktop again.
GreyGhostStudio commentedon Oct 22, 2026
note: workaround appears to be required after each windows reboot, callback.sock possibly generated during the startup process of an underlying service.