Share via

$PROFILE discrepancy between "built-in" PowerShell and PowerShell 7

Horinius 1 Reputation point
2021-05-21T14:17:26.083+00:00

I don't know if you guys have noticed this or not, in Windows 10's built-in PowerShell, the profile is at
C:\Users\<user>\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1

If I install PowerShell 7, the profile is at
C:\Users\<user>\Documents\PowerShell\Microsoft.PowerShell_profile.ps1

It's the same problem in Windows Server.

Seems like PowerShell design teams don't agree with each other!

Don't you guy think it's better for end-users to have unified AND unique profile?

Windows for business | Windows Server | User experience | PowerShell
0 comments No comments

1 answer

Sort by: Most helpful
  1. Anonymous
    2021-05-24T05:52:01.8+00:00

    Hi,

    PowerShell 7 is built on .NET Core and not fully compatible with Windows PowerShell 5.1. The separate profiles, installation paths and executable names enable you to run PowerShell 7 side-by-side with Windows PowerShell 5.1

    https://learn.microsoft.com/en-us/powershell/scripting/install/migrating-from-windows-powershell-51-to-powershell-7

    Best Regards,
    Ian Xue

    ============================================

    If the Answer is helpful, please click "Accept Answer" and upvote it.
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.