Hi all,

We too have seen the 1500 error at times and it most always seems to be tied to Windows Update in some form or another.  There may be other causes, but for us it looks like Windows Update.  It is annoying as Microsoft doesn't seem to handle it all that gracefully.  The install seems to be OK until the turnover to the execute sequence.  Then you get the error message.  I would think they should detect that right up front, which is what I would try to do.

I was thinking of running a custom action to look for a TrustedInstaller process.  If running set property and use as launch condition.  This might help avoiding the annoying message and help users sort through the issue first - complete Windows Updates, reboot, etc.

If it bypasses this detection and still gets the error, then we can support and troubleshoot the registry entry cleanup, etc.

Just wondering if you think the TrustedInstaller detection might work. ??

Thoughts, pointers, guidance appreciated!


Thanks in advance!!

0 Comments   [ + ] Show Comments


Please log in to comment


I don't see why that wouldn't work. Personally, I'd test for whether or not the 'Windows Module Installer' service was started, although I guess they're ultimately the same thing.

>Windows Module Installer
Why call it that, when there's already a service called 'Windows Installer'?!?! Why not 'Windows Update Helper' or something similar? Bizarre...Oh wait, I know. As I believe I've said before, Microsoft...logic ==> the ultimate non-sequitur!
Answered 01/29/2015 by: VBScab
Red Belt

Please log in to comment
It should work fine. I ran into a similar problem caused by Active Setup running an MSI repair coincident with another MSI process being kicked off by the software distribution system.  By looking in task manager, any active MSI install resulted in at least two instances of msiexec and normally three. Once the install was complete, the number of msiexec processes was one or zero.  I therefore wrote some code in Winbatch which would monitor the number of instances of msiexec in the task list and only allow the active setup process to run an MSI installer once any other installations had finished.  I therefore see no reason why your proposed solution would not work as well.
Answered 01/29/2015 by: EdT
Red Belt

Please log in to comment

I am able to detect the TrustedInstaller process and throw up a launch condition message if running to stop our install from proceeding.  However in testing around this, I was able to get the install to run through to completion while a TrustedInstaller process (SYSTEM) running.  I would have expected to encounter the 1500 error.  So, I guess my hypothesis that TI is causing the 1500 error at times is false.

On my test image, Trusted Installer was running then I went in to turn off Windows Update processing.  I did this so tons of updates wouldn't run if I had to restart during testing.  Maybe that messed with Microsoft 'flow' somehow.


Answered 01/30/2015 by: Superfreak3
Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity