How to Uninstall the Abloomify Device Agent (Windows and macOS)

November 21, 2026

Abloomify Team

17 min read

Uninstall the Abloomify Device Agent: a laptop and a desktop monitor, each showing the agent removed with a green checkmark
This guide removes the Abloomify device agent, and the Abloomify Chrome extension if you deployed it, from Windows and macOS. It covers a single machine and fleet removal with Jamf Pro, Microsoft Intune, Configuration Manager (SCCM), Group Policy, and Rippling. Use it when a pilot or contract ends, or when you retire or re-image a device.
You do not need the Abloomify console or the original installer. Both removal scripts are on this page, so you can remove the agent even after your Abloomify subscription has ended.

Installing instead?

Start with the Windows install guide or the device agent overview, which links to every macOS MDM guide.

Contents

Before you start: the order matters

Every Abloomify install guide sets your device management tool to keep the agent installed. If you remove the agent while that is still in place, the tool can put it straight back. Work in this order:
  1. Stop deploying it by taking the devices out of the install assignment: the Jamf policy, the Intune app assignment, the Configuration Manager deployment, the Group Policy startup script, or the Rippling app.
  2. Remove the agent with the steps for your platform below.
  3. Remove the configuration profiles (macOS) and the Chrome extension policy, if you deployed them.
  4. Verify on one device.

Remove the agent from a Mac

The macOS agent is removed with the Abloomify uninstall script, the same script that ships inside the Abloomify installer package. Download it here: abloomify-uninstall-macos.sh. It is a plain shell script, so read it before you deploy it.
On a single Mac, run it from Terminal with an administrator account, while the Mac's user is signed in:
curl -fsSLO https://www.abloomify.com/downloads/abloomify-uninstall-macos.sh
sudo bash abloomify-uninstall-macos.sh
The script must run as root. It stops the agent, removes the app (/Applications/Abloomify.app), its launch agents, the self-update daemon, the package receipts, the Chrome helper files, and the logs, and it clears the device identity. On success it prints All components successfully removed and exits with code 0. Otherwise it lists what is left and exits with 1. When you run it by hand, it offers to restart the Mac; a restart is recommended but not required.
Then remove the Abloomify configuration profile (Baseline or Full) and, if you deployed it, the Abloomify Chrome extension profile from your MDM. The steps for each MDM are below.
The script leaves the updater's log folder and an empty support folder. To remove them too, run:
sudo rm -rf /Library/Logs/AbloomifyDeviceAgent "/Library/Application Support/Abloomify"

Remove the agent from Macs with Jamf Pro

Jamf runs policy scripts as root, so the uninstall script works as is.
  1. Stop the install policy. Open Computers > Policies, open your Abloomify install policy (for example Deploy Abloomify Device Agent), and remove the Macs from its Scope, or add them under Exclusions. If you followed the Jamf install guide, the policy is scoped to the Abloomify Not Installed Smart Group. A Mac rejoins that group once Jamf sees the agent is gone, and the policy installs it again if its logs are flushed or its frequency is changed. Exclude the Macs, or disable the policy, before you go further.
  2. Add the script. Go to Settings > Computer Management > Scripts and click New. Name it Uninstall Abloomify Device Agent and paste the contents of abloomify-uninstall-macos.sh on the Script tab. Click Save.
  3. Create the removal policy. Go to Computers > Policies and click New. Name it Remove Abloomify Device Agent. Under Triggers, select Login (so the script runs while a user is signed in), and set Execution Frequency to Once per computer. The Login trigger needs login events turned on in Settings > Computer Management > Check-In. Open the Scripts payload, click Configure, and add Uninstall Abloomify Device Agent. Scope it to the Macs you are removing, and click Save.
  4. Check the result. Open the policy's Logs. A successful run prints All components successfully removed and exits with code 0. A run that exits with 1 lists what is left; see Troubleshooting.
  5. Remove the profiles. Remove the same Macs from the scope of the Abloomify configuration profile (Baseline or Full) and the Chrome extension profile. Jamf removes a configuration profile from a Mac when the Mac leaves its scope.
To test it, sign out of a test Mac in the policy's scope and sign back in.

