Forcefully unlock files locked by other processes

[BinToss]

Other processes are locking haloce.exe to write to it, which prevents us from writing our binary patches.

Priority	Solution
HIGH	Cancel "Load Game" and present user with access error. Use Windows' shutdown files API thing (see Deadlock) to list blocking processes.
Medium	Embed SysInternals' Handles/Handles64 to yank and break handles. Alternatively, System Informer, but it's larger.
low	Finish Deadlock Native Handles pull request. Integrate into HXE. Invocations will be a PITA. CIL Exports?

Propositions

A. Write to copy of haloce.exe, leaving the locked file as-is (mostly)

1. Rename the directory entry of the file to haloce.exe.0.bak. This won't touch the file itself. Instead, we change filesystem information about the file. Confusing, I know. System.IO.FileInfo?
2. Copy "haloce.exe.0.bak" to "haloce.exe" as new file in the same directory.
3. Resume normal "haloce.exe" activities.
   B. Close file handles with filename 'haloce.exe'
4. Use SysInternal's Handles app/lib to get a list of processes' File handles of filename "haloce.exe". See Handles feature of System Informer.
5. Close each handle. Suitable API in System.Management

Examples

• IObit Unlocker Heh. No way~!
• Process Hacker System Informer
• SysInternals Handles, Handles64, ProcessExplorer

Biiig dumpy

Use System.IO.File.Open() to check if file is locked (share: none)

https://www.cloudsavvyit.com/2956/how-to-manage-open-file-handles-with-powershell#testing-for-locked-files
https://www.cloudsavvyit.com/2956/how-to-manage-open-file-handles-with-powershell#openfiles-utility
https://www.cloudsavvyit.com/2956/how-to-manage-open-file-handles-with-powershell#the-handle-application

https://www.majorgeeks.com/files/details/unlocker.html
https://docs.microsoft.com/en-us/sysinternals/downloads/handle
https://lockhunter.com/download.htm

https://docs.microsoft.com/en-us/dotnet/api/system.io.filestream.unlock?view=net-5.0
https://docs.microsoft.com/en-us/dotnet/api/system.io.filestream.handle?view=net-5.0
https://docs.microsoft.com/en-us/dotnet/api/system.io.file.openhandle?view=net-6.0
https://docs.microsoft.com/en-us/dotnet/api/system.io.fileinfo?view=net-5.0
https://docs.microsoft.com/en-us/dotnet/api/system.io.fileshare?view=net-5.0
https://docs.microsoft.com/en-us/dotnet/api/system.io.file?view=net-5.0
https://docs.microsoft.com/en-us/windows/win32/api/winternl/nf-winternl-ntquerysysteminformation

https://docs.microsoft.com/en-us/dotnet/api/microsoft.visualbasic.filesystem.unlock?view=net-5.0
https://devblogs.microsoft.com/dotnet/file-io-improvements-in-dotnet-6
https://stackoverflow.com/questions/2225733/how-to-forcefully-unlock-a-file-in-c
https://stackoverflow.com/questions/47977927/error-the-process-cannot-access-the-file-because-it-is-being-used-by-another-pro
https://dotnet-assembly.blogspot.com/2012/10/c-check-file-is-being-used-by-another.html
https://www.codeproject.com/questions/141068/file-is-being-used-by-another-process

[BinToss]

https://www.nirsoft.net/utils/opened_files_view.html
We could just add this as an embedded resource to be extracted and run and a command line util when needed.

BUT I already said I would contribute to CodeDead/deadlock-dotnet-sdk

[BinToss]

Scratch that NirSoft suggestion. Use Microsoft SysInternals' Handles/Handles64.

1. OpenedFilesView does not have an EV-signed driver. It will not work under Secure Boot.
2. Handles is better >:)