function Unlock-File { param( [Parameter(Mandatory)] [string]$FilePath, [string]$HandlePath = "handle64.exe" ) if (-not (Test-Path $HandlePath)) { Write-Error "handle64.exe not found. Download from Sysinternals." return }
# Graceful stop (sends close signal) Stop-Process -Id 8764 Stop-Process -Id 8764 -Force powershell unlock file
Stop-Process -Name explorer -Force Start-Process explorer.exe You know the lock is caused by Explorer (e.g., an image or video file preview stuck open). 2. Finding the Culprit: Identifying the Locking Process PowerShell can't directly break a lock without help, but it can tell you who has the lock. For this, we use the Handle tool from Sysinternals (Microsoft’s official utility suite). This immediately rips the lock away from the owning process
# Force close all handles to a specific file (use with extreme caution!) & "C:\path\to\handle64.exe" -accepteula -c "C:\path\to\file.pdf" -y The -y flag suppresses confirmation. This immediately rips the lock away from the owning process. The process may crash or lose unsaved data, but the file will be unlocked. powershell unlock file
Now you can stop the offending process gracefully or forcefully:
You need to know exactly which application (Word, Notepad, a rogue service) is holding the lock before acting. 3. The "Force Unlock" via Safe Volume Opening For advanced scenarios, you can use .NET's FileShare.None method. This doesn't break an existing lock, but it can prevent future locks or test if a file is locked:
& "C:\path\to\handle64.exe" -accepteula "C:\path\to\your\file.pdf" The output will look like: notepad.exe pid: 8764 type: File C:\path\to\your\file.pdf