Is there a reason that you need to use both openfiles.exe and net file?īelow is a function that uses only net file and wraps it around a PowerShell Script. This cmdlet should be used with care as it may result in data loss to the client for which the file is being closed if the client has not flushed all of the file modifications back to the server before the file is closed.'

****NOTE**** Per the TechNet article 'The Close-SMBOpenFile cmdlet forcibly closes a file that is open by one of the clients of the Server Message Block (SMB) server. Get-SmbOpenFile | Where-Object -Property sharerelativepath -match '.XLSX' | Close-SmbOpenFile -Force If you want to close one or more files that are open and that match the file extension '.XLSX'. If you want to close all open files on your file server: Get-SmbOpenFile | Close-SmbOpenFile Get-SmbOpenFile | Where-Object -Property sharerelativepath -match '.XLSX'Īfter finding your problem file in the results, you can then close the file by the fileID. If you know an Excel file is the issue, you can narrow your search for all open files with a. The files will display along with the following table headers FileId SessionId Path ShareRelativePath ClientComputerName ClientUserName Use Get-SmbOpenFile to display all of the open files on your file server. Logged into your file server, start PowerShell. Get-SmbOpenFile and Close-SmbOpenFile will get the job done for you.

Windows server close open files