diff --git a/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md b/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md
index 8522325f19..425b3dca9e 100644
--- a/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md
+++ b/windows/security/threat-protection/windows-defender-application-control/microsoft-recommended-block-rules.md
@@ -76,7 +76,13 @@ These modules cannot be blocked by name or version, and therefore must be blocke
For October 2017, we are announcing an update to system.management.automation.dll in which we are revoking older versions by hash values, instead of version rules.
-Microsoft recommends that you block the following Microsoft-signed applications and PowerShell files by merging the following policy into your existing policy to add these deny rules using the Merge-CIPolicy cmdlet:
+Microsoft recommends that you block the following Microsoft-signed applications and PowerShell files by merging the following policy into your existing policy to add these deny rules using the Merge-CIPolicy cmdlet. Beginning with the March 2019 quality update, each Windows release requires blocking diffferent version of the following files:
+
+- msxml3.dll
+- msxml6.dll
+- jscript9.dll
+
+In the comments of the following script, find the Windows release that you plan to use the policy for and remove the other file versions.
```xml
@@ -137,7 +143,35 @@ Microsoft recommends that you block the following Microsoft-signed applications
-
+
+
+
+
+
+
+
+ -->
+
+
+
+ -->
+
+
+
+ -->
+
+
+
+ -->
+
+
+
+ -->
@@ -842,8 +876,11 @@ Microsoft recommends that you block the following Microsoft-signed applications
-
-
+
+
+
+
+
@@ -1457,7 +1494,7 @@ Microsoft recommends that you block the following Microsoft-signed applications
0
-
+
```