"You have an older version of PackageManagement..." Prompts Repeatedly

[sympmarc]

System Details

System Details Output

### VSCode version: 1.47.2 17299e413d5590b14ab0340ea477cdd86ff13daf x64

### VSCode extensions:
blackmist.LinkCheckMD@0.3.1
DavidAnson.vscode-markdownlint@0.36.1
docsmsft.docs-article-templates@0.2.9
docsmsft.docs-authoring-pack@0.1.8   
docsmsft.docs-images@0.0.9
docsmsft.docs-linting@0.0.5
docsmsft.docs-markdown@0.2.76        
docsmsft.docs-metadata@1.0.4
docsmsft.docs-preview@0.3.53
docsmsft.docs-yaml@0.2.5
GitHub.vscode-pull-request-github@0.18.0
ms-vscode.powershell@2020.6.0
msjsdiag.debugger-for-chrome@4.12.9
redhat.vscode-yaml@0.9.1
streetsidesoftware.code-spell-checker@1.9.0


### PSES version: 2.2.0.0

### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.18362.752
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.752
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1

Issue Description

When I open a project, I am prompted with this probably 80% of the time. I've run it repeatedly, but it doesn't seem to make a difference.

If I click "Yes", this command is run"

PS D:\code\Denholtz\Deployment> powershell.exe -NoLogo -NoProfile -Command 'Install-Module -Name PackageManagement -Force -MinimumVersion 1.4.6 -Scope CurrentUser -AllowClobber'

Expected Behaviour

One prompt makes sense if I'm out of date. But it simply repeats.

Actual Behaviour

Too many prompts.

[kaiaschulz]

Hi,
I have exactly the same error as described above.
Also a re-installation of "ms-vscode.PowerShell" wasn't successfull.

Message which will be displayed:
You have an older version of PackageManagement known to cause issues with the PowerShell extension. Would you like to update PackageManagement (You will need to restart the PowerShell extension after)?

Command which will be executed if I click on "Yes":
powershell.exe -NoLogo -NoProfile -Command 'Install-Module -Name PackageManagement -Force -MinimumVersion 1.4.6 -Scope CurrentUser -AllowClobber'

Message which appears after the command was successfully executed:
PackageManagement updated, If you already had PackageManagement loaded in your session, please restart the PowerShell extension.

Directly afterwards the initial message appears again.
This only happens twice to me.

---

### VSCode version: 

Version: 1.47.2 (user setup)
Commit: 17299e413d5590b14ab0340ea477cdd86ff13daf


### PowerShell version:

Name                           Value
----                           -----
PSVersion                      5.1.18362.752
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.752
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1


### VSCode extensions:

bencoleman.armview
ckolkman.vscode-postgres
donjayamanne.githistory
eamodio.gitlens
hashicorp.terraform
jmrog.vscode-nuget-package-manager
ms-dotnettools.vscode-dotnet-runtime
ms-vscode-remote.remote-ssh
ms-vscode-remote.remote-ssh-edit
ms-vscode.powershell
ms-vsts.team
msazurermtools.azurerm-vscode-tools

[GreatScott000]

I have been getting the same issue for about a month issue. When I run the update requested I get an error:

You have an older version of PackageManagement known to cause issues with the PowerShell extension. Would you like to update PackageManagement (You will need to restart the PowerShell extension after)?

PS E:\todd\Repos\Evolve-iMS\UNIT001_Apps> powershell.exe -NoLogo -NoProfile -Command 'Install-Module -Name PackageManagement -Force -MinimumVersion 1.4.6 -Scope CurrentUser
-AllowClobber'
WARNING: Unable to resolve package source 'https://www.powershellgallery.com/api/v2/'.
PackageManagement\Install-Package : No match was found for the specified search criteria and module name 'PackageManagement'. Try Get-PSRepository to see all available
registered module repositories.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.6.0\PSModule.psm1:2057 char:21
... $null = PackageManagement\Install-Package @PSBoundParameters
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], Exception
+ FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

