Import-Module : Could not load file or assembly 'System.Management.Automation

H Risbud 246

I'm unable to run PnP PowerShell commands using PowerShell ISE in administrative mode. Getting following error

PS C:\WINDOWS\system32> Import-Module PnP.PowerShell
Import-Module : Could not load file or assembly 'System.Management.Automation, Version=7.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
At line:1 char:1
+ Import-Module PnP.PowerShell
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Import-Module], FileNotFoundException
    + FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.PowerShell.Commands.ImportModuleCommand

My PowerShell ISE details PS C:\WINDOWS\system32> $PSVersionTable Name Value ---- ----- PSVersion 5.1.19041.1 PSEdition Desktop PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...} BuildVersion 10.0.19041.1 CLRVersion 4.0.30319.42000 WSManStackVersion 3.0 PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 PS C:\WINDOWS\system32> get-host|Select-Object Name : Windows PowerShell ISE Host Version : 5.1.19041.1 InstanceId : d91d81d9-be20-492f-be62-f5ea45de0765 UI : System.Management.Automation.Internal.Host.InternalHostUserInterface CurrentCulture : en-US CurrentUICulture : en-US PrivateData : Microsoft.PowerShell.Host.ISE.ISEOptions DebuggerEnabled : True IsRunspacePushed : FalseRunspace : System.Management.Automation.Runspaces.LocalRunspace Please help me to solve this error. Thanks in advance

Kathy Blasco 21

My error is similar. I just updated to 2.1.1. I was not having an issue prior to the upgrade. My error:

Import-Module -Name PnP.PowerShell -Debug -Force
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\PnP.PowerShell\2.1.1\PnP.PowerShell.psd1'.
VERBOSE: Loading 'FormatsToProcess' from path 'C:\Program Files\WindowsPowerShell\Modules\PnP.PowerShell\2.1.1\PnP.PowerShell.Format.ps1xml'.
VERBOSE: Populating RepositorySourceLocation property for module PnP.PowerShell.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\PnP.PowerShell\2.1.1\Core\PnP.PowerShell.dll'.
Import-Module : Could not load file or assembly 'System.Runtime, Version=6.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. 
The system cannot find the file specified.
At line:1 char:1
+ Import-Module -Name PnP.PowerShell -Debug -Force
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Import-Module], FileNotFoundException
    + FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.PowerShell.Commands.ImportModuleCommand

Rich Matheisen 42,996 Reputation points

2023-04-04T18:35:54.7566667+00:00

What version of System.Management.Automation is installed on your machine? The version on my machine Windows 10, PowerShell 5.1) (without any PNP packages installed) is 6.x.x.x. Your module is looking for version 7.2.0.0.
Kathy Blasco 21 Reputation points

2023-04-04T18:41:44.48+00:00

Hi @Rich Matheisen Where would I find that information?
H Risbud 246 Reputation points

2023-04-04T19:00:36.88+00:00

I can see System.Management.Automation. but still not sure how to fix this issue
C:\Program Files (x86)\Reference Assemblies\Microsoft\WindowsPowerShell\3.0\System.Management.Automation.dll C:\Windows\Microsoft.NET\assembly\GAC_MSIL\System.Management.Automation\v4.0_3.0.0.0__31bf3856ad364e35\System.Management.Automation.dll
Rich Matheisen 42,996 Reputation points

2023-04-04T19:10:45.6533333+00:00

Find the DLL, right-click on it, and look at the "Details" tab.
H Risbud 246 Reputation points

2023-04-04T20:11:47.8766667+00:00

Still not cleared how to fix this issue?
AdamMorgan-1941 10 Reputation points

2023-04-04T20:29:21+00:00
I started seeing this error after setting up a VDI at a customer site. After comparing my setup with my customer's setup, I can see that he had version 1.12.0 and I had 2.1.1.
Here is what I did to resolve it:

Uninstalled the module

Rebooted (not sure if this is necessary)

Installed a specific version of the module: Install-Module -Name PnP.PowerShell -RequiredVersion 1.12.0

and I am working again now
Darío León 0 Reputation points

2023-04-18T03:58:38.8733333+00:00

You should first check your PowerShell version, I had the same problem and I resolve it by installing the last version of PowerShell (7.3.4).
Zhou, George 6 Reputation points

2023-07-19T18:50:33.6766667+00:00

Hi Risbud,

Thanks for your instruction. It works for the Import-Module PnP.Powershell. Due to Microsoft PowerShell and Window's PowerShell change. Bunch of my Ps1 files do not work any more. I have spent time to review the PowerShell. It seems that Microsoft has made PowerShell more confusing and becoming a useless tool. Check the Exchange online PowerShell, SharePoint Online PowerShell, Azure PowerShell, these are pieces of garbage! A disaster! All of these PowerShell does not even cover complete set of functionalities. Looked at their reference, it's just a small set of functions.

Thank you Risbud!

George
Lovnesh Kumar 10 Reputation points

2023-09-14T04:18:52.08+00:00

After installing Version 2.1.1 of PnP Powershell, i faced the same issue. It looks like this version has some compatibility issue with Powershell ISE version 5.

Below are the steps that i used to overcome this issue as a workaround.

Uninstalled all versions of PnP Module

Uninstall-Module PnP.PowerShell -AllVersions

