title: Powershell paths off (settings corrupt?)
body: <p>I'm running Windows 10x64 with full updates on a Lenovo P70 laptop with 32GB of RAM.</p>
  
  <p>My team is working on a complex powershell 5.1 solution.  We have a powershell window that opens a lot of other powershell windows which run some SQL.  Until a few days ago, everything worked fine.  Suddenly PowerShell 5.1 starting inserting "C:\windows\system32" in as the value for pwd.path where we find TXT files that will be read in.  We would literally get paths like "C:\windows\system32" when we were accessing the pwd.path variable.</p>
  
  <p>Here is where its is being used:</p>
  
  <pre><code>$fr = [System.IO.Path]::Combine( ((pwd).Path), ($folderName) );
  </code></pre>
  
  <p>The entire PS1 script now fails spectacularly.  I looked at my powerhsell profiles, and they're all blank (just some comments at most).  I decided to try installing Powershell 6, and after two minor modifications, everything worked fine.  Thing is, my team has come up with a rather complex PS1 script solution, and we're about to put it into action.  Now is not the time to be switching from Powershell5 to Powershell6.  Also, I tried hard coding the path we need on Powershell5, and that worked.  Thing is, these scripts really need to be able to run from a relative folder that varies.  Everything runs fine on my colleague's identical computer.</p>
  
  <p>From what I can tell, one of settings got corrupted.  Thing is, I don't know how to fix this.</p>
  
  <p>Does anyone know what happened to my powerhsell?
  Does anyone know how to fix it other than running Powershell6?</p>
  
  <p>Thanks in advance!</p>