I upgraded from v4 to v5, and now I have to import all the modules in my scripts using “Import-Module.” Previously, it worked with the $PSModulePath environment variable.
I don’t understand how to avoid having to use “Import-Module” anymore.
I’m using the PowerShell 7 environment with “C:\Program Files\PowerShell\7\pwsh.exe.”
The modules are located in “C:\Program Files\PowerShell\7\Modules.”
Here is my $PSModulePath environment variable:
In the environments, I added the module path, but it still doesn’t work. I even specified the module path in “Modules to Import” in the environment, but still nothing.
Does anyone know why I’m experiencing this behavior?
Are you printing that environment variable in your script that is running in PSU? Or are you looking at the variable from a PS terminal? I mainly ask because PSU does do some messing with the PSModulePath.
That said, it should never be removing the C:\Program Files\PowerShell\7\Modules path so, if it’s not there, then we need to investigate this.
Are these your own custom modules or are they other ones you rely on?
That’s very strange. With Microsoft.Graph, the module is automatically imported, but not with MSOnline.
When I try to install MSOnline from PSU under “Platform > Module > Repositories > PSGallery,” the module doesn’t install because the “install” checkbox remains white. Whereas for Microsoft.Graph, the checkbox is greyed out.