Install nuget package
Install-PackageProvider -Name nuget -MinimumVersion 2.8.5.201 -force

Installed version 1.12.0 for PnP Powershell Module.
Install-Module -Name "PnP.PowerShell" -RequiredVersion 1.12.0 -Force -AllowClobber

Now i am able to import the PnP Module without any issues.
Le Dang 0 Reputation points

2023-09-29T09:45:28.13+00:00

Thank you @Lovnesh Kumar . It works. Step Install-PackageProvider -Name nuget -MinimumVersion 2.8.5.201 -force is necessary. I tried uninstalling, reinstall version 1.12.0 before without the second step and it did not work. With your comment, I run three steps and it is OK now.
Mathieu Diepman 6 Reputation points

2023-10-10T06:20:49.05+00:00

Try installing Powershell 7 and running it from there, that worked for me

Accepted answer

RaytheonXie_MSFT 26,876 Reputation points Microsoft Vendor

2023-04-05T02:35:54.4933333+00:00
Hi @H Risbud ,

I'm glad to hear you solve the problem ,if you have any issue about SharePoint, you are welcome to raise a ticket in this forum.

By the way, since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others." and according to the scenario introduced here: Answering your own questions on Microsoft Q&A, I would make a brief summary of this thread:

[Import-Module : Could not load file or assembly 'System.Management.Automation] Issue Symptom: unable to run PnP PowerShell commands using PowerShell ISE in administrative mode. Getting following error

Import-Module : Could not load file or assembly 'System.Management.Automation, Version=7.2.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.

Solution:

Uninstall all versions and then install correct 1.12.0 version. Newer version PnP PowerShell 2.1.1 has issues #1. This issue happened with newer version PnP PowerShell 2.1.1.

Set Tls12 protocol [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Install NuGet Install-PackageProvider -Name nuget -MinimumVersion 2.8.5.201 -force

Install PnP.PowerShell with version 1.12.0 Install-Module -Name "PnP.PowerShell" -RequiredVersion 1.12.0 -Force -AllowClobber

You could click the "Accept Answer" button for this summary to close this thread, and this can make it easier for other community member's to see the useful information when reading this thread. Thanks for your understanding!
Please sign in to rate this answer.

38 people found this answer helpful.
Lamar Gardner 10 Reputation points Microsoft Employee

2023-04-05T13:55:49.8133333+00:00

This does not work for me.

Kathy Blasco 21 Reputation points

2023-04-05T16:05:40.7933333+00:00

I only completed steps 1 and 4 to resolve my issue. Also reverted back to 1.12.0.

BerndEinholz-9539 0 Reputation points

2023-04-06T12:57:28.6666667+00:00

I was able to update (Update-Module -Name "PnP.PowerShell") to a working 2.1.1 after installing 1.12.0

Little, Matthew 0 Reputation points

2023-04-10T18:09:53.7366667+00:00

Worked for me... thank you very much!

Paul Martin 0 Reputation points

2023-04-17T23:13:38.2866667+00:00

Not working for me. I'm at my wit's end with this thing.

Matt Derosia 0 Reputation points

2023-04-20T15:40:15+00:00

Worked for me

Golding, Dustin 0 Reputation points

2023-05-04T16:28:15.61+00:00

PnP folks on github will not admit this is an issue with their module, but reverting back to 1.12.0 from 2.1.1 solved my issues.

J-Luc B 0 Reputation points

2023-05-31T11:11:35.56+00:00

Worked for me with Install-Module -Name "PnP.PowerShell" -RequiredVersion 1.12.0 -Force -AllowClobber, thank you very much!

Carlos Montilla 0 Reputation points

2023-06-09T23:47:29.98+00:00

This worked for me. I initially continued to have issues until I figured this out...

If you are using PS 5.1, YES, you need to have PnP.PowerShell 1.12.0 installed.
Yes, you CAN have this installed alongside 2.1.1. The requirement is that you have to Import the correct version in your 5.1 scripts. If you don't, it will load the latest version and you'll continue to get the error.

You can do this by putting this at the top of your scripts running in PS 5.1 :
Import-Module pnp.powershell -RequiredVersion 1.12.0

Basic stuff, unless you don't read the fine print - like me.

Ashish Prajapati 0 Reputation points

2023-07-04T06:31:42.11+00:00

It's Work for me.

Berger, Matthias 10 Reputation points

2023-08-14T11:37:00.8166667+00:00

Same problem here.

Why would I deliberately install an old version? Shouldn't the new one be fixed instead?
Sign in to comment

6 additional answers

WP 5 Reputation points

2023-07-14T10:14:58.21+00:00

This is unacceptable and should have been fixed straight away or at least with the first update after this problem appeared. It is not supposed to be a game of "match the right version".
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment
Matt Derosia 0 Reputation points

2023-05-18T15:25:36.8433333+00:00

I am attempting to run PNP Powershell in PS v5 and doesnt mention anything about needing to migrate to v7.
Please sign in to rate this answer.
Mikołaj Wiśniewski 5 Reputation points

2023-05-22T12:54:27.4633333+00:00

Welcome to Microsoft world!
Sign in to comment

Import-Module : Could not load file or assembly 'System.Management.Automation

6 additional answers

Activity