[BUG] Mirth Connect 4.5.0 unattended installation does not start Mirth Connect Service and Mirth Connect Server Manager

[RockyMM]

Describe the bug
Trying on a fresh Windows 10 VM, Mirth Connect 4.5.0 unattended installation does not start Mirth Connect Service and Mirth Connect Server Manager.

To Reproduce
I am starting the installation with the following options:

Start-Process -Wait -FilePath ".\mirthconnect-4.5.0-x64.exe" `
 -ArgumentList "-q", "-console",`
 "-splash MirthInstallationProgress", "-alerts",`
 "-varfile response-connect.varfile"

Contents of the response file:

# install4j response file for Mirth Connect 4.5.0.b3012
dir.appdata=C\:\\Program Files\\Mirth Connect\\appdata
dir.logs=C\:\\Program Files\\Mirth Connect\\logs
executeLauncherAction$Boolean=true
fileChooser=
http.port.new$Long=8080
https.port.new$Long=8443
installServiceAction$Boolean=true
key=
mySelection$Integer=-1
password.minlength.new$Long=0
password.minlower.new$Long=0
password.minnumeric.new$Long=0
password.minspecial.new$Long=0
password.minupper.new$Long=0
showFileAction$Boolean=false
sys.adminRights$Boolean=true
sys.component.1357$Boolean=true
sys.component.2047$Boolean=false
sys.component.31$Boolean=true
sys.component.33$Boolean=true
sys.installationDir=C\:\\Program Files\\Mirth Connect
sys.languageId=en
sys.programGroupAllUsers$Boolean=true
sys.programGroupDisabled$Boolean=false
sys.programGroupName=Mirth Connect

Expected behavior
When doing a manual install, the service is automatically started and the server manager is available in the system tray.

Actual behavior
When doing a manual install, the service is installed but not started and the server manager is not available in the system tray.

Environment (please complete the following information):

• OS: Windows 10
• Java Distribution/Version Microsoft OpenJDK 21
• Connect Version 4.5.0

Workaround(s)
Issuing post install steps such are Start-Service and starting the mcmanager.exe.

[RockyMM]

I compared installation.log from manual and silent installations. I've found that manual installation contains these additionally:

[INFO] com.install4j.runtime.beans.actions.services.StartServiceAction [ID 167]: Execute action
       Property executable: null
       Property launcherId: 144
       Property serviceName: null
       Property autostartOnly: false
       Property rollbackSupported: true
       usedExecutable: C:\Program Files\Mirth Connect\mcservice.exe
       previous state false
       Execute action successful after 133 ms
[INFO] com.install4j.runtime.beans.actions.finish.ExecuteLauncherAction [ID 170]: Execute action
       Property arguments: null
       Property launcherId: 160
       Property rollbackSupported: false
       execute directly
       Execute action successful after 587 ms

[tonygermano]

In your expected and actual behavior, did you mean to say silent install instead of manual install?