⬇️ Scroll for more ⬇️
FileWave 16.4.1 is now generally available and is the recommended release for the FileWave 16.4 branch. It carries the full FileWave 16.4 feature set and includes fixes based in part on feedback from customers who ran FileWave 16.4 through Early Access, along with updated third-party components.
If you are running FileWave 16.4.0 Early Access, you still need to upgrade to 16.4.1. The GA announcement and Beta setting do not update your installed version. Follow the hosted or on-premises upgrade steps below. You can keep the Beta channel enabled to continue participating in Early Access for FileWave 16.5. After installing 16.4.1, you can ignore the BETA indicator in FileWave Central; it reflects your package channel, not the release status. Switching back to Production is optional. The 16.4.1 release page explains how.
If you plan to manage devices on Apple's upcoming version 27 operating systems, including macOS 27 Golden Gate, install FileWave 16.4.1. Apple's final releases are not yet available, so final QA validation is still pending. FileWave 16.4.1 has been working with the current beta releases. We will update our compatibility guidance as soon as QA completes testing against Apple's final versions.
Staying on FileWave 16.3 or 16.2?
We also released FileWave 16.3.5 and 16.2.6. These maintenance releases include bug fixes and third-party library security updates. If you are not ready to move to FileWave 16.4, update to the latest maintenance release for the branch you are staying on: FileWave 16.3.5 or FileWave 16.2.6.
What is new in FileWave 16.4
Safer upgrades with less manual work
- Client Upgrades in Software Update can monitor, retry, roll back, and batch upgrades for clients already running 16.3.0 or later. Clients earlier than 16.3.0 still need the Client Upgrade Fileset bridge. See Upgrading FileWave Clients.
- Booster upgrades validate both upgrade status and installed version, with limited automatic retries when an upgrade fails.
- IVS upgrades can be managed from Central for on-premises Server deployments after the IVS reaches 16.4. Hosted customers with customer-managed IVS appliances use the version-specific one-line command on the FileWave 16.4.1 release page.
Deployments, automation, and administration
- The redesigned Deployment workflow brings Targets and Filesets into one view and adds installation type, timing, license assignment, tags, and new list columns.
- A new public Deployments API supports creating, listing, updating, and deleting Deployments.
- FileWave Central now manages macOS and Windows agent package builds on 16.4 Servers. Fileset upload validation, Model Update, Smart Group evaluation, IdP login through the system browser, and localized server messages also improve.
Apple and mixed-fleet management
- FileWave now supports managing Apple Vision Pro devices running visionOS.
- Apple management adds ASM/ABM API integration, the Profile Compatibility Report, richer MDM and DDM status details, DDM declaration import and export, Managed Migration Assistant, and VPP licensing improvements.
- Inventory now reports macOS and Windows application architecture, and Android EMM gains more system update, compliance, per-app update, and credential-provider controls.
Upgrading to FileWave 16.4.1
- FileWave-hosted customers: FileWave Operations will email you with the scheduled date and time for your Server upgrade to 16.4.1, whether or not you participated in Early Access. After Operations confirms completion, connect with FileWave Central and accept the matching upgrade when prompted. Follow the hosted post-upgrade guide for your remaining customer-managed components.
- On-premises/self-managed customers: Plan and perform your upgrade to 16.4.1 using the on-premises upgrade guide. Review the prerequisites and back up your Server. Upgrade the Server first, followed by Central and your other components. Direct upgrades to 16.4 require FileWave Server 16.0.0 or later; older Servers need an intermediate upgrade first.
- Clients earlier than 16.3.0: These clients do not block the Server upgrade, but they cannot use Integrated Client Upgrades. After upgrading the Server and Central, use Inventory to identify them and deploy the Client Upgrade Fileset bridge as needed.
- iPhone and iPad Kiosk: Acquire and sync enough free FileWave Kiosk licenses in ASM/ABM before moving managed devices to the automatic-updating Kiosk. Review Automatic updating of iOS/iPadOS Kiosk.
View FileWave 16.4.1 release details