Symptoms
The Secureframe Agent has stopped reporting into the Secureframe dashboard / asset inventory.
Reinstalling the agent fails with “The specified account already exists.” and closes after you click OK.
An earlier uninstall may have failed with an MSI 1603 error.
Fleet osquery no longer appears in Services or in Add or Remove Programs, yet the reinstall still fails.
Why this happens
This is caused by a leftover (orphaned) Windows Installer registration from the previous agent (Fleet osquery / Orbit). Even after the old agent has been removed from Services and Add or Remove Programs, Windows can still hold a “ghost” MSI registration for it. When the new installer runs, it detects that stale registration and stops with “The specified account already exists.”
How to fix it
Follow these steps in order.
1. Restart the device
Reboot the machine before doing anything else. A pending state from the previous uninstall can cause the reinstall to fail, and a restart clears it.
2. Remove the orphaned registration with Microsoft’s troubleshooter
Download the Microsoft Program Install and Uninstall Troubleshooter from Microsoft Support: support.microsoft.com – Fix problems that block programs from being installed or removed .
Run the troubleshooter and choose Uninstalling.
In the list of programs, select Fleet osquery and remove it. Orphaned products show up in this list even when they no longer appear in Add or Remove Programs.
Let the troubleshooter finish cleaning up the registration.
3. Reinstall the Secureframe Agent
In Secureframe, go to Employee Onboarding > Windows and download the current agent build.
Run the installer as Administrator.
Complete the installation and confirm the device appears back in your Secureframe asset inventory within a few minutes.
Tip: Re-downloading the installer through a browser can save it as secureframe-agent (1).msi. Installing from a file renamed this way can itself trigger the error — make sure you rename the file to secureframe-agent.msi.
Still not working?
If the reinstall still fails after the steps above, capture a verbose installer log so Support can pinpoint the exact cause. Open a new Administrator Command Prompt and run (adjust the path to where you saved the installer):
msiexec /i "C:\Users\<user>\Downloads\secureframe-agent.msi" /L*V "%TEMP%\sf-agent-install.log"
Then reach out to Secureframe Support with:
The generated log file (
%TEMP%\sf-agent-install.log).A screenshot or short recording of the error.
Whether Fleet osquery appears in Services and in Add or Remove Programs.
The exact filename of the installer you ran.