Update about rebootless removal of unsigned policies and Supplemental policies #11953
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Updated the described process for removal of App Control policies that are not signed. Also made it clear that supplemental policies, signed or not, can be removed just like any other unsigned policy.
Why
Beginning Windows 11 version 24H2, reboot is no longer required to remove unsigned policies.
Changes
Removed the statement that reboot is always mandatory. Instead added a note stating that reboot is no longer required if using Windows 11 24H2 or 2024 update, however previous versions still require a reboot to finalize the removal process.
There was no mention of supplemental policies in the document related to App Control policy removal so added some info and made the distinction between removing signed base and signed supplemental policies and how supplemental policies can be removed like unsigned policies without requiring the re-signing process.