Solution:

Check the Windows Event Viewer If it indicates that the "Application SID does not match the Conductor SID" then I found the associated note. Event 10010 the error ”Application SID does not match Conductor SID” will be generated whenever the user account the service is being run under does not match the user account used to launch the setup instance. The term “Conductor” refers to the MSI setup engine. It also appears that if the setup is executed with elevated permissions (Run As Administrator), then the SID check is bypassed. This behavior is by design and is intended to prevent the malicious restarting of critical system services. ********************************* For example: If you have MsiRunningElevated=1(in msi log), this should be the case because services are automatically elevated when run under an administrative account. In the routine that marks a service for restart, there are a half-dozen API calls that could fail. So I don't think there is anything we can do other than meet the above conditions.