Problem
Split-PathEntries (Windows-Path-Repair-Full.ps1, ~line 44) splits the raw PATH value on every ;. Windows PATH permits quoted entries such as "C:\Program Files;odd". If such an entry exists, the script splits it into two invalid fragments and would persist that corruption on -Apply.
Proposed fix
Rare edge case, so a conservative guard is enough: if the raw Machine or User PATH value contains a double-quote character, refuse to proceed (or at minimum warn loudly and require an explicit override switch), consistent with the tool's preview-and-approve philosophy. A full quoted-segment parser is optional follow-up.
Acceptance criteria
- A PATH value containing
" triggers the guard before any plan is computed for that scope.
- Test covering the guard (both rejection and, if an override is added, the override path).
- README note in the safety section.
Problem
Split-PathEntries(Windows-Path-Repair-Full.ps1, ~line 44) splits the raw PATH value on every;. Windows PATH permits quoted entries such as"C:\Program Files;odd". If such an entry exists, the script splits it into two invalid fragments and would persist that corruption on-Apply.Proposed fix
Rare edge case, so a conservative guard is enough: if the raw Machine or User PATH value contains a double-quote character, refuse to proceed (or at minimum warn loudly and require an explicit override switch), consistent with the tool's preview-and-approve philosophy. A full quoted-segment parser is optional follow-up.
Acceptance criteria
"triggers the guard before any plan is computed for that scope.