When a DLL is loaded into processes as a result of invoking SetWindowHookEx, the DLL remains in the processes after exiting Hotkey Detective. As a consequence, the DLL cannot be deleted from user's disk, because it's still used by the system. It's not possible to simply unload a DLL from a foreign process.
A possible solution is to implement a logic inside the DLL that will make it to unload itself. I'm thinking about using CreateTimerQueue to periodically check for global "unloading event" that will be signaled when Hotkey Detective is being closed.
When a DLL is loaded into processes as a result of invoking
SetWindowHookEx, the DLL remains in the processes after exiting Hotkey Detective. As a consequence, the DLL cannot be deleted from user's disk, because it's still used by the system. It's not possible to simply unload a DLL from a foreign process.A possible solution is to implement a logic inside the DLL that will make it to unload itself. I'm thinking about using
CreateTimerQueueto periodically check for global "unloading event" that will be signaled when Hotkey Detective is being closed.