Uninstall the FileWave Client on macOS
Use these uninstallers when you need to remove the FileWave Client from macOS computers before archiving, deleting, selling, or otherwise removing those devices from FileWave management.
Remove the client while the Mac can still receive Filesets. After the FileWave Client is removed, the Mac will no longer check in to the FileWave Server through the client.
Before you begin
- Test the uninstaller on a small pilot group before broad deployment.
- Confirm whether the Mac is also MDM enrolled. Removing the FileWave Client does not remove the MDM enrollment profile.
- If the Mac should leave management entirely, handle the MDM enrollment separately. For Automated Device Enrollment devices with a non-removable MDM profile, the local FileWave Client uninstaller cannot remove that profile.
- Do not run this on a FileWave Server unless you understand what is installed on that Mac. The script is intended to remove the FileWave Client and client-side data.
Downloads
| Option | Download | Use when |
|---|---|---|
| Fileset | FileWaveUninstallermacOSv4.1.2-kiosk-process-fix-fileset.zip | You can still deploy Filesets to the Macs being removed. |
| Standalone script | FileWaveUninstallermacOSv4.1.2.sh.zip | You need to run the uninstaller locally or through another tool. |
Version 4.1.2 keeps the version 4.1 behavior for clients that no longer use FileWave VNC, corrects the FileWave Kiosk app path, and terminates the running FileWave Kiosk process before removing the app bundle.
Fileset directions
- Download the attached Fileset and unzip it.
- Drag the unzipped Fileset into the root level of the Filesets tab so it is not accidentally deployed from inside another folder.
- Associate the Fileset to the Macs that should be removed from FileWave management.
- Run a Model Update.
- Confirm the uninstall has had time to run on the targeted Macs.
- Archive or delete the FileWave records as appropriate, then run another Model Update.
Standalone script directions
- Download and unzip the standalone script.
- Run the script locally as root with
zsh:
sudo /bin/zsh ./FileWaveUninstallermacOSv4.1.2.shDo not run the script with sh. The script uses zsh process substitution. Running it with sh can produce this error:
syntax error near unexpected token `<'
done< <(pkgutil --files com.filewave.fwcld.pkg)If you see that error, run the current standalone script again using sudo /bin/zsh, not sh.
MDM enrollment note
This uninstalls the FileWave Client, but it does not remove an MDM enrollment profile. If the Mac is still MDM enrolled, FileWave may still have an MDM channel to the device, and a configured custom PKG can reinstall the FileWave Client during enrollment or later MDM-driven installation.
If the Mac is enrolled through Apple Business Manager or Apple School Manager using Automated Device Enrollment and the MDM profile is configured as non-removable, the user cannot remove that profile locally. Use one of the supported MDM/ADE offboarding paths instead:
- Send the MDM command to remove the enrollment profile while the device is powered on, online, and still enrolled. In FileWave, archiving an applicable Apple MDM device can send that removal command depending on the enrollment state and the setting in Preferences > Mobile.
- Wipe the Mac when the profile cannot be removed or when the device is being fully reset.
- If the Mac is leaving the organization, release it from Apple Business Manager or Apple School Manager. If it should remain owned by the organization but move to another MDM, change the Automated Device Enrollment assignment before wiping and re-enrolling.
Do not treat SIP-disable/manual profile-store deletion as a normal offboarding method. Use the MDM command, wipe workflow, or FileWave Technical Support for exceptional recovery cases. See Archiving Clients, Wipe Device for macOS, and Apple's device management profile removal guidance.
Uninstaller scope
The macOS uninstaller uses the FileWave Client package receipt, com.filewave.fwcld.pkg, to identify installed client components. That works best for a standard FileWave Client installation. It may not perfectly describe devices that were upgraded several times, modified manually, or changed by older upgrade Filesets. Those devices can have files or folders that are newer than the package receipt, or older files that are no longer part of the current client.
The script forgets the FileWave Client package receipt at the end of a successful run. If you run the script again after that, it may report that the package receipt is not found and exit without doing additional work.
You can check which FileWave package receipts macOS currently knows about with:
pkgutil --pkgs | awk '/com.filewave/ {print}'The client receipt is com.filewave.fwcld.pkg. FileWave Server, Booster, Admin, and other FileWave components may have their own package receipts. The uninstaller checks for some shared FileWave components before removing shared resources, but it is still a client uninstaller. Review FileWave Server or multi-role Macs carefully before using it.
If FileWave Kiosk remains visible
Version 4.1.2 removes /Applications/FileWave Kiosk.app and also attempts to terminate a running FileWave Kiosk process before removing the app bundle. If a menu bar icon remains immediately after uninstall, confirm that the device ran version 4.1.2 or newer, then log out or restart the Mac to clear any stale menu bar item that was already loaded in the user's session.
If the FileWave Kiosk app bundle or process remains after running version 4.1.2 and restarting, collect the uninstall output and contact FileWave Technical Support.