The way it seams to be supposed to work is that the SbieSvc.exe, from RunHandler2, invokes: You can use a tool like TaskExplorer with enabled ETW Monitoring and use the "hold" option (snow flake icon on toolbar) to view all processes running as well as started and terminated.Īnyhow, the fact that Start.exe does not even try to start "C:\Windows\system32\msiexec.exe /V", tells me that most likely a trigger for the service to be started has changed, or is missing entirely, and we need to find an other one. On 1903 it does not even try to start the msiServer. On 1809 when trying to install a msi file inside a sandbox, Start.exe starts an sandbox internal instance of that service. From 1809 to 1903 MSFT changed something around the "msiServer" service.
0 Comments
Leave a Reply. |