Which PowerShell session should you open?
Check whether the guide calls for PowerShell 7 or Windows PowerShell 5.1. PowerShell 7 can run alongside 5.1 on Windows and uses the pwsh executable. In a known local PowerShell session, read $PSVersionTable.PSVersion to confirm what is running. Some Windows-specific commands and modules may behave differently or be unavailable on another operating system.
Where will the next command act?
In a known local PowerShell tab, Get-Location reports the current location. Compare it to the project folder you expected. PowerShell can also browse other kinds of locations, such as the Windows registry, so a location name is not always a folder. Its own commands can pass structured results to one another, such as a list of files with names and sizes.
What should you keep when you change computers?
PowerShell 7 is open source. Check Microsoft’s supported versions and the operating system your script expects. Keep your script files, a list of the modules they require and the settings you need. A profile is a script that runs when a session starts. Its path can depend on the host app and your user account. Check $PROFILE in that host and read the file before copying any settings.
How would you catch a version or folder mix-up?
Imagine a guide expects PowerShell 7 in the local sample-shop project. On paper, write version 5.1 and sample-notes as the two reported values. Either mismatch is a reason to stop. Write down the version and folder you expect before moving to the guide’s next command. No remote session or real project is needed for this example.