That is very interesting. Thanks for the details. Code running in a service context would typically call LoadUserProfile prior to trying to access the user areas of the registry. The notes on this function provides more details.
Another area where I would expect issues is related to the fact that windows messages do not cross winstation boundaries (however named pipes and memory mapped files are alternative methods of interprocess communication that do cross winstation boundaries). Code running in a service context is running in the 'services' winstation if launched under a system account and in its own separate winstation/desktop if launched under a user account. Any process that gets spawned by the service code needs to specify its own winstation/desktop in the STARTUPINFO.lpDesktop attribute if it expects to get or send any windows messages to or from the spawned process. I would be interested in hearing the results. I think I do not fully understand the use case where using a service to launch a setup is beneficial, but I would like to help if I knew how. -- View this message in context: http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Managed-Bootstrapper-fails-to-load-Errror-0x80040150-tp7591316p7591362.html Sent from the wix-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ WiX-users mailing list WiX-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wix-users
