title: 'Cannot find drive' powershell error after invoking Get-Date command
body: <p>Why is it that this command is able to export and create a file in the current path but when I add the Get-Date cmdlet it suddenly fails?</p>
  
  <p>Is the Get-Date cmdlet invoking some type of new environment?</p>
  
  <p>Working command - </p>
  
  <blockquote>
    <p>Get-Process | Sort-Object WorkingSet64 | Select-Object Name,@{Name='WorkingSet';Expression={($_.WorkingSet64/1MB)}} | Export-Csv -Path "processes64.csv" -Delimiter "," </p>
  </blockquote>
  
  <p>Command breaks - </p>
  
  <blockquote>
    <p>$Date = Get-Date -Format "MM-dd-yy-HH:MM"</p>
    
    <p>Get-Process | Sort-Object WorkingSet64 | Select-Object Name,@{Name='WorkingSet';Expression={($_.WorkingSet64/1MB)}} | Export-Csv -Path "processes64$Date.csv" -Delimiter ","  </p>
  </blockquote>
  
  <p>Error message - </p>
  
  <blockquote>
    <p>Export-Csv : Cannot find drive. A drive with the name 'processes64-06-28-16-15' does not exist.
    At line:3 char:120</p>
    
    <ul>
    <li>... Set64/1MB)}} | Export-Csv -Path "processes64-$Date.csv" -Delimiter ","</li>
    <li>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~</li>
    <li>CategoryInfo          : ObjectNotFound: (processes6406-28-16-15:String) [Export-Csv], DriveNotFoundException</li>
    <li>FullyQualifiedErrorId : DriveNotFound,Microsoft.PowerShell.Commands.ExportCsvCommand</li>
    </ul>
  </blockquote>
  
  <p>I'd just like to either export to a directory on the C drive or to the current working directory..</p>