Discrepancy in Powershell version reporting.
-
@JasGot Choco is returning the version the Choco has installed, it is not returning the version that is selected by default when you execute the PowerShell command. I guarantee you have multiple versions installed side by side.
-
@scottalanmiller said in Discrepancy in Powershell version reporting.:
@JasGot Choco is returning the version the Choco has installed, it is not returning the version that is selected by default when you execute the PowerShell command. I guarantee you have multiple versions installed side by side.
C:\Users\administrator.HT>powershell -Version 5 Cannot start Windows PowerShell version 5 because it is not installed. C:\Users\administrator.HT> -
-
Might be as simple as PS5 not being in the normal path. Check its absolute path.
-
@scottalanmiller said in Discrepancy in Powershell version reporting.:
Might be as simple as PS5 not being in the normal path. Check its absolute path.
That would have been too easy
There is only one powershell installation and it is at:
C:\Windows\System32\WindowsPowerShell\v1.0\Which is right where it belongs. I'm running the stand alone gui installer now to see if that works.
-
Do you have WMF 5.1 installed?
-
@black3dynamite said in Discrepancy in Powershell version reporting.:
Do you have WMF 5.1 installed?
That's the gui installer I'm going to install to see if it works. If it does, I should then be able to install it again with -force, or use Chocolaty with the upgrade option and see it go smoothly.
-
what version of windows are you on?
-
You need to reboot however so it shows the correct powershell version after the install. Did you do that?
-
@Dashrender said in Discrepancy in Powershell version reporting.:
what version of windows are you on?
Server 2012
-
@dbeato said in Discrepancy in Powershell version reporting.:
You need to reboot however so it shows the correct powershell version after the install. Did you do that?
Sadly. Several times.
Busy weekend. I'll have to get back to this next week.
The ignition for this was the desire to start using Chocolaty. It has been one obstacle after another to get it off the ground. And know this, my goal is to get Powershell updated, .Net updated, and Chocolaty installed all from scripts within a backstage connection through SC.
So there are tons of scenarios that have to be worked out, and handled, all through scripting. :anguished_face:
-
@JasGot chocolatey is the easy one.
-
What version of .net is installed on the server?
I'm failing to remember which version of Powershell had a hard but silent requirement for a particular version of .net.
If memory serves it would install successfully (no errors) but would actually fail to install if the correct ver of .net was not already installed.
