From 958c96a5f114a5c722f31fccdd1f70484d394d03 Mon Sep 17 00:00:00 2001
From: NathanJepson <61210670+NathanJepson@users.noreply.github.com>
Date: Wed, 5 Nov 2025 14:42:43 -0700
Subject: [PATCH] Update Set-CIPolicySetting.md

Fix typo in example 1.

The reason is that supplying "$True" actually results in a typo in the XML file where "True" is capitalized -- this doesn't fit the XML specifications of code integrity policies, and actually leads to an error. (See https://github.com/PowerShell/PowerShell/issues/21286 for a discussion on this).

This change makes example 1 conform to other Microsoft documentation which uses a correct example of this cmdlet, see:
https://learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/design/allow-com-object-registration-in-appcontrol-policy
---
 docset/winserver2025-ps/ConfigCI/Set-CIPolicySetting.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docset/winserver2025-ps/ConfigCI/Set-CIPolicySetting.md b/docset/winserver2025-ps/ConfigCI/Set-CIPolicySetting.md
index 570e9b46ee..01cbd36e2d 100644
--- a/docset/winserver2025-ps/ConfigCI/Set-CIPolicySetting.md
+++ b/docset/winserver2025-ps/ConfigCI/Set-CIPolicySetting.md
@@ -36,7 +36,7 @@ Secure Settings are queried by Windows APIs to set security behaviors.
 
 ### Example 1: Set the Code Integrity policy
 ```powershell
-Set-CIPolicySetting -FilePath C:\Policies\WDAC_policy.xml -Key "{12345678-9abc-def0-1234-56789abcdef0}" -Provider WSH -Value $True -ValueName EnterpriseDefinedClsId -ValueType Boolean
+Set-CIPolicySetting -FilePath C:\Policies\WDAC_policy.xml -Key "{12345678-9abc-def0-1234-56789abcdef0}" -Provider WSH -Value true -ValueName EnterpriseDefinedClsId -ValueType Boolean
 ```
 
 This command sets the Code Integrity policy to allow for the specified **Provider**, **Key** and **ValueName**.