Setting User and Machine Environment Variables on Windows with PowerShell

By default, environment variables in PowerShell are per-process. However, persisting environment variables at the user profile level, or globally at the operating system layer, is easy to do. Thanks to the System.Environment helper class in the Microsoft .NET Base Class Library (BCL), we can set per-process, per-user, or global system environment variables on the Windows platform.

The goal of this video is to demonstrate how you can manage these user and machine level environment variables from your PowerShell automation scripts.

Producer: Trevor Sullivan

#Microsoft #DevOps #PowerShell

[gaganchhabra]

Thanks for this helpful video, I searched online and wasted a lot of time reading articles before watching this amazing video.

[stefanspinu]

Dude, you made my day. You got no clue how much this video has helped me in understanding PowerShell and the .NET framework. Liked it, subscribed, enabled the bell icon. Keep up the good work. Cheers!

[saranyaprasath]

Great and crisp Explanation! Thank yiu

[tomparson]

Great teaching style. Keep these nice informational videos coming.

[vorkpalur]

Thanks for sharing the knowledge and great demonstration. Maybe try and catch would be nice to see, as I'm looking into sofware deployment using powershell. Just an idea for the nex videos. Merry Christmas to you!

[shidoan]

Ty a lot very useful.
What about if you want to add some lines to an user environment variable?

[techno]

Thanks, interesting video, I wanted to update path variable, but can only find get & set values. setx method still works weird. So for the update, I need to call get, then append new value & then set?