Product: PowerShell Universal
Version: 4.0.4
Updated to 4.0.4 and have found an issue were the modules available are now limited and do not match the modules available when running powershell directly on the server under the service account. Issue was present in a scheduled job but confirmed to be there in Terminals.
Upon investiation it looks like $env:PSModulePath when running powershell locally on the server does not match when powershell is run under the same user in either terminal and/or a job in PSU.
PSU Terminal Output
Powershell Output (Missing paths highlighted in Yellow)
