From d87e2064a67955cfb4dfec85e80dcedb50642ed2 Mon Sep 17 00:00:00 2001
From: Anna-Li <70676128+v-lianna@users.noreply.github.com>
Date: Fri, 6 Aug 2021 09:55:53 +0800
Subject: [PATCH] Update credential-guard-known-issues.md

---
 .../credential-guard/credential-guard-known-issues.md         | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/windows/security/identity-protection/credential-guard/credential-guard-known-issues.md b/windows/security/identity-protection/credential-guard/credential-guard-known-issues.md
index 4aa8190429..310e1ceb6d 100644
--- a/windows/security/identity-protection/credential-guard/credential-guard-known-issues.md
+++ b/windows/security/identity-protection/credential-guard/credential-guard-known-issues.md
@@ -28,8 +28,8 @@ Windows Defender Credential Guard has certain application requirements. Windows
 The following known issue has been fixed in the [Cumulative Security Update for November 2017](https://support.microsoft.com/help/4051033):
 
 -  Scheduled tasks with domain user stored credentials fail to run when Credential Guard is enabled. The task fails and reports Event ID 104 with the following message: <br>
-   "Task Scheduler failed to log on ‘\Test’ . <br>
-   Failure occurred in ‘LogonUserExEx’ . <br>
+   "Task Scheduler failed to log on ‘\Test’. <br>
+   Failure occurred in ‘LogonUserExEx’. <br>
    User Action: Ensure the credentials for the task are correctly specified. <br>
    Additional Data: Error Value: 2147943726. 2147943726 : ERROR\_LOGON\_FAILURE (The user name or password is incorrect)."
 -  When enabling NTLM audit on the domain controller, an Event ID 8004 with an indecipherable username format is logged. For example: