I need a message pump that doesn't mess up my open window

Question

My application (the bootstrap application for an installer that I\'m working on needs to launch some other applications (my installer and third party installers for my installer

Answer 1

I think your problem is in WaitForSingleObject

Looking in MSDN you see this

Use caution when calling the wait functions and code that directly or indirectly creates windows. If a thread creates any windows, it must process messages. Message broadcasts are sent to all windows in the system. A thread that uses a wait function with no time-out interval may cause the system to become deadlocked. Two examples of code that indirectly creates windows are DDE and the CoInitialize function. Therefore, if you have a thread that creates windows, use MsgWaitForMultipleObjects or MsgWaitForMultipleObjectsEx, rather than WaitForSingleObject.

In my code in the message pump use use MsgWaitForMultipleObjects (doc).

With a call this call.

MsgWaitForMultipleObjects(1, &ProcessInfo.hProcess, FALSE, 100, QS_ALLEVENTS); 

This should stop your problem with the resources dissapearing.