Set-ProcessMitigation: -Remove does not remove path-scoped entries created with a full -Name path
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- powershell
- Domain
- documentation
Research direction
Open docset/winserver2025-ps/ProcessMitigations/Set-ProcessMitigation.md and locate the -Name parameter description and the -Remove examples (e.g. Set-Processmitigation -Name test.exe -Remove -Disable DEP). Add a note stating that when -Name is a full path, the entry is path-scoped and must be deleted under HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\<name>. Done means the same note appears in the 2025, 2022, and 2019 docset copies of the page and the Markdown builds without lint errors.
Written by the indexing model from the issue text.
Description
Page: docset/winserver2025-ps/ProcessMitigations/Set-ProcessMitigation.md (same text in the 2022 and 2019 docsets); also https://learn.microsoft.com/defender-endpoint/enable-exploit-protection
The page documents -Name as <ProcessPathAndFilename.exe> and shows removal as Set-Processmitigation -Name test.exe -Remove -Disable DEP. When -Name is a full path, the cmdlet creates a path-scoped entry (UseFilter=1 on the IFEO key plus a subkey with FilterFullPath), but none of the documented removal forms delete it:
-Removealone: error "Invalid input parameters".-Remove -Disable <mitigation>: succeeds silently, entry unchanged.
Reproduction (elevated PowerShell 7.6 or Windows PowerShell 5.1, Windows 11 Pro 26300, ProcessMitigations module 1.0.12):
Set-ProcessMitigation -Name C:\test\app.exe -Disable ForceRelocateImages
Get-ProcessMitigation -Name C:\test\app.exe # ForceRelocateImages: OFF; registry has UseFilter + FilterFullPath subkey
Set-ProcessMitigation -Name C:\test\app.exe -Remove # Invalid input parameters
Set-ProcessMitigation -Name C:\test\app.exe -Remove -Disable ForceRelocateImages # no error, entry still present
Get-ProcessMitigation -Name C:\test\app.exe # still OFF
-Reset and -Force off also fail with "Invalid input parameters"; -Remove -Enable ForceRelocateImages and a bare-name -Name app.exe -Remove -Disable ForceRelocateImages succeed without removing the entry. Deleting the subkey under the IFEO key by hand is the only way to undo the exemption.
Either the cmdlet should remove such entries, or the page should state that path-scoped entries must be removed from HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\<name> directly.
Also filed in feedback hub: feedback-hub:?contextid=871&feedbackid=c3ac56ef-2214-40a3-96d2-cbed787ec578&form=1&src=1
- Dominant language
- Dockerfile
- Stars
- 510
- Forks
- 643
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 8
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from MicrosoftDocs/windows-powershell-docs
-
issue-doc-bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
MicrosoftDocs/windows-powershell-docs#4112 ·
Maintainers usually reply within 1 day
-
issue-doc-bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
MicrosoftDocs/windows-powershell-docs#3861 · 1 comment ·
Maintainers usually reply within 1 day
-
issue-doc-bug needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 55/100
MicrosoftDocs/windows-powershell-docs#4153 ·
Maintainers usually reply within 1 day
-
issue-doc-bug needs-triage
Difficulty 4/5 3-5 days Newbie friendliness 45/100
MicrosoftDocs/windows-powershell-docs#4122 ·
Maintainers usually reply within 1 day
-
issue-doc-bug needs-triage
Difficulty 3/5 1-2 days Newbie friendliness 48/100
MicrosoftDocs/windows-powershell-docs#4114 ·
Maintainers usually reply within 1 day
All issues in MicrosoftDocs/windows-powershell-docs
Similar issues
-
area:agent-sdk area:docs documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
anthropics/claude-code#110914 ·
-
specification
Difficulty 1/5 Under an hour Newbie friendliness 78/100
WICG/webmonetization#813 ·
Maintainers usually reply within 3 days
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Polish READMEOpendocumentation
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Doc: Remove quotes and backticks around RFC objectsPossibly taken @Tirth00000 claimed this today. Opendoc good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
collective/icalendar#2146 · 1 comment ·