-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows Installer breaks PATH variable #11416
Comments
@jwhonce PTAL |
The clean up issue is being tracked here: #11089 We are waiting on PR to wixl to support clean up. @baude @ashley-cui I seem to remember the quote issue being addressed or at least discussed before. Do you have any input? |
One non-obvious symptom of this issue is that, after installing Podman, the CLI can only be called from the traditional Windows Command Prompt (CMD) and not from PowerShell. Apparently CMD will parse PATH with the invalid trailing quote, but PowerShell will not. So PowerShell users will just get the usual error message indicating a missing command:
Not that this changes anything about the underlying problem, but it might help to direct PowerShell users' searches to this issue where the fix is described. |
Just for completeness: To fix: |
I should have confirmed that dialog box when I had the chance ... that's easier than using the registry 💯 |
A friendly reminder that this issue had no activity for 30 days. |
The latest installer is still adding a single double-quote to the Path... |
A friendly reminder that this issue had no activity for 30 days. |
Is this fixed in podman 3.4.1 |
@rhatdan Sorry, I completely missed this... Just tested: Removed all previous versions, made sure my env vars are clean. Still a lost double-quote after 3.4.1... |
28 days ago, I nagged the PR to MSI, but still no movement that I can see. |
/shrug |
Go add a further whine to #11089 |
…ote is not escaped Fixes containers#11416 [NO NEW TESTS NEEDED] Signed-off-by: Jason Greene <[email protected]>
Fixes #11416 - Trailing quote on PATH added by Windows MSI
…ote is not escaped Fixes containers#11416 [NO NEW TESTS NEEDED] Signed-off-by: Jason Greene <[email protected]>
Your Windows Installer is breaking the users environment by adding a single
"
at the end of the path-variable.Can only be reverted via registry editor:
Windows UI for env vars doesn't show it anymore.
Also, as a side note: It doesn't clean up the env var when uninstalling.
The text was updated successfully, but these errors were encountered: