Yea, WinHook only makes it simpler to us RegisterShellHookWindow and SetWinEventHook DLLs. It can still be tricky to find the right events to monitor for.
Also, the operating system only knows what the windows tell it and not all windows play nice and follow protocol. And some of the worse windows are the ones built into Windows. I assume to get some special cooler functionality.
For me in Windows 11 the calculator opening and closing works fine if I use "CalculatorApp.exe" and watch for 1 and 2. But there have definitely been cases where I could only figure out what code to use by monitoring them all and picking one that always seemed to occur. There are cases with hi/low bits that are combined in a code which is where you ended up with stuff like 32,772. I see code 32,772 pretty often when a window is activated, on the other hand, I have no idea what code 53 is for.
Also, it could be something with how you are opening the calculator. From the event log, it looks like it is opening, closing, and opening again when you open it. I would just open it manually without a hotkey to test it.
FG