Timeline for Set PSModulePath Environment Variable with PowerShell in Windows 10
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 4 at 16:13 | answer | added | theking2 | timeline score: 0 | |
| Mar 31, 2023 at 10:27 | answer | added | Xavier Plantefève | timeline score: 1 | |
| Jul 18, 2018 at 4:38 | vote | accept | EllipticalInitial | ||
| Jul 17, 2018 at 23:13 | answer | added | Vomit IT - Chunky Mess Style | timeline score: 3 | |
| Jul 17, 2018 at 17:06 | comment | added | EllipticalInitial | @PimpJuiceIT, just open System Properties\Advanced\Environment Variables and take a look in there yourself. If you use the actual UI, or even check the corresponding registry entry, you can see the percentage signs in the text string. The problem is that I cannot get the string with the percentage signs using PowerShell for some reason; they always get converted to hard-coded paths and I don't know why. | |
| Jul 16, 2018 at 23:32 | answer | added | postanote | timeline score: 0 | |
| Jul 16, 2018 at 19:55 | comment | added | Ramhound | "C:\Users\Username\Documents\WindowsPowerShell\Modules" - This would only exist in the user's PATH variable. It appears you are modifying the user's PATH variable instead of the system's PATH variable hence the difference. This question has an answer that explains the differences. | |
| Jul 16, 2018 at 19:49 | history | asked | EllipticalInitial | CC BY-SA 4.0 |