Issue

Alex
Software Development
StableBit DrivePool
2.X
Windows 8.1 (64 bit)
Public
Alex

The UI launch at the end is explicitly disabled in the MSI installer. The burn EXE engine sets LAUNCHUI=1 when it installs the MSI. You can achieve the same behavior by setting that property at installation time.

Here is the full command line that Burn uses:
  • Install:

    Applying execute package: DrivePoolApplication, action: Install, path: C:\ProgramData\Package Cache\{43053F4F-87D0-4459-A600-03896AC6F486}v2.2.766\StableBit.DrivePool.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" LAUNCHUI="1" INSTALLLOCATION="C:\Program Files\StableBit\DrivePool"'

  • Upgrade:

    Applying execute package: DrivePoolApplication, action: MinorUpgrade, path: C:\ProgramData\Package Cache\{43053F4F-87D0-4459-A600-03896AC6F486}v2.2.767\StableBit.DrivePool.msi, arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" LAUNCHUI="1" INSTALLLOCATION="C:\Program Files\StableBit\DrivePool\"'

  • Uninstall:

    Applying execute package: DrivePoolApplication, action: Uninstall, path: (null), arguments: ' ARPSYSTEMCOMPONENT="1" MSIFASTINSTALL="7" LAUNCHUI="1" INSTALLLOCATION="C:\Program Files\StableBit\DrivePool\"'

For StableBit CloudDrive, there is an additional property called STOPSERVICE. You can set it to 1 to stop the service at upgrade time (not recommended, as this will unmount all of the cloud drives). Settings STOPSERVICE=1 may avoid a reboot, if the driver was not updated.
Public
Alex

Test Group Policy Object (GPO) deployment of the new MSI files. Specifically, there is an issue with auto-starting the UI after the installation completes.