Windows - Software - Uninstall JAWS 2022

What the JAWS 2022 uninstaller does

This Automox Worklet™ identifies and removes Freedom Scientific JAWS 2022 from Windows endpoints by querying the system registry and executing targeted uninstall operations. The Worklet handles three related components: the JAWS 2022 application itself, the JAWS Training Table of Contents DAISY Files, and FSReader 3.0.

Detection runs against both 64-bit and 32-bit registry locations so the policy is safe on every Windows system architecture. The Worklet reads HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall on 64-bit Windows and HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall for 32-bit applications hosted on a 64-bit OS. Each subkey's DisplayName is matched against the JAWS 2022 product strings, so the policy works against every install variant the Freedom Scientific bundler produces.

Remediation uses the path each component was packaged with. JAWS 2022 ships as an EXE installer, so the Worklet downloads JAWS_2022.exe from the Automox cache and invokes it with /Type SilentSharedUninstall. The Training Table of Contents ships as an MSI, so the Worklet resolves the IdentifyingNumber via a Win32_Product CIM query and calls msiexec.exe /x <guid> /qn. FSReader 3.0 ships its own UninstallFSReader.exe binary, which the Worklet runs with /S from C:\Program Files\Freedom Scientific\FSReader\3.0\. Each path is silent so the end user is not prompted.

Why uninstall JAWS 2022 across the fleet

JAWS is a per-seat licensed product, and accessibility software typically follows the user, not the endpoint. When a JAWS user changes role, returns a laptop, or migrates to a newer JAWS release (JAWS 2023, JAWS 2024, JAWS 2025), the 2022 installation lingers on the original endpoint and continues to hold a slot in vendor reporting. Manual cleanup is slow because the bundle leaves three separate entries in Add or Remove Programs and a 1–2 GB footprint under Program Files. The components also self-register screen-reader hooks that conflict with the newer JAWS major version if both are installed side by side.

Scheduling this Worklet against the upgrade cohort runs the three-component removal sequence unattended on every Windows endpoint in scope: vendor uninstall of JAWS 2022 via JAWS_2022.exe /Type SilentSharedUninstall, msiexec /x /qn against the Training Table of Contents MSI ProductCode, and UninstallFSReader.exe /S for FSReader 3.0. License seats return to the Freedom Scientific portal as each install clears, and the next evaluation pass gives the help desk a single compliance view confirming no JAWS 2022 instance remains in production after the upgrade window closes.

How JAWS 2022 removal works

1. Evaluation phase: The Worklet opens the LocalMachine Registry64 view and enumerates SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall on 64-bit endpoints, then scans HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall for 32-bit entries. Each subkey's DisplayName is matched against the literal string "JAWS 2022" using a -like wildcard. If any match is found the script writes "JAWS 2022 was found. Flagging for remediation." and exits 1. On 32-bit Windows endpoints the script scans HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall directly. A clean endpoint exits 0 with "JAWS 2022 was not found. Endpoint is compliant."

2. Remediation phase: A CheckForInstalls helper re-runs registry detection for each of the three component product strings (Freedom Scientific JAWS 2022, Freedom Scientific JAWS Training Table of Contents DAISY Files, Freedom Scientific FSReader 3.0). When JAWS 2022 is detected, Uninstall-JAWS2022 pulls JAWS_2022.exe from https://api.automox.com/api/cache?cmd=downloadLatestVersion&name=JAWS_2022&os=Windows&arch=64 with System.Net.WebClient, runs it with /Type SilentSharedUninstall, and removes the installer with Remove-Item -Force -Recurse. When the Training Table of Contents is detected, Uninstall-JAWSTraining resolves the MSI product code via Get-CimInstance Win32_Product and invokes msiexec.exe /x <guid> /qn. When FSReader 3.0 is detected, Uninstall-FSReader runs the vendor's own UninstallFSReader.exe with the /S silent switch. Each function returns a boolean to the caller, and the script exits 1 only if the primary JAWS uninstall fails.

JAWS 2022 uninstall requirements

• Windows 10 or later, or Windows Server 2016 or later, with PowerShell v4 or later available

• Local administrator privileges (the Automox agent context already meets this)

• Outbound connectivity to api.automox.com so the remediation script can download the JAWS 2022 uninstaller binary

• Read access to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall for the evaluation phase

• FSReader removal depends on C:\Program Files\Freedom Scientific\FSReader\3.0\UninstallFSReader.exe being intact; reinstall FSReader first if a partial removal has corrupted that binary

• Win32_Product CIM class enabled for MSI inventory (default on supported Windows versions; required for JAWS Training MSI GUID resolution)

• JAWS 2022, JAWS Training Table of Contents, or FSReader 3.0 must be installed for remediation to take effect; clean endpoints exit early as compliant

Expected state after JAWS 2022 removal

After remediation completes, JAWS 2022, the JAWS Training Table of Contents DAISY Files, and FSReader 3.0 no longer appear in Settings > Apps > Installed apps or in the legacy Add or Remove Programs view. The Program Files\Freedom Scientific\JAWS\2022 directory is removed, the C:\Program Files\Freedom Scientific\FSReader\3.0 directory is removed, and the corresponding registry subkeys under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall are gone. Exit code 0 from the remediation script indicates the JAWS 2022 primary uninstall succeeded; exit code 1 indicates the JAWS_2022.exe vendor uninstaller failed and the next evaluation pass will reflag the endpoint.

Validate by running Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object { $_.DisplayName -like '*JAWS 2022*' } in PowerShell; the query should return no rows. Repeat against the Wow6432Node path for 32-bit coverage. For audit evidence, capture the Automox activity log entry plus the exit code, and confirm the Freedom Scientific license portal shows the seat as returned within the vendor's reconciliation window. Subsequent policy runs report the endpoint as compliant without further remediation because the evaluation phase finds no matching DisplayName entries.