This could also be a known problem with Install Monitor. If this package is a 16bit install then the issue is related to our logging and the initialization of NTs virtual dos machine (NTVDM). In the meantime, another workaround is to make sure NTVDM (and wowexec) is already loaded before monitoring and then begin monitoring. This can be done by launching a 16 bit app - even just launching the 16 bit setup and shutting it down. You can check task manager to make sure these processes are running.