Background: I have a service that will be running regardless of which features the user has selected. If the user installs some features and then later changes the installed features by running the installer in maintenance mode (add/remove features), then the service does not appear to be shutting down. That means that any time the user adds or removes features, the installer prompts them to reboot (some files that the installer uses are being used by the service). I've tried marking every file with the don't replace check box, but it still asks for a reboot. If I stop the service and then do the add/remove then it does not ask for a reboot.
My question is can I get the installer to stop a service when it adds or removes features, without running the external program "net STOP" to control the service?
Stop service on Maintenance
Who is online
Users browsing this forum: No registered users and 32 guests