scottgus1 wrote:Re "Application SID does not match Conductor SID", I found several results discussing MSI in context of this problem, which is the installer system, not Virtualbox itself. Does MSI get involved when the normal Virtualbox application is started? I haven't ever read that it does, only when Virtualbox is being installed. Almost as if the install is still being processed, rather than Virtualbox itself running. Of course I'm probably misunderstanding it.
You might be close this time.
I don't know much about this either, but I could speculate a bit as follows: Let's assume that the
VBoxSVC is already running, started by a (possibly elevated) user A (e.g. System via
Task Scheduler,
AutoStart, whatnot?). Then (elevated) user C installs a new VirtualBox version. At the end of the installation,
RestartManager is triggered, whose task is to try and replace running software components, to avoid an otherwise necessary reboot.
RestartManager wants to stop the running
VBoxSVC and start the new
VBoxSVC, but it recognizes that A != C (
Application SID !=
Conductor SID), leading to the warning in the
Windows Event Log. But I would expect this situation to be resolved after the next Windows reboot ...