Install fails if PATH variable is > 1024 characters. about microsoft-authentication-cli HOT 6 CLOSED

More precisely, I don't think that can have an effect on processes that aren't PowerShell and we also have users launching azureauth entirely outside PowerShell. Again, would love to be wrong though.

from microsoft-authentication-cli.

Thanks for the report, @seanadams9. We'll look into this right away.

from microsoft-authentication-cli.

FYI, using setx was a deliberate choice because of these properties.

I'm not sure we were aware of or accounted for the truncation at the time...

from microsoft-authentication-cli.

For further clarity, the desired property is the broadcast of the WM_SETTINGCHANGE message. I think that we can set the $PATH through direct registry manipulation ourselves and then broadcast that message ourselves, but it's more complicated in PowerShell than just using setx. We'll have to dig into how to do that... 😅

from microsoft-authentication-cli.

Can you not just use powershell via:

[Environment]::SetEnvironmentVariable('PATH',$newPath, [System.EnvironmentVariableTarget]::User)

from microsoft-authentication-cli.

I might be mistaken, but I don't believe that will propagate the environment variable change to new processes, just the current PowerShell or Windows Terminal window. I would be happy to be wrong though.

from microsoft-authentication-cli.