Automated Windows OS Updates Policy

What

There may be Windows OS updates that you want to simply apply without needing to create a Fileset or manage in FileWave. This new option will allow you to set it and forget it. FileWave 16.2.0 introduces a new concept to simplify Windows OS patching. 

When/Why

If you have a very lightly managed environment or have certain updates that you always want to have applied then this option may be for you.

How

When you create a new Fileset in FileWave 16.2.0 or higher you can pick General -> Policy to create a FileWave Policy. In the below image you can see the options for the Windows Software Updates component of FileWave Policy. This type of Fileset can also be used for customizing the Kiosk appearance, Geofencing for Android, and Blocker Scripts

You will give the Policy a name on the General section and then go to the Windows Software Updates section and set the rules. Anything that matches will apply. 

When setting this up consider the example below. For any update where "Cumulative" is in the name, the update MUST be Critical, the update may or may not reboot, and the update is ONLY an update of the two categories; Critical updates OR Security updates. 

FileWave Admin 2025-09-23 09.21.11.png

Starting in FileWave 16.3, updates deployed through this Windows Software Update Policy are labeled Triggered by Policy in the Software Update status view in FileWave Central and FileWave Anywhere, and that status is also recorded in inventory.

You can also confirm that the policy itself is active on the device in Client Info > Policies, as shown below.

FileWave Client Info showing an active Windows Software Update Policy applied to a Windows device

You can also deploy updates with finer control by following the guidance in Best Practice Guide: Software Update Deployment (16.0+)


Revision #11
Created 2025-07-03 14:04:22 UTC by Josh Levitsky
Updated 2026-04-12 16:47:59 UTC by Josh Levitsky