Remove the agent from Macs with Intune

  1. Stop the install. In the Intune admin center, go to Apps > macOS, open the Abloomify app, and under Properties > Assignments, remove the device group (or add it as excluded). This stops new installs. It does not remove the agent from Macs that already have it.
  2. Add the script. Go to Devices > macOS > Shell scripts (in newer versions of the admin center, Devices > Scripts and remediations > Platform scripts) and add a macOS script. Upload abloomify-uninstall-macos.sh and set:
    • Run script as signed-in user: No (the script must run as root).
    • Hide script notifications on devices: Yes.
    • Script frequency: Not configured (the script runs once).
  3. Assign the script to the device group you are removing, and save.
  4. Remove the profiles. Under Devices > macOS > Configuration, remove the group from the Abloomify configuration profile and the Chrome extension profile assignments.
Intune shows the script's result per device. Exit code 0 means the agent is removed. Intune can run the script while no one is signed in; a Mac that reports exit code 1 for that reason needs the step in Troubleshooting.

Remove the agent from Macs with Rippling or another MDM

The same pattern works in Rippling, Kandji, Mosyle, Addigy, or any MDM:
  1. Take the devices out of the scope of the Abloomify app or package, so the MDM stops installing it.
  2. Run abloomify-uninstall-macos.sh as root on each Mac, while the user is signed in. Use your MDM's custom script feature if it has one, any remote management tool that runs a root shell script, or Terminal with sudo on the Mac itself.
  3. Remove the Abloomify configuration profile and the Chrome extension profile from the devices' scope.

Remove the agent from a Windows PC

On Windows the agent appears in Settings > Apps > Installed apps (or Apps & features on Windows 10) as Abloomify, published by Abloomify. Older versions are listed as Abloomify Device Agent.
To remove it from one PC by hand, sign in as an administrator, find Abloomify in that list, and choose Uninstall. The uninstall entry uses a copy of the installer that the agent keeps on the machine, so you do not need the original AbloomifySetup.exe.
Uninstalling stops and removes the agent, its background service (AbloomifyMonitoringService) and scheduled task, and its program files. With the with Chrome extension installer, it also removes the Chrome extension policy. It also deletes the agent's enrollment identity (its key and certificate).

The Windows removal script

Download it here: abloomify-uninstall-windows.ps1. Run it elevated (as an administrator) or as SYSTEM:
powershell.exe -NoProfile -ExecutionPolicy Bypass -File abloomify-uninstall-windows.ps1
It runs the quiet uninstall command that Windows registered for the installed version, then checks that the agent, its service, its scheduled task, and its files are gone. It exits with 0 when the agent is removed, or prints what is left and exits with 1. On a machine without the agent it does nothing and exits with 0, so it is safe to run more than once. On devices that enforce App Control or AppLocker script rules, sign the script with a certificate your policy trusts (or allow it in the policy); otherwise PowerShell blocks what it needs and the script exits with 1.

Remove the agent from Windows with Intune

  1. Stop the install. Go to Apps > Windows, open the Abloomify Win32 app, and under Properties > Assignments, remove the Required assignment for the devices you are removing. If you leave it, Intune reinstalls the agent when its detection rule stops finding it.
  2. Add the removal script. Go to Devices > Scripts and remediations > Platform scripts, click Add, choose Windows 10 and later, and upload abloomify-uninstall-windows.ps1. Set:
    • Run this script using the logged on credentials: No (it runs as SYSTEM).
    • Enforce script signature check: No.
    • Run script in 64 bit PowerShell Host: Yes.
  3. Assign the script to the device group and save. Intune runs a platform script once per device and reports its result.

Remove the agent from Windows with Configuration Manager (SCCM)

  1. Stop the install. In Software Library > Application Management > Applications, select the Abloomify application, open the Deployments tab, and delete the Install deployment for the collection you are removing.
  2. Add the script to the content. Copy abloomify-uninstall-windows.ps1 into the application's content source folder (the folder that holds AbloomifySetup.exe). Open the deployment type's properties, and on the Programs tab, set the Uninstall program to:
    powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\abloomify-uninstall-windows.ps1
    
    Save, then right-click the deployment type and choose Update Content.
  3. Deploy the removal. Right-click the application, choose Deploy, pick the collection, and set Action to Uninstall and Purpose to Required.
The file detection method from the SCCM install guide is what tells Configuration Manager the uninstall worked: once AbloomifyDeviceAgent.exe is gone, the device reports the application as removed.

