From fbf779b03cf5974156ff8de66892f4d744382c30 Mon Sep 17 00:00:00 2001 From: Brian Lich Date: Wed, 20 Jul 2016 12:24:31 -0700 Subject: [PATCH] task# 7619482 --- windows/keep-secure/security-considerations-for-applocker.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/windows/keep-secure/security-considerations-for-applocker.md b/windows/keep-secure/security-considerations-for-applocker.md index 0fc2aa0bc5..c959f1bfd0 100644 --- a/windows/keep-secure/security-considerations-for-applocker.md +++ b/windows/keep-secure/security-considerations-for-applocker.md @@ -41,7 +41,7 @@ AppLocker rules either allow or prevent an application from launching. AppLocker >**Note:**  Two flags that illustrate this condition are `SANDBOX_INERT`, which can be passed to `CreateRestrictedToken`, and `LOAD_IGNORE_CODE_AUTHZ_LEVEL`, which can be passed to `LoadLibraryEx`. Both of these flags signal AppLocker to circumvent the rules and allow a child .exe or .dll to be loaded. -You can block the Windows Subsystem for Linux by blocking LxssManager.dll +You can block the Windows Subsystem for Linux by blocking LxssManager.dll.   ## Related topics