PowerShell Message

Topic

New Reply

I am running Win 10 1909 64-bit, and I am trying to use PowerShell to run a command to diagnose an EventLog entry.  PowerShell gives me the message

“Try the new cross-platform PowerShell https://aka.ms/pscore6 ”

and it will not accept any commands.   I looked at a number of help sites, and the response was to install  the latest PowerShell.  I installed PowerShell 7.0.2 from the x64 .msi files, and it installed in Program FilesPowerShell. not in Program FilesWindowsPowerShell .  When I run pwsh,.exe from there, I get the same message.  Do others see this behavior?

 

Reply | Quote

Replies

What commands were you trying to run?

cheers, Paul

Reply | Quote

The command that I was trying to run is immaterial here.  When I open PowerShell 7.0.2, I get what I posted in the screenshot above.  After PowerShell has displayed the “nag” message (which should not apply for PowerShell 7), the PowerShell window will not accept any commands.  Cntl-C does not close.  I have to cancel via Task Manager.  I opened WindowsPowerShell, and I got the same “nag”, and the windows does not accept any commands.

Reply | Quote

[RetiredGeek]

Windows PowerShell 5.1is installed in Program Files\WindowsPowerShell. PowerShell Core, cross platform PowerShell versions 6+, are installed at Program Files\Powershell. They are mutually exclusive and both can coexist on the same machine. If you are working in Windows exclusively, I’d recommend working with Windows PowerShell.

HTH 😎

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

• This reply was modified 4 years, 9 months ago by RetiredGeek.

Reply | Quote

Do you have any versions PowerShell listed in Programs and Features? What happens if you remove all but the oldest?

cheers, Paul

Reply | Quote

I am not sure of the Win 10 terminology.  In “Apps & features” I see “Power Shell 7 x64”, installed yesterday.  That list does not show WindowsPowerShell.  Control Panel “Programs and Features” has “Power Shell 7 x64” but not Windows Power Shell.  I have no idea why there are two lists, and I did not compare them.  And I am not sure what is the Windows 10 definition of “app”, as opposed to “software”.  WindowsPowerShell came with the 1909 version I installed in March.

1 user thanked author for this post.

Elly

Reply | Quote

[RetiredGeek]

Windows Powershell is a builtin part of the OS and therefor not listed in Apps & Programs.

PowerShell Core (6.0+) needs to be installed and therefor shows up in Apps & Programs.

PowerShell Core is started via PWSH.exe, it has only a command window interface. If you want an Integrated Development environment you need to download the free Visual Studio Code.

Windows Powershell is started via one of 4 commands:

• %windir%\system32\WindowsPowerShell\v1.0\PowerShell.exe – 64 bit  command window. (32 bit on Windows 32 bit).
• %windir%\SysWOW64\WindowsPowerShell\v1.0\powershell.exe – 32 bit command window on 64 bit Windows.
• %windir%\system32\WindowsPowerShell\v1.0\PowerShell_ISE.exe – 64 bit PowerShell ISE – Integrated Development environment on Windows 64 bit (32 bit on Windows 32 bit).
• %windir%\SysWOW64\WindowsPowerShell\v1.0\powershell_ise.exe – 32 bit PowerShell ISE – Integrated Development environment.

HTH

 

May the Forces of good computing be with you!

RG

PowerShell & VBA Rule!
Computer Specs

• This reply was modified 4 years, 9 months ago by RetiredGeek.

Reply | Quote

I did a reboot because I needed to update my %PATH% environmental variable.  After the reboot, both Power Shells worked fine.  So, this problem is solved.  Is there a way to add a directory to %PATH% without a reboot?  Maybe a SET command via a CMD prompt?

1 user thanked author for this post.

Elly

Reply | Quote