Remove the agent from Windows with Group Policy

  1. Unlink the install GPO first. The startup script from the Group Policy install guide reinstalls the agent at the next boot whenever it is missing. Unlink or delete Abloomify Device Agent - Install (or whatever you named it) for the OUs you are removing.
  2. Stage the script. Copy abloomify-uninstall-windows.ps1 to a share that Domain Computers can read, for example \\server\software\Abloomify\.
  3. Create the removal GPO. Create a GPO, for example Abloomify Device Agent - Remove, and edit it. Go to Computer Configuration > Policies > Windows Settings > Scripts (Startup/Shutdown) > Startup. On the Scripts tab (not the PowerShell Scripts tab), click Add and enter:
    • Script Name: powershell.exe
    • Script Parameters: -NoProfile -ExecutionPolicy Bypass -File \\server\software\Abloomify\abloomify-uninstall-windows.ps1
  4. Link it and reboot. Link the GPO to the OU, run gpupdate /force on a test machine, and reboot it. Startup scripts run at boot as SYSTEM.
The script does nothing on a machine that no longer has the agent, so leaving the removal GPO linked for a few days is safe. Unlink it once your machines have rebooted.

Remove the agent from Windows with Rippling

  1. Take the devices out of the Abloomify app's scope in Rippling, so Rippling stops installing it.
  2. Run abloomify-uninstall-windows.ps1 on each device as SYSTEM or from an elevated PowerShell, with any tool you use to run scripts on your Windows fleet.
If you set AbloomifySetup.exe /uninstall /quiet /norestart as the app's uninstall command in Rippling, the warning in Remove the agent from a Windows PC applies: on devices that have updated themselves, it may not remove the agent. The removal script does not have that problem.

Remove the Chrome extension

How you remove the extension depends on how you deployed it. The extension ID is ghahjllpbnbbfogpjdnalhijjbfkllad in every case. When the force-install policy is gone, Chrome removes the extension. Visit chrome://policy and click Reload policies to apply the change on a test machine right away.
  • If it came with the Windows with Chrome extension installer, there is nothing extra to do. Uninstalling the agent removes the extension policy the installer set.
  • If you pushed the Chrome profile through an MDM on macOS, remove the Abloomify Chrome extension profile from the devices' scope. In Jamf Pro, that is the computer configuration profile with the com.google.Chrome plist payload.
  • If you added it in the Google Admin console, go to Devices > Chrome > Apps & extensions > Users & browsers, select the organizational unit, select the Abloomify extension, and remove it from the list.
  • If you set it with Windows Group Policy or the registry, remove the ghahjllpbnbbfogpjdnalhijjbfkllad;... entry from Configure the list of force-installed apps and extensions (ExtensionInstallForcelist), and remove the extension's entry from Extension management settings (ExtensionSettings) if you set it. If you used the registry method, delete those values under HKLM\SOFTWARE\Policies\Google\Chrome.

Verify the agent is gone

On a Mac, run these in Terminal. Each one should print nothing:
pgrep -x AbloomifyDeviceAgent
ls -d /Applications/Abloomify.app 2>/dev/null
launchctl list | grep -i abloomify
sudo launchctl list | grep -i abloomify
pkgutil --pkgs | grep -i abloomify
sudo profiles show -type configuration | grep -i abloomify
The last command checks that the Abloomify configuration profiles are gone. It prints nothing once your MDM has removed them.
On Windows, run these in PowerShell. The first three should return nothing and the last should print False:
Get-Process -Name AbloomifyDeviceAgent -ErrorAction SilentlyContinue
Get-Service -Name AbloomifyMonitoringService -ErrorAction SilentlyContinue
Get-ScheduledTask -TaskName AbloomifyAgentLauncher -ErrorAction SilentlyContinue
Test-Path "$env:ProgramW6432\Abloomify\Abloomify Device Agent\AbloomifyDeviceAgent.exe"
Abloomify should also be gone from Settings > Apps > Installed apps.
In Chrome, chrome://extensions should no longer list the Abloomify extension, and chrome://policy should show no entry with the ID ghahjllpbnbbfogpjdnalhijjbfkllad.

What happens in Abloomify after removal

A removed device stops reporting. On the Device Agents page in Abloomify, its last-active time stays at its final report, and after 30 days without a report its status changes to Inactive. The list on the Device Agents tab shows only active devices by default, so the device drops out of it. Set Agent Status to Inactive or All to see it.
A shared Mac can appear more than once, because each macOS user account that ran the agent counts as its own device. If you reinstall the agent later for the same user on the same computer (on Windows, with the same computer name), it reports under its existing entry and becomes active again.

What happens to data already collected

