Rollback and uninstall

Removal is a first-class path, and it restores prior state rather than deleting settings blindly. This page lists the removal motion on each platform, exactly what it restores, what the management tool removes separately, the order to do it in, and what remains afterwards.

The motion

The order

1. Remove the agent from the devices first, through the uninstall assignment.
2. Confirm on the endpoints that the service and, on Windows, the driver are gone and prior settings are back. The checklist at the bottom of this page is the confirmation.
3. Only then remove the certificate profile. Removing it earlier only adds a noisy half-covered interval; removing it after the endpoints are confirmed clean keeps the exit orderly, and the record shows one clean removal.
4. The device group and the app's assignment history remain in the management tool as an audit trail.

What Windows uninstall restores

The MSI stops the service, removes the exact recorded driver package where one was installed (it refuses to guess if the record is missing), then runs the agent cleanup:

1. Ends the companion process and removes its logon entries.
2. Sweeps every user profile's proxy setting, deleting it only where it points at Proxara's local configuration. A proxy a user or an administrator set themselves is untouched.
3. Restores AI-client configurations from the backups taken at install.
4. Removes every Proxara certificate from both the machine and user certificate stores.
5. Removes the Firefox enterprise-roots policy.
6. Replays the exact pre-install machine proxy state from the snapshot taken at install. If no snapshot exists, the setting is left untouched; removal never resets an administrator's proxy to direct.
7. Removes the agent's data under ProgramData and the managed configuration values. A detached finisher deletes the files the running service held open.

What macOS uninstall restores

In order:

1. Stops and removes the companion menu-bar app and its LaunchAgent.
2. Deactivates the system transport extension where one is present.
3. Restores every re-pointed AI-client configuration from the backups taken at install.
4. Removes the firm's CA certificate from the System keychain and from every user's login keychain, and deletes the on-disk certificate and key files.
5. Removes the Firefox enterprise-roots policy.
6. Removes the system proxy configuration, replaying each network service's captured prior state.
7. Removes installer artifacts, the agent's data directories, and the package receipts.
8. Removes the LaunchDaemon itself, last, so every earlier step runs under the service that owns the files.

What remains

• On the device: nothing the agent wrote, with one bounded exception. On macOS, the downloaded installer file in a user's Downloads folder can survive when macOS privacy controls deny the uninstaller access to that folder.
• Profile state the management tool delivered remains until the tool removes it, in the order above.
• In the firm's environment: the record the deployment produced, governed by the retention terms. At the end of a pilot that does not convert, Proxara deletes the environment's data and certifies the deletion in writing, per the Pilot Terms.

Verifying a removal

• The service is gone: the ProxaraAgent service absent on Windows, no agent process on macOS.
• On Windows, the driver is gone: no Proxara driver package remains in the Driver Store, and no Proxara filter remains in the networking stack.
• Proxy state is back: netsh winhttp show proxy on Windows shows the pre-install state; networksetup -getautoproxyurl on each macOS network service shows the prior state.
• No Proxara certificate remains: search the machine and user certificate stores on Windows, or Keychain Access on macOS.
• AI-client configurations match their pre-install contents.

Single-device validation ends with exactly this verification, so the firm has run the whole removal path once before any employee device carries the agent.