强制关闭脚本运行时正在使用的文件

Question

I have following script that take files older than specified day and saves them as archive in a different folder. The script works fine with most of the files but for some files it gives this error and doesn't include those file in the archive.

Move-Item : The process cannot access the file because it is being used by another process.
At C:\SRS\SRSLogArchieveScript.ps1:49 char:13
+             Move-Item <<<<  $item.FullName $destPathController -force;
    + CategoryInfo          : WriteError: (C:\SRS\Controll...apter0611-1.log:FileInfo) [Move-Item], IOException
    + FullyQualifiedErrorId : MoveFileInfoItemIOError,Microsoft.PowerShell.Commands.MoveItemCommand

However I am using -force with -move item but it still have this issue. Is there a way I can actually force close all the files in use to make sure all files are included as a part of archive.

try
{
foreach( $item in (Get-ChildItem $sourcePath -recurse | Where-Object { $_.CreationTime -le $archiveTillDate }) )
{
$item.FullName;
Move-Item $item.FullName $destPath -force;
}
}
catch
{
$_.Exception.Message;
}
Finally
{
#Executing Zip Command to Archieve:
& $pathTo7ZipExe $arguments;

#Delete temporary log archieve directory
Remove-Item $logArchieve -recurse;

}

Answer 1

This behavior is by design. Consider that the original application keeping an open file tries to write into it. If you have "stolen" the underlying file, what'll happen? Anything from a crash to unexpected behavior. To prevent such a thing, all modern OS prevent such an operation from non-priviledged users.

That being said, you could use a tool like Sysinternals' Handle.exe to check if a file has got open a handle. The same tool can close handles if you have sufficient permissions.

Another a solution would be to try and open the file with read-write access. This would allow you to filter out files that are reserved - assuming no process is going to open the file just after you release your own lock. The only way to be sure is to copy the file contents into archive location whlist you got the exclusive write lock and finally deleting the file.