🚀 go-pugleaf

I'm curious if anybody knows how the Windows Task Manager (Win2K, XP) kills
a window when the "End Process" button is clicked?  The reason I ask is I've
written an application which attempts to close all windows on the desktop by
calling DestroyWindow, passing the handle of the window to be closed as the
function's parameter.  For the most part, this works.  However, the instance
of Windows Explorer which controls the Windows shell will not close,
regardless of what API call I use.  In addition to DestroyWindow, I've tried
posting/sending a WM_QUIT and WM_CLOSE message to the window.  The WM_QUIT
does nothing (the icons on the desktop might blink a bit as if they're being
refreshed, but not much else), and the WM_CLOSE causes the "Are you sure you
want to log off?" dialog to appear (and that's not the behavior I desire).
The Windows Task Manager on the other hand, will kill any instance of
Explorer outright (regardless of whether it controls the desktop shell or
not), so it appears to use a function call that I'm not aware of to kill the
window.  Does anybody know how this is accomplished?

Thanks.