From 3daf38674ff3d5a2cb43ae12b82dfc7c82e447ea Mon Sep 17 00:00:00 2001 From: Greg Lindsay Date: Wed, 11 Apr 2018 17:47:55 +0000 Subject: [PATCH] Merged PR 7089: Typo Typo --- windows/deployment/upgrade/setupdiag.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/windows/deployment/upgrade/setupdiag.md b/windows/deployment/upgrade/setupdiag.md index a460f3c8b5..32859c06fe 100644 --- a/windows/deployment/upgrade/setupdiag.md +++ b/windows/deployment/upgrade/setupdiag.md @@ -7,7 +7,7 @@ ms.mktglfcycl: deploy ms.sitesec: library ms.pagetype: deploy author: greg-lindsay -ms.date: 03/30/2018 +ms.date: 04/11/2018 ms.localizationpriority: high --- @@ -103,7 +103,7 @@ SetupDiag.exe /Output:C:\SetupDiag\Dumpdebug.log /Mode:Offline /LogsPath:D:\Dump ## Known issues -1. Some rules can take a long time to process if the log files involved as large. +1. Some rules can take a long time to process if the log files involved are large. 2. SetupDiag only outputs data in a text format. If another format is desired, please provide this [feedback](#feedback). 3. If the failing computer is opted into the Insider program and getting regular pre-release updates, or an update is already pending on the computer when SetupDiag is run, it can encounter problems trying to open these log files. This will likely cause a failure to determine a root cause. In this case, try gathering the log files and running SetupDiag in offline mode.