title: Package Manager Console has wrong version of PowerShell
body: <p>I'm running Visual Studio 2017 (version 15.7.3) on Windows 10 on two PCs, home and work.  Both have all of the latest updates applied both to the OS and to VS.  </p>
  
  <p>The problem is this: My work PC shows me a very wrong, very old (2.0) version of PowerShell in Package Manager Console.  My home PC shows me the correct (5.1) version corresponding to the OS version.  </p>
  
  <p>When I fire up PowerShell by itself, outside of Visual Studio, it shows me 5.1 on both machines.</p>
  
  <p>I cannot figure out what is causing the problem with Visual Studio on one PC and not the other and I don't even know where to begin looking.  Can anyone give me any ideas?</p>
  
  <p>Here's what I see on the work computer when enter the command "$PSVersionTable" in PM Console:   </p>
  
  <blockquote>
    <p>PM> $PSVersionTable</p>
    
    <p>Name                           Value                                  </p>
    
    <p>----                           -----                                                                                                             PSVersion                      2.0<br>
    PSCompatibleVersions           {1.0, 2.0}<br>
    BuildVersion                   6.1.7600.16385<br>
    CLRVersion                     4.0.30319.42000<br>
    WSManStackVersion              2.0<br>
    PSRemotingProtocolVersion      2.1<br>
    SerializationVersion           1.1.0.1</p>
  </blockquote>
  
  <p>Here's what I see with the same command on my home PC, all looks well.</p>
  
  <blockquote>
    <p>PM> $PSVersionTable</p>
    
    <p>Name                           Value                                  </p>
    
    <p>----                           -----                                                                                                       PSVersion                      5.1.16299.492<br>
    PSEdition                      Desktop<br>
    PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}<br>
    BuildVersion                   10.0.16299.492<br>
    CLRVersion                     4.0.30319.42000<br>
    WSManStackVersion              3.0<br>
    PSRemotingProtocolVersion      2.3<br>
    SerializationVersion           1.1.0.1</p>
  </blockquote>
  
  <p>In my investigations so far, I did come across a workaround (in the accepted answer to <a href="https://developercommunity.visualstudio.com/content/problem/35803/help-error-the-package-manager-console-requires-po.html" rel="nofollow noreferrer">this question</a>) that lets me edit the devenve.config file for Visual Studio to add some package redirects.  This does fix the problem but every time I make any minor configuration change to Visual Studio, the file gets overwritten and I have to do it all over again.</p>
  
  <p>Any idea where I might look to fix this?</p>