An update.
On a fresh Windows 10 install, with ESET endpoint running, installing (as domain admin manually, by msiexec /i file.msi /qn) a custom msi using the online wizard, produced the following:
* 7.0.0.3 host seems installed
* No ru host service exists
* The following were logged under %programdata%\remote utilities\install.txt
12-04-2021_12:05:18#T:SilentInstall: installation 69110
12-04-2021_12:05:18#T:SilentInstall: NTSetPrivilege:SE_DEBUG_NAME:false. OK
12-04-2021_12:05:18#T:SilentInstall: OpenService: service not found. OK
12-04-2021_12:05:18#T:SilentInstall: CreateService. OK
12-04-2021_12:05:18#T:SilentInstall: finished
12-04-2021_13:34:55#T:SilentInstall: uninstallation 69110
12-04-2021_13:34:55#T:SilentInstall: NTSetPrivilege:SE_DEBUG_NAME:false. OK
12-04-2021_13:34:55#T:SilentInstall: service found, removing
12-04-2021_13:34:57#T:SilentInstall: installation 70003
12-04-2021_13:34:57#T:SilentInstall: NTSetPrivilege:SE_DEBUG_NAME:false. OK
12-04-2021_13:34:57#T:SilentInstall: service found, removing
12-04-2021_13:34:58#T:SilentInstall: finished
This is quite similar to what I saw in my previous post. There's something I do not understand though: why is the installer removing the service, right after installation of 70003 has started? Essentially considering that there
is a service to remove!
If I understand your log correctly, the 69110 service was removed at 13:34:55. Between that time and 13:34:57 obviously a service was installed and subsequently deleted. It's not as though as an error that came up. It's as if the installer decided to roll back for some reason.
Is there some way I can enable a debug output here?