PR Summary

Fix #7324

The PowerShellVersion fields in PSCore built-in modules were changed to 6.1 to reflect the current version of PSCore (new cmdlets were added in 6.1 timeframes). However, this breaking the scenario where a user needs to start Windows PowerShell from PSCore because the PSCore built-in modules will be found first and loaded by default, and the loading fails because they require a powershell of version 6.1.

Set PowerShellVersion to 3.0 for built-in modules to make Windows PowerShell work when starting from PSCore. This is a temporary workaround. We have the RFC PowerShell/PowerShell-RFC#133 submitted to address this issue by introducing a new environment variable representing PSModulePath for PSCore. Once we implement that RFC, this problem will go away. See #7324 (comment) for more information.

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Change is not breaking
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: to the beginning of the title and remove the prefix when the PR is ready.
• User-facing changes
  • Not Applicable
  • OR
  • User-facing Documentation needed
    • Issue filed - Issue link:
• Testing - New and feature
  • Not Applicable or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
    • Add [feature] if the change is significant or affects feature tests