🚀 go-pugleaf

I have an application that used to shutdown gracefully if it was running 
when Windows shutdown.  Now I noticed that my application shuts down, but 
it also seems to cancel the Windows shutdown.

I trap/handle the WM_QUERYENDSESSION and WM_ENDSESSION messages to save my 
files and close.  I set the Msg.Result = 1 (ok to shutdown) in each handler 
so Windows should continue to shutdown.  It use to work...

I did some research and apparently any 3rd party component that is using 
AllocateHWnd and not calling DefaultWindowProc in the handler method can 
cause this problem. In that case the handler method is answering 0 to 
WM_QUERYENDSESSION which tells Windows to cancel the shutdown. 

This is a BIG application and I use a lot of components. I created a new 
project and have been adding components one at a time to see what kills the 
shutdown.  With an almost 5 minute reboot cycle this is EXTREMELY time 
consuming. There must be a better way?

Does anyone know any way of "tracing" a message so I can see where 
Msg.Result is being set incorrectly?

I also created a test application that sends the WM_QUERYENDSESSION and 
WM_ENDSESSION messages to my app in an attempt to "fake" the shutdown, but 
it seems to report that my app is responding properly.

Something is going wrong but I am having trouble finding it.

Can anyone help?