That is surprising. It means that madCodeHook's automatic "a new dll was loaded, I need to hook it now" check doesn't seem to work in your case. I don't know why, maybe the dll was loaded in an unusual way or something. Might make sense to update to the latest madCodeHook build, in case you're still using an older version. Not sure if it will help, but would be worth a try:http://madshi.net/madCollection.exe
I wouldn't advise to always call LoadLibrary('wtsapi32.dll') in all processes systemwide in your hook dll.