Forum Discussion
Problem with Windows PowerShell
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
You're right in that their screenshot is of Windows PowerShell and not PowerShell - you can tell from the tab title and welcome message where it says "Windows PowerShell".
Conversely, PowerShell simply says "PowerShell", and not "Windows PowerShell. PowerShell also dumps the version in the welcome message where Windows PowerShell does not.
Here's a side-by-side example showing the title bar differences in Windows Terminal:
You can't compare Windows PowerShell version numbers to PowerShell version numbers.
For Windows PowerShell, if you've been applying the monthly Windows operating system updates (speaking for Windows 10, at least, as I don't run Windows 11) then Windows PowerShell should already be up-to-date.
For PowerShell, if you're running 7.4.0 then you are on the latest stable branch and there is nothing left to do. Just make sure that within Windows Terminal, you are starting a new PowerShell session and not a Windows PowerShell session.
Cheers,
Lain
