We have low but consistent failure rate of MSI in our clients. In most cases the simple fix of unregsiter-re-register (see below) works fine.
I am considering adding this fix to any installation on any machine. This is provided there is no risk associated for healthy machines.
Does anybody know if running the below on a healthy machine is safe? Is it safe for all versions of MSI and all OSs?

msiexec.exe /unregister msiexec /regserver
0 Comments   [ - ] Hide Comments


Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


Normally a reboot of the machine is required if you use the command "msiexec /unregister".
And another reboot is required if you use the command "msiexec /regserver". According to Microsoft.

Therefore adding this fix to any installation on any machine, as you said, would not be the conclusion...

Answered 09/10/2009 by: McRip
Orange Senior Belt

Please log in to comment
The only conceivable reason I can see that a reboot would be required after re-regsitering MSIExec would be if it were running at the time of registration. Even then I'd be dubious, since all it does is write its AppID etc to the regsitry.

If you want to know if it's safe, capture its execution and make a judgement.

Having said that, I would be equally dubious about adding such a command to your packages. If the client build is broken enough to require it, you'll most likely find every single subsequent issue laid at your company's door. Avoid.
Answered 09/10/2009 by: VBScab
Red Belt

Please log in to comment