From cc98a62c2a8b84fd688b116f009f9cc7e31d1ba3 Mon Sep 17 00:00:00 2001 From: Baard Hermansen Date: Fri, 27 Sep 2019 17:33:48 +0200 Subject: [PATCH] Update dll-rules-in-applocker.md Updated markdown. --- .../applocker/dll-rules-in-applocker.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/windows/security/threat-protection/windows-defender-application-control/applocker/dll-rules-in-applocker.md b/windows/security/threat-protection/windows-defender-application-control/applocker/dll-rules-in-applocker.md index ec45f1d75e..be5c338598 100644 --- a/windows/security/threat-protection/windows-defender-application-control/applocker/dll-rules-in-applocker.md +++ b/windows/security/threat-protection/windows-defender-application-control/applocker/dll-rules-in-applocker.md @@ -41,9 +41,11 @@ The following table lists the default rules that are available for the DLL rule | Allow all users to run DLLs in the Program Files folder | (Default Rule) All DLLs located in the Program Files folder| | Everyone | Path: %programfiles%\*| -> **Important:** If you use DLL rules, a DLL allow rule has to be created for each DLL that is used by all of the allowed apps -> -> **Caution:** When DLL rules are used, AppLocker must check each DLL that an app loads. Therefore, users may experience a reduction in performance if DLL rules are used. +> [!IMPORTANT] +> If you use DLL rules, a DLL allow rule has to be created for each DLL that is used by all of the allowed apps + +> [!CAUTION] +> When DLL rules are used, AppLocker must check each DLL that an app loads. Therefore, users may experience a reduction in performance if DLL rules are used. ## Related topics