From 69798288c6fd4d32f6a025dad0105c8c9089c031 Mon Sep 17 00:00:00 2001 From: Aaron Czechowski Date: Fri, 30 Jun 2023 11:25:19 -0700 Subject: [PATCH] fix style issues --- .../required-windows-11-diagnostic-events-and-fields.md | 4 ++-- ...dows-defender-application-control-policies-using-intune.md | 2 +- .../disable-windows-defender-application-control-policies.md | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/windows/privacy/required-windows-11-diagnostic-events-and-fields.md b/windows/privacy/required-windows-11-diagnostic-events-and-fields.md index a2f855b64e..439810cc47 100644 --- a/windows/privacy/required-windows-11-diagnostic-events-and-fields.md +++ b/windows/privacy/required-windows-11-diagnostic-events-and-fields.md @@ -1983,7 +1983,7 @@ The following fields are available: ### Microsoft.Windows.Security.CodeIntegrity.State.Current -This event indicates the overall CodeIntegrity Policy state and count of policies, fired on reboot and when policy changes rebootlessly. The data collected with this event is used to help keep Windows secure. +This event indicates the overall CodeIntegrity Policy state and count of policies, which occur when the device restarts and when policy changes without a restart. The data collected with this event is used to help keep Windows secure. The following fields are available: @@ -2006,7 +2006,7 @@ The following fields are available: ### Microsoft.Windows.Security.CodeIntegrity.State.PolicyDetails -This individual policy state event fires once per policy on reboot and whenever any policy change occurs rebootlessly. The data collected with this event is used to help keep Windows secure. +This individual policy state event occurs once per policy when the device restarts and whenever any policy change occurs without a restart. The data collected with this event is used to help keep Windows secure. The following fields are available: diff --git a/windows/security/threat-protection/windows-defender-application-control/deployment/deploy-windows-defender-application-control-policies-using-intune.md b/windows/security/threat-protection/windows-defender-application-control/deployment/deploy-windows-defender-application-control-policies-using-intune.md index 83e3847164..e4eec68d0f 100644 --- a/windows/security/threat-protection/windows-defender-application-control/deployment/deploy-windows-defender-application-control-policies-using-intune.md +++ b/windows/security/threat-protection/windows-defender-application-control/deployment/deploy-windows-defender-application-control-policies-using-intune.md @@ -43,7 +43,7 @@ Intune's built-in Windows Defender Application Control support allows you to con > Intune's built-in policies use the pre-1903 single-policy format version of the DefaultWindows policy. You can use Intune's custom OMA-URI feature to deploy your own multiple-policy format WDAC policies and leverage features available on Windows 10 1903+ or Windows 11 as described later in this topic. > [!NOTE] -> Intune currently uses the AppLocker CSP to deploy its built-in policies. The AppLocker CSP will always request a reboot when applying WDAC policies. You can use Intune's custom OMA-URI feature with the ApplicationControl CSP to deploy your own WDAC policies rebootlessly. +> Intune currently uses the AppLocker CSP to deploy its built-in policies. The AppLocker CSP always requests a device restart when it applies WDAC policies. You can use Intune's custom OMA-URI feature with the ApplicationControl CSP to deploy your own WDAC policies without a restart. To use Intune's built-in WDAC policies, configure [Endpoint Protection for Windows 10 (and later)](/mem/intune/protect/endpoint-protection-windows-10?toc=/intune/configuration/toc.json&bc=/intune/configuration/breadcrumb/toc.json). diff --git a/windows/security/threat-protection/windows-defender-application-control/disable-windows-defender-application-control-policies.md b/windows/security/threat-protection/windows-defender-application-control/disable-windows-defender-application-control-policies.md index be973cf600..11ea39bbe9 100644 --- a/windows/security/threat-protection/windows-defender-application-control/disable-windows-defender-application-control-policies.md +++ b/windows/security/threat-protection/windows-defender-application-control/disable-windows-defender-application-control-policies.md @@ -55,7 +55,7 @@ To make a policy effectively inactive before removing it, you can first replace 5. If applicable, remove option **0 Enabled:UMCI** to convert the policy to kernel mode only. > [!IMPORTANT] -> After a policy has been removed, you must restart the computer for it to take effect. You can't remove WDAC policies rebootlessly. +> After you remove a policy, restart the computer for it to take effect. You can't remove WDAC policies without restarting the device. ### Remove WDAC policies using CiTool.exe