A windows service will likely log events to the application event log. IF the event viewer is open when running an installer to upgrade a product that contains one or more services Then it is likely that a module will be in use by the event viewer. An MSI installer will, when upgrading such a service, want to overwrite the EXE or DLL module containing the Message Table resource. During the upgrade installation the restart manager detects that the event viewer (and its back end components) have this module open. For a full UI install this gives the user the option to have apps automatically shut down and restart - in order to overwrite modules that will be upgraded. This list includes the event viewer!! The Event viewer HOWEVER does not respond to the end session request. The module remains locked. The user MUST know that they should close the event viewer in order to avoid a reboot. Thats all fine and mightily inconvenient for a novice user who won't necessarily understand the messages displayed by the installer. WORSE still for an unattended silent install (quiet mode) as it will always result in a reboot. So although the event viewer might not be open much of the time I'm merely asking if there is any particularly good reason why the event viewer should not respond to the restart manager. To me it seems like laziness and bad manners not to and is detrimental to user experience.
