Appaloosa lets you manage how Windows software updates are delivered to your managed devices. You can pin devices to a specific Windows version, control Insider Preview builds, defer updates by a number of days, set an enforcement deadline, and choose when devices are allowed to restart.
All settings are located on the Configuration tab of your Windows managed configuration, in the Update card. The card is organised in three sections:
A shared section with version pinning, Insider Preview builds and active hours.
A Feature updates section — the major Windows updates released about once a year (for example moving from 22H2 to 23H2).
A Quality updates section — the monthly security and bug-fix updates (Patch Tuesday).
How it works
As soon as the device applies the policy, Windows handles update download, installation and restart according to the rules you set.
A typical lifecycle for an update on the device:
During the defer period, the update is hidden from the device.
After the defer period, Windows downloads and installs the update.
If a restart is required, Windows tries to schedule it outside the configured active hours.
After the deadline, Windows ignores active hours and forces the restart.
An optional grace period gives the user a few extra days to save their work before the forced restart actually happens.
Shared settings
Insider Preview builds
Controls whether the device can join the Windows Insider program and receive preview builds.
Block — Preview builds are not available on the device.
Block after release — Preview builds are blocked once the next major release is public; useful for piloting a release before it ships.
Allow — the user can opt into Preview builds.
Target OS version
Pins the device family to a specific Windows version.
None — no restriction; the device can move freely between Windows 10 and Windows 11 (subject to hardware compatibility).
Windows 10 — keeps the device on Windows 10 until end of service.
Windows 11 — moves the device to Windows 11 (or keeps it there).
Target release version
Pins the device to a specific feature update of the chosen Windows version, for example 23H2. Windows will move the device to that version (if it is on an older one) and keep it there until end of service or until you change this setting.
Leave empty to let the device follow the normal feature-update cadence.
Active hours start and end
Defines the window during which Windows avoids automatic restarts after an update. The user can keep working during these hours without being interrupted by a sudden restart.
Accepted values: 0 to 23 for both start and end (24-hour format).
On the device: Settings > Windows Update will reflect the active-hours window. Outside of it, Windows is free to schedule a restart to finish installing an update.
Feature updates
Major Windows updates released about once a year (e.g. 22H2 → 23H2). The same four fields exist in the Quality updates section, but with shorter ranges.
Defer (in days)
Number of days the device delays receiving a new feature update after Microsoft makes it available, giving you time to validate a release before users see it.
Accepted values: 0 to 365 days.
Deadline (in days)
Number of days after the update has been offered to the device before Windows installs and restarts regardless of active hours.
Accepted values: 0 to 30 days. (7 days is the recommended configuration.)
Grace period after deadline (in days)
Minimum number of days between the deadline being reached and the actual forced restart. This gives the user a buffer to save their work after seeing the deadline notification.
Accepted values: 0 to 7 days. (2 days is the recommended configuration.)
Automatically reboot
On — once the deadline (and grace period) is reached, Windows restarts the device automatically to finish installing the update.
Off — the restart is deferred until the user manually restarts or the next scheduled restart window.
Quality updates
Monthly security and bug-fix updates (Patch Tuesday). The fields work the same way as Feature updates, with shorter ranges that reflect the monthly cadence.
Defer (in days)
Accepted values: 0 to 30 days.
Deadline (in days)
Accepted values: 0 to 30 days. (3 days is the recommended configuration.)
Grace period after deadline (in days)
Accepted values: 0 to 7 days. (2 days is the recommended configuration.)
Automatically reboot
On — Windows restarts the device automatically once the deadline (and grace period) is reached.
Off — the restart is deferred until the user takes action.
Notes
Each field can be locked from the default configuration so that all sibling Windows managed configurations inherit the same value and all your devices across all your configurations follow the same update policy. See Lock Configurations for details.
