Hi Eusebiu,
I ran into this while trying to do something sort of crazy I suppose, but I've since changed by approach, so we don't need to worry about it now.
Basically, if you create a basic project with Enhanced UI enabled and run it under the SYSTEM account, you will see one instance of the bootstrapper get launched, then a second one, which eventually exits, but the first one never does. No UI is ever displayed and there is no notification from the OS that a service is trying to display a UI. You'll see two separate MSI logs for the embedded MSI. If I put a GP wrapper MSI around that, I notice that the embedded original MSI gets called differently somehow and the UI is displayed through the "Interactive Services Detection" mechanism where you switch over to the SYSTEM desktop, and the bootstrapper does not hang in that case.
In the first scenario above, I noticed that the UI sequence would run, and I was trying to take advantage of that to do some things during a silent install that must happen before the main MSI runs (like uninstalling a legacy MSI and installing some prereqs). I've since switched my approach to a custom EXE as a pre-install prereq to do that work, so I'm not concerned about this behavior, but it does seem like something is a little wonky with it.

FOLLOW US
Get the latest news in Application Packaging