Modules not recognized after install about pnp-powershell

[JohnGoldsmith]

So on further investigation, a couple of things appear to be happening. Installation scope appears not to be working correctly and setting the User variable, PSModulePath, appears to interfere with Module discovery.

Running the msi installs per-user even though the install scope (Advanced button) is set to all users. However if you toggle the install scope radio buttons and finally select all users, then it installs as expected (as all users) and other non-pnp modules are discovered correctly.

When installing for all users the User variable PSModulePath is not created and Powershell seems to handle the Documents located modules ok.

So just to confirm, having installed for all users, there is no entry for PSModulePath under the User scope and the System scope looks like this:

%SystemRoot%\system32\WindowsPowerShell\v1.0\Modules;
C:\Program Files\Intel;
C:\Program Files (x86)\Microsoft SDKs\Azure\PowerShell\ServiceManagement;
C:\Program Files (x86)\SharePoint Online Management Shell;
C:\Program Files\SharePoint Online Management Shell;
C:\Program Files (x86)\OfficeDevPnP.PowerShell.Commands\

I did come across a Sapien post https://www.sapien.com/blog/2012/05/22/psmodulepath-discrepancies/ that suggests that the Documents and ProgramFiles\WindowsPowerShell\Modules paths are added by default (unless modified?), but I'm not certain if that's the case here.

Best regards

John

[TobiasWeltner]

When you test-drive your MSI package, no matter what you do, always make sure you never change existing values. The default user profile modules folder must at all times be part of PSModulePath, or else you disable all user-specific modules from other sources.

In fact, you should not modify PSModulePath at all. Simply pick one of the default locations.

[rjesh-git]

Can you try "Set-ExecutionPolicy Unrestricted -Force" in PowerShell window?

[JohnGoldsmith]

Hi rjesh,
Well I installed for all users and then it worked correctly (as above). The issue, I believe, is other non-pnp modules not being discovered when the user PSModulePath variable is set. For the record, though, my Execution Policy is set to Bypass.