Forum Discussion
Problem with Windows PowerShell
- Dec 29, 2023
With respect to the "v1.0" shown in the path to Windows PowerShell, it has always lived in that directory, has never changed from it, and likely never will.
Conversely, PowerShell (not Windows PowerShell) can be installed pretty much anywhere you like - if you're using the MSI-based installation. It just happens to default to %ProgramFiles%.
You can exert a limited amount of control over Windows PowerShell logging by using the variables listed in the following article:
You cannot specifically target a particular event ID though.
Cheers,
Lain
Windows PowerShell appears to be version 5.1, but I don't understand why the description of the event in the photo shows me version 1.0.
and is it not possible to eliminate that id 300 error described in the first post?
Thank you
- LainRobertsonDec 29, 2023Silver Contributor
With respect to the "v1.0" shown in the path to Windows PowerShell, it has always lived in that directory, has never changed from it, and likely never will.
Conversely, PowerShell (not Windows PowerShell) can be installed pretty much anywhere you like - if you're using the MSI-based installation. It just happens to default to %ProgramFiles%.
You can exert a limited amount of control over Windows PowerShell logging by using the variables listed in the following article:
You cannot specifically target a particular event ID though.
Cheers,
Lain
- Dec 29, 2023The installation folder never changed from the system32 folder from version 1 until 6 or 7 when it was moved to program files.