Swif’s Windows Software Update Policy lets you automate and control how Windows devices receive patches, updates, and new features. By defining update deadlines, active hours, or automatic reboots, you can keep devices both secure and compliant with minimal disruption.
1. Creating a New Policy
In the Swif Admin Console, go to Device Management → Policy.
Click Create New Policy.
Select Windows Software Update Policy as your policy type.
Enter a Policy Name and (optionally) a Policy Description.
Configure your Settings (detailed below), then select Next to choose the devices or groups for this policy.
2. Core Policy Settings (Screenshot Order)
Allow Non-Microsoft Signed Update
What It Does: Permits Windows to fetch updates (e.g., drivers/firmware) from non-Microsoft sources.
Use Case: Helpful if your environment relies on OEM driver updates.
Branch Readiness Level
Field:
branchReadinessLevelDescription: Determines which update channel the device follows for Feature Updates.
Default:
16(Semi-annual Channel Targeted)Possible Values:
2– Windows Insider build (Fast) [1709+]4– Windows Insider build (Slow) [1709+]8– Release Windows Insider build [1709+]16– Semi-annual Channel (Targeted)32– Semi-annual Channel (pre-1903)64– Release Preview (Quality Updates Only)128– Canary Channel
Defer Feature Updates Period (Days)
What It Does: Delays major OS updates by 0–365 days.
Defer Quality Updates Period (Days)
What It Does: Delays monthly security/quality patches by typically 0–30 days.
Pause Feature Updates
What It Does: Temporarily halts new feature updates.
Pause Feature Update Start Time
What It Does: Sets when the device starts pausing feature updates.
Pause Quality Updates
What It Does: Temporarily halts monthly patches.
Pause Quality Update Start Time
What It Does: Specifies when to begin pausing monthly patches.
Active Hours Start / End
What It Does: Defines times when Windows avoids forced restarts for updates.
Allow Auto Update
What It Does: Lets Windows download and install updates automatically outside active hours.
Notice: Per Microsoft’s recent changes in Windows 10/11, the “Get the latest updates as soon as they’re available” toggle may be disabled or hidden. For more details, see Windows Update: “Get the latest updates as soon as they’re available” toggle disabled (Windows 10/11). This policy setting does not override Microsoft’s handling of that toggle, but ensures auto updates install once available via the standard Windows channels.
Scheduled Install Day / Time
What It Does: Schedules updates for a particular day/time each week/month.
Configure Deadline for Feature Updates / Quality Updates
What It Does: Mandates an install deadline (in days) after updates become available.
Configure Deadline Grace Period
What It Does: Grants additional days beyond the deadline for forced updates.
Allow Optional Content
Field:
allowOptionalContentDescription: Lets devices receive optional updates, such as driver updates or preview builds.
Possible Values:
0– Don’t receive optional updates1– Automatically receive optional updates (incl. CFRs)2– Automatically receive optional updates3– Users choose which optional updates to receive
Reboot Restriction
What It Does: Prevents forced restarts (e.g., if a user is logged on).
Update Notification Settings (if present)
What It Does: Controls how often Windows notifies users about pending reboots or updates.
3. Applying Your Policy
Click Continue after configuring the fields above.
Assign the policy to the appropriate devices or device groups.
Click Finish to apply. The targeted Windows devices will now follow these update rules.
4. Verifying Policy in Windows Settings
Optional Content
Settings → Update & Security → Advanced Options → Configured update policies
Look for references to optional updates (or the absence thereof).
Preview Builds / Readiness Level
Settings → Update & Security → Windows Insider Program
Confirm your assigned channel (Insider Fast, Slow, Release Preview, etc.) matches the Branch Readiness Level policy.
5. Best Practices
Test in a Pilot Group: Avoid wide-scale disruptions by deploying policies to a small set of devices first.
Balance Security and Stability: Don’t postpone patches excessively, but do allow some time for testing.
User Communication: Notify end users about potential reboots or any changes to the update process.
Check the Swif Console: Monitor devices for compliance or errors.
6. Troubleshooting & Support
Policy Conflicts: Previous MDM rules or Group Policy settings might override your new Swif policy.
Connectivity: Make sure devices remain online with an updated Swif Agent to apply changes promptly.
Further Assistance: Contact Swif Support if issues persist.