title: Copy-Item with timeout
body: <p>I am recovering files from a hard drive wherein some number of the files are unreadable.   I'm unable to change the hardware level timeout / ERC, and it's extremely difficult to work around when I have several hundred thousand files, any tens of thousands of which might be unreadable.  </p>
  
  <p>The data issues were the result of a controller failure.  Buying a matching drive (all the way down), I've been able to access the drive, and can copy huge swaths of it without issues.  However, there are unreadable files dotted throughout the drive that, when accessed, will cause the SATA bus to hang. I've used various resumable file copy applications like <code>robocopy</code>, RichCopy, and a dozen others, but they all have the same issue.  They have a RETRY count that is based on actually getting an error reported from the drive. The issue is that the drive is taking an extremely long time to report the error, and this means that a single file may take up to an hour to fail officially.   I know how fast each file SHOULD be, so I'd like to build a powershell CMDLET or similar that will allow me to pass in a source and destination file name, and have it try to copy the file.  If, after 5 seconds, the file hasn't copied (or if it has - this can be a dumb process), I'd like it to quit. I'll write a script that fires off each copy process individually, waiting for the process before it to finish, but I'm so far unable to find a good way of putting a time limit on the process.   </p>
  
  <p>Any suggestions you might have would be greatly appreciated!</p>
  
  <p><strong>Edit:</strong> I would be happy with spawning a <code>Copy-Item</code> in a new thread, with a new PID, then counting down, then killing that PID.  I'm just a novice at PowerShell, and have seen so many conflicting methods for imposing timers that I'm lost on what the best practices way would be.  </p>
  
  <p><strong>Edit 2:</strong>  Please note that applications like <code>robocopy</code> will utterly hang when encountering the bad regions of the disk.  These are not simple hangs, but bus hangs that windows will try to preserve in order to not lose data.  In these instances task manager is unable to kill the process, but Process Explorer IS.  I'm not sure what the difference in methodology is, but regardless, it seems relevant.  </p>