Manage OS Software Updates with FileWave

Keep operating systems current

---

FileWave collects Windows and Apple operating-system update information so you can create Software Update Filesets, test them with representative devices, and deploy approved updates on a controlled schedule. This workflow covers Windows, macOS, iOS, iPadOS, and tvOS.

Plan at least a pilot and production stage before creating update Filesets. Use representative hardware and operating-system versions in the pilot, including laptops that may be off network or on battery during the maintenance window. Confirm download, installation, restart behavior, and final inventory before moving the same tested Filesets to a broader group.

Create and deploy Software Update Filesets

---

Creating update Filesets in a Fileset Group and assigning that group through a Deployment gives you one repeatable path for new updates. Devices ignore update Filesets that do not apply to their platform or current operating-system state.

Your administrator account needs Manage Updates and Configure Automation Rules. Check these permissions in Assistants → Manage Administrators.

Create the update Filesets and Deployment:

1. In FileWave Central, open Software Updates.
2. Select the operating-system platform. Turn on Requested only to show updates that managed devices currently report as applicable. Select No fileset to hide updates that already have a Fileset.
3. Select the updates, right-click, choose Create Filesets..., and select the destination Fileset Group. Separate Windows and Apple groups make platform targeting and staged promotion easier to review.
4. Create a Deployment from the update Fileset Group to the intended Smart Group. For staged testing, create updates in a test Fileset Group first, verify the pilot, then move the same Filesets into the production group.
5. Select Update Model to commit the changes.

Before broad deployment, inspect the pilot devices in Client Info and confirm that each intended update is assigned, downloaded, installed, and no longer requested. Review failures by operating-system build and hardware model rather than repeatedly redeploying to the whole group. Devices that remain absent from the update view still need the independent inventory check described below.

Windows Client requirement: Do not assign FileWave 16-format Windows OS updates to Clients earlier than 16.0.0. During a transition, add FileWave Client Version begins with 16. to the Windows patch Smart Group and independently report on older Clients that still need an upgrade.

Remove obsolete pre-16 Windows update Filesets after confirming they are no longer assigned or needed. See OS Software Updates - Obsolete Filesets Cleanup for the guarded cleanup workflow.

A Deployment can contain update Filesets for more than one platform because a device skips updates that do not apply. In Client Info, Ignore non applicable Software Update Filesets hides assigned updates that the device does not need; clear it when you need to troubleshoot the complete assignment set.

A short or empty filtered list is not fleet-wide compliance proof. Requested only, platform, category, and Fileset-status filters intentionally omit records. Before declaring a rollout complete, run an Inventory Report for the target devices' operating-system build and FileWave Client version, then compare that device count with the update results.

Schedule Software Update Deployments

---

Software Update Filesets use the same Deployment scheduling controls as other compatible Filesets.

1. Open FileWave Central and navigate to Deployments on the left hand side of the window.
2. Create a new Deployment that contains your Windows or Apple patches and for the target use a Smart Group that is your Windows or Apple devices. You may have already done this earlier, and if you have this already then you can just edit that Deployment.
3. In the Properties for the Deployment you will see on the Options tab that you can decide when to Activate (Install) the patches. You can also set a Reboot deadline. If you re-use this Deployment for monthly patches then know that you'll need to keep changing these dates or else new patches will immediately be past their deadline after enough time passes. 
4. "Update Model" to save the changes.

Windows BIOS/UEFI firmware and driver updates

Windows Software Updates can include BIOS/UEFI firmware from certain OEMs, including Dell, HP, and Lenovo. Treat firmware separately from routine operating-system patches during testing because applicability and restart behavior vary by model.

The view can also include third-party drivers for monitors, audio devices, and peripherals. These updates may improve compatibility, but plan for their user and restart impact:

• Many of these drivers require a reboot to complete installation.
• Automatic deployment may result in unexpected restarts, potentially disrupting end-user workflows.

To maintain a smooth user experience and prevent unplanned reboots, you may want to deploy driver updates via Self-Service Kiosk instead of automatic enforcement.

Next Steps

Use the Best Practice Guide: Software Update Deployment (16.0+) to build staged Alpha, Beta, and Production groups, validate policy coverage, and track results.

Related Content

• Best Practice Guide: Software Update Deployment (16.0+)