PackageManagement module fails to update when using AppLocker

[johlju]

The preview extension asks to replace the PackageManagement module which throws an error when using AppLocker (ConstrainedLanguage mode).

PackageManagement\Install-Package : An error has occurred while loading script module PackageManagement because it has a different language mode than the module manifest. The manifest la
nguage mode is ConstrainedLanguage and the module language mode is FullLanguage. Ensure all module files are signed or otherwise part of your application allow list configuration.

Originally posted by @johlju in #1221 (comment)

[TylerLeonhardt]

@johlju do you have any policies set up for PackageManagement or PowerShell built-in modules or signatures?

Also, what version of PowerShellGet are you using?

[johlju]

...do you have any policies set up for PackageManagement or PowerShell built-in modules or signatures?

Yes, we allow running the modules under %programfiles%\WindowsPowerShell\Modules on these dev workstations.

Also, what version of PowerShellGet are you using?

PowerShellGet has not been replaced with a newer one, still the one that came with Windows 10 I guess.

ModuleType Version    Name
---------- -------    ----
Script     1.0.0.1    PowerShellGet

Although myself do not have local admin permission so I waiting for a colleague to verify this still exist when running VS Code with elevation, which I guess is needed to replace/update the PackageManagement module, unless it will update to -Scope CurrentUser?

I saw now that it do indeed try to update to the scope CurrentUser.

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

PackageManagement\Install-Package : An error has occurred while loading script module PackageManagement because it has a different language mode than the module manifest. The manifest language mode is ConstrainedLanguage and the module language mode is FullLanguage. Ensure all
 module files are signed or otherwise part of your application allow list configuration.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:1809 char:21
+ ...          $null = PackageManagement\Install-Package @PSBoundParameters
+                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (Microsoft.Power....InstallPackage:InstallPackage) [Install-Package], Exception
    + FullyQualifiedErrorId : Modules_MismatchedLanguageModes,Microsoft.PowerShell.Commands.TestModuleManifestCommand,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackage

[TylerLeonhardt]

I have a "fix" out for this that doesn't run a command on your behalf because apparently PackageManagement doesn't play well in CLM...

There's also a setting to disable this warning already... though, keep in mind, you're using a version of PackageManagement that could lock up the PowerShell extension if you don't update it...

[johlju]

Then I suggest we close this issue once that PR is through.

We can distribute the module (PackageManagement and PowerShellGet) centrally, for example together with the deployment of VS Code (for PowerShell dev stations).