From 5379d9c00a94ec43a59b0a86b6259ff254188973 Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Mon, 1 Jun 2020 14:35:56 -0700 Subject: [PATCH] tweaks --- windows/deployment/upgrade/setupdiag.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index 5b4b523f2f..ac5f6cd93a 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -37,7 +37,7 @@ SetupDiag works by examining Windows Setup log files. It attempts to parse these ## SetupDiag in Windows 10, version 2004 and later -With the release of Windows 10, version 2004, SetupDiag is included with Windows Setup. +With the release of Windows 10, version 2004, SetupDiag is included with [Windows Setup](https://docs.microsoft.com/windows-hardware/manufacture/desktop/deployment-troubleshooting-and-log-files#windows-setup-scenario). During the upgrade process, Windows Setup will extract all its sources files to the **%SystemDrive%$Windows.~bt\Sources** directory. With Windows 10, version 2004 and later, **setupdiag.exe** is also installed to this directory. If there is an issue with the upgrade, SetupDiag will automatically run to determine the cause of the failure.