I have an initialization program which registers some COM components for our application. The registration simply invokes REGSVR32.EXE, waits for it to terminate (using WaitForSingleObject) and then continues. Although this used to work ok, the call to WaitForSingleObject now nolonger returns! This appears to happen even after REGSVR32 has *successfully* registered a component.
At present I have a hack which is working ok - using MsgWaitForMultipleObjects instead of WaitForSingleObject, and processing any messages that appear for the process. This seems to keep REGSVR32.EXE happy, but I'm interested to know why suddenly it's not working as before, despite no major changes to the code or Windows installation.
