Windows 32-bit FileWave Client End of Life
What changed
AsFileWave 15.3.0 ended support for 32-bit Windows because the new desktopWindows kioskKiosk forintroduced in that release depends on 64-bit libraries. During that initial transition, the FileWave Client process (fwcld) remained 32-bit, so Fileset deployment and script execution behavior did not change solely because of the Kiosk update.
Who is affected
Devices running a 32-bit edition of Windows iscannot based on 64bit libraries,use FileWave 15.3.0 willor notlater beas a supported onmanagement baseline. Identify and upgrade or replace those devices before upgrading their FileWave Client.
Current guidance
Use a 64-bit edition of Windows 32bitfor platforms.current FileWave Agent (fwcld) is currently still a 32bit executable, meaning there is no change in how Filesets are deployed,Client and scriptsKiosk aredeployments. executedThis withpage this initial change.
When/Why
Windows 32bit has long been onrecords the way out. Because it can only handle 3.5Gb of RAM there has long been a lot of progress to get away from it by customers.
How
At first the Kiosk in FileWave 15.3.0 willsupport be 64bit, and in a future releaseboundary; the entireold agentforward-looking willagent-transition transition.timeline Movingno tolonger adescribes 64bitthe applicationcurrent is expected to happen later this year.product.