Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deprecate PowerShell 2.0 Support #163

Closed
4 tasks done
dahlbyk opened this issue Nov 13, 2014 · 24 comments · Fixed by #186
Closed
4 tasks done

Deprecate PowerShell 2.0 Support #163

dahlbyk opened this issue Nov 13, 2014 · 24 comments · Fixed by #186

Comments

@dahlbyk
Copy link
Owner

dahlbyk commented Nov 13, 2014

Dropping support for PowerShell 2.0 means fewer workarounds like #162. Before we do so, it would be good to warn those using 2.0 about the change:

  • Add warning mentioning that PowerShell 2.0 will no longer be supported.
  • Provide link to PowerShell 3.0 download.
  • Provide link to this issue for those wishing to express dissent.
  • Provide a setting to disable the warning?
theaquamarine added a commit to theaquamarine/posh-git that referenced this issue Apr 14, 2015
Allow Powershell 2 support deprecation warning to be suppressed by
importing the module with a true value as an argument.

The ability to pass arguments through Import-Module is pretty limited,
accepting only positional arguments, but it still seems a preferable
option to environment variables or asking users to modify posh-git
directly.

Closes dahlbyk#163
theaquamarine added a commit to theaquamarine/posh-git that referenced this issue May 14, 2015
Allow Powershell 2 support deprecation warning to be suppressed by
importing the module with a true value as an argument.

The ability to pass arguments through Import-Module is pretty limited,
accepting only positional arguments, but it still seems a preferable
option to environment variables or asking users to modify posh-git
directly.

Closes dahlbyk#163
@Neon22
Copy link

Neon22 commented May 9, 2016

just getting this warning now. but the link suggested:

This download includes Windows PowerShell 3.0, WMI, WinRM, Management OData IIS Extension, and Server Manager CIM Provider
All of which seem essential to make powershell work. but are labelled as incompatible with the Configuration Manager, and System Center Virtual Machine Manager and some others.

Does not donwloading this mean I can't use github for windows, or github anymore ?

@dahlbyk
Copy link
Owner Author

dahlbyk commented May 9, 2016

@Neon22 what version of Windows Server are you using? You might try jumping straight to PowerShell 4.0 or PowerShell 5.0?

@Neon22
Copy link

Neon22 commented May 9, 2016

oh... completely unaware - good solution - thanks...
I'd suggest you change message to recommend 5 instead of 3

dahlbyk added a commit that referenced this issue May 9, 2016
@dahlbyk
Copy link
Owner Author

dahlbyk commented May 9, 2016

Done: 83caec1

@ghost
Copy link

ghost commented May 15, 2016

Hrm... well, I just now started getting the "get version 3.0" warning yesterday. I'm still using windows 7 and those links to get the newer powershell just take me to an "upgrade to windows 10" link, which I don't really want to do. Any suggestions aside from telling me to upgrade to windows 10? Would it hurt anything to just suppress the warning for now?

@coridrew
Copy link
Collaborator

fwiw, I have to dev on an x86 win7 machine for a current client, and was able to successfully upgrade Powershell on that dinosaur :)

@ghost
Copy link

ghost commented May 15, 2016

so how do I do that? Links to instructions would be wonderful.... going to google it, but hopefully maybe you'll have some direction for me as well.

@ghost
Copy link

ghost commented May 15, 2016

sigh Never mind and thanks for the replies. I just realized the link only has an advert for windows 10... not that I have to install it.... hehe. Sorry all!

@sanjanat
Copy link

ps

Which one shall I select ?

@dahlbyk
Copy link
Owner Author

dahlbyk commented Jun 10, 2016

Which one shall I select ?

Which OS and architecture (32- or 64-bit) do you have?

@SnailSword
Copy link

Where is the setting to disable the warning

@theaquamarine
Copy link
Collaborator

$NoVersionWarn, https://github.com/dahlbyk/posh-git/blob/master/posh-git.psm1

On 10 Jun 2016, at 18:56, SnailSword [email protected] wrote:

Where is the setting to disable the warning


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@lZzozZl
Copy link

lZzozZl commented Jul 28, 2016

dahlbyk commented on Jun 10
Which one shall I select ?
Which OS and architecture (32- or 64-bit) do you have?

i have windows 7 ultimate 64-bit

@dahlbyk
Copy link
Owner Author

dahlbyk commented Jul 28, 2016

i have windows 7 ultimate 64-bit

Vista = Windows6.0
Win7 = Windows6.1

x86 = 32-bit
x64 = 64-bit

So for Win7 64-bit you want Windows6.1-KB2506143-x64.msu.

@lZzozZl
Copy link

lZzozZl commented Jul 28, 2016

ty

@chrisdemetriad
Copy link

I am on Windows Server 2008 R2. Will probably look for something else then.

@theaquamarine
Copy link
Collaborator

2008 R2 is Windows6.1, so would use Windows6.1-KB2506143-x64.msu
2008 is Windows6.0.

@rainecyt
Copy link

PowerShell 4.0/ PowerShell 5.0/ PowerShell 3.0 are not fit my PC ,can not updata ,what I can do next

@dahlbyk
Copy link
Owner Author

dahlbyk commented Sep 12, 2016

What OS are you using that you're unable to upgrade to PS 3?

I'm not all that interested in trying to preserve compatibility with Vista or XP, but you could certainly maintain a fork that maintains PS 2.0 compatibility and back-ports new features. Or just use an older version of posh-git.

@gherson
Copy link

gherson commented May 27, 2017

WARNING: posh-git support for PowerShell 2.0 is deprecated; you have version 2.0.
To download version 5.0, please visit https://www.microsoft.com/en-us/download/details.aspx?id=50395
For more information and to discuss this, please visit #163

To lose the above error I d/l'ed and installed Win7AndW2K8R2-KB3134760-x64.msu on my Win7 SP1 system (twice) as instructed then rebooted as it requested, and /still have the error/. The only folder I see under C:\Windows\System32\WindowsPowerShell is v1.0. (Just FYI; I'm giving up on this for now.)

@rkeithhill
Copy link
Collaborator

The folder name C:\Windows\System32\WindowsPowerShell\v1.0 is the same for all versions of Windows PowerShell. To tell which version you are running, type $PSVersionTable at the PowerShell prompt and hit enter.

@gherson
Copy link

gherson commented May 27, 2017

Good to know, thanks.
PowerShell version is still v2.0 after installing aforementioned .msu:

~\Documents\GitHub> $PSVersionTable

Name                           Value
----                           -----
CLRVersion                     2.0.50727.5485
BuildVersion                   6.1.7601.17514
PSVersion                      2.0
WSManStackVersion              2.0
PSCompatibleVersions           {1.0, 2.0}
SerializationVersion           1.1.0.1
PSRemotingProtocolVersion      2.1

@dahlbyk
Copy link
Owner Author

dahlbyk commented May 28, 2017

BuildVersion confirms you're on Win7 SP1, which is supported, so not sure why the installer would not be working for you. Does the Event Log have anything to say?

@gherson
Copy link

gherson commented May 28, 2017

Good call! thanks:
Control Panel\System and Security\Windows Update\View update history shows that my first install of KB3134760 yesterday failed (silently but with code 80070308) and that my second install was "Successful". After another reboot, Git Shell and PowerShell v5.0 are working with no complaints.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.