{"version":"2.1.196","anchor":"windows-sandbox-acl-per-process-ownership","canonical_anchor":"windows-sandbox-acl-per-process-ownership","heading":"Windows Sandbox ACL \u2014 Per-Process Ownership","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196\/e\/windows-sandbox-acl-per-process-ownership","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.196","markdown":"### Windows Sandbox ACL \u2014 Per-Process Ownership\n\nThe Windows file-deny ACL stamp now accepts a `--holder-pid` flag that associates the stamp with a specific process ID. When the holder process exits, the ACL can be cleaned up rather than persisting for the entire session group.\n\n**Details**\n\n- `gta()` (ACL stamp) and `poo()` (ACL restore) both pass `--holder-pid <pid>` to the `srt-win acl` helper.\n- Changing the Windows sandbox group still requires `reset()` and `re-initialize()`.\n- If the file-deny set changes mid-session, a warning is logged noting that the change cannot be applied without a reset.\n\n**Evidence**\n\nNew flag (search for `\"--holder-pid\"`)"}