**Start Docker Desktop and wait for the engine, not just the window.** Launch Docker Desktop from the Start menu and wait until its status says the engine is running. A tray icon alone does not mean the pipe exists yet. Expected: the status indicator turns to running.

**Retry the simplest command.** Run docker version and look for a Server section in the output. Success check: the Server section prints a version instead of the pipe error.

**Check the active context.** Run docker context ls and confirm the current context is the desktop-linux one. A context left pointing at a remote host or a removed engine produces connection errors that look like a stopped daemon. Switch back to the desktop context if needed and rerun step 2.

**Check the WSL 2 backend.** Run wsl --list --verbose and confirm the docker-desktop distributions show as running while Docker Desktop is open. If they are stopped or missing, Docker Desktop is set to a backend that is not up; open its settings and confirm the WSL 2 based engine option is enabled, then restart Docker Desktop.

**Restart cleanly when the pipe never appears.** Quit Docker Desktop completely from the tray, confirm no Docker Desktop process remains in Task Manager, relaunch it, and wait for the running status before any CLI command. Expected: docker version prints the Server section.

**Rule out a broken install last.** If a clean restart still creates no pipe and the app itself reports engine errors on startup, repair or reinstall Docker Desktop, then repeat steps 1 and 2. Success check: a fresh start reaches running status and the CLI connects.