0

updater: document legacy support for the runtime mode

Bug: 1064792
Change-Id: I63e76c8564112b743024ee3fcd2cb6c19d222844
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5238016
Commit-Queue: Sorin Jianu <sorin@chromium.org>
Auto-Submit: S Ganesh <ganesh@chromium.org>
Commit-Queue: S Ganesh <ganesh@chromium.org>
Reviewed-by: Sorin Jianu <sorin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1252272}
This commit is contained in:
S. Ganesh
2024-01-25 19:36:31 +00:00
committed by Chromium LUCI CQ
parent 9b9798d688
commit 98719ac10d

@ -448,6 +448,17 @@ The updater removes the following Omaha registrations:
registry at `HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run`.
* Removes the Omaha Core and UA tasks.
#### Runtime mode (Windows)
Similar to Omaha, the updater supports command lines of the form:
`UpdaterSetup.exe /install "runtime=true"`
`UpdaterSetup.exe /install "runtime=true&needsadmin=false"`
`UpdaterSetup.exe /install "runtime=true&needsadmin=true"`
The "runtime" argument in the tag tells the updater to install itself and stay
on the system without any associated application. The updater will stay on for
at least `kMaxServerStartsBeforeFirstReg` wakes. This feature is used to expose
the COM API to a process that will install applications via that API.
### Installer User Interface
During installation, the user is presented with a UI that displays the progress
of the download and installation. The user may close the dialog, which cancels