Unattended/automated operation
InControl includes scriptable command-line switches to perform and automate its operation.

• control ‑ places Windows Update under the user's control. It creates, sets or modifies six (6) Registry entries which cause Windows Update to target a specific Windows version and feature release. Since, by default, this will be the current version and feature release, this will prevent Windows Update from changing anything. Entries are also created to suppress, to whatever degree is possible, unwanted and unnecessary update and upgrade status messages. This command's operation can be altered with the version and feature options (see below). Note that important monthly Security Updates will never be prevented.
• release ‑ completely releases Windows Update from the user's control and restores its normal operation. It deletes the same six (6) Registry entries which were created when Windows Update was placed under control, thus freeing Windows Update to notify, obtain and possibly install updates and upgrades to Windows.
• version ‑ can be used to modify the “control” command to specify a different, non-current non-default targeted major Windows version (10, 11, etc.) See the example command line below.
• feature ‑ can be used to modify the “control” command to specify a different, non-current non-default targeted Windows Feature Release (20H2, 21H2, etc.) See the example command line below.
• showui ‑ displays the application's pop-up dialog which would otherwise be suppressed by the presence of either the “control” or “release” commands. The dialog displays the system's state after the command has been applied.

Typical command line:   InControl.exe control version 10 feature 21H2

In this example, if the system was already at version 10 feature 21H2, then “control” by itself would have the same effect. But if, for example, the system was at 21H1, this would request Windows Update to move to 21H2, where it would then remain forever until it was released from control.

Note that the presence of the command verbs triggers the program's actions. There is no need for additional “escape” prefixes such as ‘-’ or ‘/’ though they may be added if desired.