2 Responses

  1. Doc Dish
    Doc Dish at |

    This appears to be due to the PowerCLI installer adding a user environment variable for PSModulePath where one doesn’t exist and populating it with the location of the PowerCLI modules (it does this even if you install it for all users).

    If there is no user PSModulePath variable, PowerShell adds “$Home\Documents\WindowsPowerShell\Modules” to it automatically; but if a user variable does exist, it doesn’t.

    I moved the location of the PowerCLI modules to the system PSModulePath variable (as it’s installed for all users of the system) and removed the user variable, which had the same effect as your fix above.

    (see https://communities.vmware.com/thread/509272?start=0&tstart=0)

    Thanks for your help getting to the bottom of this.

  2. How to Use the PowerShell Gallery to Update Your Standalone Modules - Wahl Network

    […] PSModulePath environmental variable. This seems to be a natural part of using Windows 10. Check out this blog post for more […]

Share your point of view!