From c065d96bc8124d45a7cbb2e3b97dbdfe5ed554fe Mon Sep 17 00:00:00 2001 From: Allie Sadler <102604716+aevesdocker@users.noreply.github.com> Date: Wed, 19 Jul 2023 15:13:34 +0100 Subject: [PATCH] ENGDOCS-1520 (#17762) Co-authored-by: aevesdocker --- desktop/troubleshoot/overview.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/desktop/troubleshoot/overview.md b/desktop/troubleshoot/overview.md index 6f786bbbb5..3b815126ce 100644 --- a/desktop/troubleshoot/overview.md +++ b/desktop/troubleshoot/overview.md @@ -100,7 +100,7 @@ Docker Desktop cannot start. 2. Create and upload the diagnostics ID. Run: ```console - $ gather -upload + $ "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" gather -upload ``` After the diagnostics have finished, the terminal displays your diagnostics ID and the path to the diagnostics file. The diagnostics ID is composed of your user ID and a timestamp. For example `BE9AFAAF-F68B-41D0-9D12-84760E6B8740/20190905152051`. @@ -184,7 +184,7 @@ Docker Desktop contains a self-diagnose tool which can help you identify some co 2. Run the self-diagnose tool: ```console - $ check + $ "C:\Program Files\Docker\Docker\resources\com.docker.diagnose.exe" check ``` The tool runs a suite of checks and displays **PASS** or **FAIL** next to each check. If there are any failures, it highlights the most relevant at the end of the report.