Hello, we've been experiencing a problem when users have installed Web Companion. Calling SetFileCompletionNotificationModes(handle, FILE_SKIP_COMPLETION_PORT_ON_SUCCESS) from our code will get intercepted by your LavasoftTcpService64.dll, which crashes with the above access violation on 64bit Windows 8 and Windows 10.
Examining a disassembly of the code that's crashing, it seams that the memory address (0x00000001FFFD868A) is hardcoded into your code. Are you assuming something about the system that's no longer valid in newer Windows versions?
Since this will potentially be blocking users from using our product. Is there a way for our app to opt out of the hooking performed by LavasoftTcpService64.dll? Uninstalling Web Compantion will not always remove this dll, so users will not always have a workaround for the problem.
With kind regards
Please sign in to leave a comment.