Removing the agent stops new data from that device. It does not delete what Abloomify has already received. That data stays in your Abloomify account, retained per your configuration and your agreement.
When your agreement ends, the Abloomify Data Processing Agreement governs the data. By default you can export it for 30 days after termination, unless your agreement sets a different period. Abloomify then deletes it within 30 days, or a shorter period your agreement sets, unless EU, member state, UK or Swiss law requires keeping it. Backups are deleted or overwritten within 90 days of that deletion. On written request, Abloomify confirms the deletion in writing. For questions about your data, email support@abloomify.com.

Troubleshooting

  • The macOS script ends with exit code 1 and "Sensitive Abloomify data still exists". The app is already removed. Each error line names a file or folder left in a user's account, usually because that user was not signed in when the script ran. Sign in as that user and delete each path listed. The device identity is in ~/Library/Group Containers/group.com.abloomify.deviceagent/DeviceIdentity, and the other paths are under ~/Library/Containers/com.abloomify.AbloomifyDeviceAgent (macOS may ask you to allow access to another app's data). For the rest of your fleet, run the script while users are signed in.
  • The macOS script says it must be run with sudo or as root. Run it with sudo, or set your MDM to run it as root (in Intune, Run script as signed-in user: No).
  • The agent came back after you removed it. Something is still deploying it: a Jamf policy scoped to the Abloomify Not Installed Smart Group, an Intune Required assignment, a Configuration Manager install deployment, the Group Policy install startup script, or a Rippling app scope. Remove that first, then run the removal again.
  • The Windows script ends with exit code 1. It prints what is still present. Run it again from an elevated PowerShell to see the exit codes of the uninstall commands it ran, and email support@abloomify.com with that output if it still fails.
  • The Chrome extension is still there. Chrome removes it only after the policy is gone. Check chrome://policy for an ExtensionInstallForcelist entry with the Abloomify ID, and check that no other policy source (the Google Admin console, a Group Policy, or another profile) still lists it.

FAQ

How do I uninstall the Abloomify device agent on a Mac?

Run the Abloomify uninstall script as root while the user is signed in: download it from https://www.abloomify.com/downloads/abloomify-uninstall-macos.sh and run sudo bash abloomify-uninstall-macos.sh, or add it to your MDM as a script that runs as root. It stops the agent, removes the app, its launch agents, the updater, package receipts and logs, and clears the device identity. Then remove the Abloomify configuration profile and the Chrome extension profile in your MDM.

How do I uninstall the Abloomify device agent on Windows silently?

Run the Abloomify removal script elevated or as SYSTEM: powershell.exe -NoProfile -ExecutionPolicy Bypass -File abloomify-uninstall-windows.ps1. It runs the uninstall command Windows registered for the installed version, so it works after the agent has updated itself and when the original AbloomifySetup.exe is gone. It exits with 0 when the agent is removed and 1 if anything is left.

Do I need the Abloomify console or the original installer to remove the agent?

No. Both removal scripts are published on this page, and on Windows the uninstall entry in Settings > Apps uses a copy of the installer kept on the machine. You can remove the agent after your subscription has ended.

Can an employee uninstall the agent?

Not without administrator rights. On Windows the agent installs per machine, so removing it needs an administrator. On a managed Mac the configuration profile locks the agent on, and the uninstall script must run as root. Removal is an IT task done through your device management tool.

Does uninstalling the agent delete the data Abloomify already collected?

No. Removing the agent stops new data from that device. Data already collected stays in your Abloomify account, retained per your configuration and agreement. When the agreement ends, the Abloomify DPA sets what happens: you can export the data for 30 days unless your agreement sets a different period, then it is deleted within 30 days (or a shorter period your agreement sets) unless EU, member state, UK or Swiss law requires keeping it, and backups within 90 days of that. Abloomify confirms deletion in writing on request.

What happens to the device in Abloomify after I remove the agent?

It stops reporting. After 30 days without a report, the Device Agents page shows it as Inactive, and it drops out of the list on the Device Agents tab, which shows active devices by default. If you reinstall the agent later for the same user on the same computer (on Windows, with the same computer name), it reports under its existing entry and becomes active again.

Get help

Email support@abloomify.com and we will help you remove the agent cleanly. For how the agent works and what it collects, see the Abloomify device agent overview.
Share this article
← Back to Blog
Abloomify Team
Abloomify Team
Editorial Team

The collective voice of Abloomify's product, engineering, and customer success teams sharing insights from the frontlines of AI-powered workforce management.