File used by another process. about termsrvpatcher HOT 4 CLOSED

This means that after stopping the Remote Desktop Service still another process is locking termsrv.dll. Please stop the service manually and make sure no other process is locking it before trying again. Maybe I will implement a more helpful error message for this situation.

from termsrvpatcher.

Will it be possible to patch the termsrv.dll in another location?
I cannot get this patcher to work but when I do it manually it works magically;

1. Take ownership
2. Give myself (User) Full Control of Termsrv.dll
3. Copy Termsrv.dll to desktop
4. Edit with HEX editor
5. Kill termservice
6. Rename Termsrv.dll in System32 folder to Termsrv.dll.bak.[date]
7. Copy Termsrv from desktop to System32 folder
8. Start Termservice

But somehow this patcher doesn't work and cannot find out why it is strugling. Do you have some kind of persistent error log?

from termsrvpatcher.

Please stop termservice manually and use Sysinternals Process Explorer to find the process with a handle to C:\Windows\System32\termsrv.dll and kill the process. See https://helpcenter.gsx.com/hc/en-us/articles/115015880627-How-to-Identify-which-Windows-Process-is-Locking-a-File-or-Folder for details. After the process is killed, patching should succeed.

If you want to modify the path to termsrv.dll you have to change this code line. If you don't have Visual Studio 2019 installed for debugging, you can download the Community Edition from https://visualstudio.microsoft.com/vs/.

from termsrvpatcher.

It turns out that running Process Explorer as Administrator is not enough to see for example the handle of the termservice process svchost.exe. I had to run Process Explorer at least as System user. I propose to use NSudo to run the Process Explorer as TrustedInstaller to be able to find ALL handles to termsrv.dll

from termsrvpatcher.