PS E:\todd\Repos\Evolve-iMS\UNIT001_Apps>get-psrepository

WARNING: MSG:UnableToDownload «https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409» «»
WARNING: Unable to download the list of available providers. Check your internet connection.

Name InstallationPolicy SourceLocation

---

PSGallery Untrusted https://www.powershellgallery.com/api/v2/

Environment Information

Visual Studio Code

Name	Version
Operating System	Windows_NT x64 10.0.14393
VSCode	1.47.3
PowerShell Extension Version	2020.6.0

PowerShell Information

Name	Value
PSVersion	5.1.14393.3471
PSEdition	Desktop
PSCompatibleVersions	1.0 2.0 3.0 4.0 5.0 5.1.14393.3471
BuildVersion	10.0.14393.3471
CLRVersion	4.0.30319.42000
WSManStackVersion	3.0
PSRemotingProtocolVersion	2.3
SerializationVersion	1.1.0.1

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)

Extension	Author	Version
al	ms-dynamics-smb	5.0.288712
al-code-outline	andrzejzwierzchowski	2.0.5
al-object-designer	martonsagi	0.2.2
crs-al-language-extension	waldo	1.2.4
gc-excelviewer	GrapeCity	3.0.39
gitlens	eamodio	10.2.2
navertical	Kine	0.5.6
powershell	ms-vscode	2020.6.0
team	ms-vsts	1.161.0
todo-tree	Gruntfuggly	0.0.178
vscode-guid	heaths	1.4.20
vsliveshare	ms-vsliveshare	1.0.2478
xml	DotJoshJohnson	2.5.1

[SydneyhSmith]

What is the output of gmo PackageManagement -ListAvailable in the integrated console?

[sympmarc]

Before reinstalling PackageManagement:

    Directory: C:\Program Files\WindowsPowerShell\Modules


ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Binary     1.0.0.1    PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}

Command which runs:

powershell.exe -NoLogo -NoProfile -Command 'Install-Module -Name PackageManagement -Force -MinimumVersion 1.4.6 -Scope CurrentUser -AllowClobber'

After reinstalling PackageManagement:

    Directory: C:\Program Files\WindowsPowerShell\Modules


ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Binary     1.0.0.1    PackageManagement                   {Find-Package, Get-Package, Get-PackageProvider, Get-PackageSource...}

Before and after look the same to me...

[rjmholt]

@sympmarc does any error output appear in the integrated console?

[sympmarc]

No error at all. Just the prompt to reinstall PackageManager.

Since I posted the issue, I think I've figured out the pattern. The prompt comes up each time I open a new project folder, no matter how many other projects folders I have open in other VS Code windows. The prompt comes up right as the terminal window is revving up.

From that point forward in the project folder session, everything is fine.

If it's helpful, the prompt in the PowerShell Integrated Console is this:

=====> PowerShell Integrated Console v2020.6.0 <=====

PS D:\code\[...]> 

If I garbage can the terminal window for any reason, I'm prompted again.

[rjmholt]

Ok, given that, I think your logs might be useful here

[sympmarc]

Here are the logs from one PS terminal session. I can broaden out if that is useful.

1595969526-8689461e-d76d-4354-9e2a-0f05974d7ce41595969454260.zip

[rjmholt]

Strangely, there doesn't seem to be any report of failure:

2020-07-28 16:52:16.270 -04:00 [VRB] Attempting to execute command(s):

    powershell.exe -NoLogo -NoProfile -Command 'Install-Module -Name PackageManagement -Force -MinimumVersion 1.4.6 -Scope CurrentUser -AllowClobber'
    Out-Default

[sympmarc]

It doesn't really feel like a failure, per se. It's more like the session doesn't see the installed version of PackageManager and thinks it needs a new install.

Here's a log with the reinstallation included.
1595970085-39394155-83d7-4431-b0d9-d0f1a64238f21595970040956.zip

[SydneyhSmith]

Thanks @sympmarc we actually just released an update to our Preview extension which has addressed a Package Management bug, would you mind giving it a try and letting us know if you are still hitting this issue?