Skip to content

Est. 2011ยทMicrosoft Partner ID 7033487ยทDelivery under 3 minยทSupport 7 days a week

Your vault is empty.

Free Fix 2753

Trend Micro will not uninstall: removal tool errors and stuck components

11 min read Updated October 5, 2026 Antivirus & Endpoint Security

Fix it now

Removal is failing inside Windows Installer, and Trend Micro publishes its own route around it. Open the Diagnostic Toolkit and use its Uninstall tab rather than Settings, because that is the supported way to remove a Trend Micro consumer product and it does not depend on the installer metadata that has broken.

Run in an elevated Command Prompt. Capture the sc qc output before removing anything

sc qc <servicename>
sc query msiserver
  1. Close the Trend Micro console completely, including its tray icon.
  2. Press Windows+R, type supporttool.exe and click OK, then approve the User Account Control prompt.
  3. Open the (C) Uninstall tab, click 1. Uninstall Software, note the serial number when it is shown, tick the box confirming you have copied it, then click Uninstall and allow the restart.
  4. After the restart, check Settings, Apps, Installed apps to confirm the entry has gone.
  5. If it is still listed, find the product code under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall and, on 64-bit Windows, also under HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall, then run msiexec /x {product-code} from an elevated Command Prompt.
  6. If removal still fails, run the Trend Micro Remnant File Remover Tool to clear what is left, and restart.

Write the serial number down when the toolkit shows it. You will need it to reinstall, and the uninstall is the last time the machine will offer it to you.

If no Trend Micro entry remains and no Trend Micro services start, you are done. If not, the next section explains why an uninstall fails this way.

Why it happens

Windows Installer does not remove software by deleting the files it finds. It replays the original installation in reverse, using a cached copy of the package on the system drive plus a registration describing every component that was installed. Removal only works while those two things agree with each other and with what is on disk. When the cached package is missing, truncated or from a different build, the installer is asked to act on entries it has no record of, and it stops.

2753 and 2769 are numbers from that breakdown, and it is worth being straight about what they are. Microsoft’s published Windows Installer error reference states that error codes numbered greater than 2000 are internal errors that do not have authored strings, and that they can occur where the installation package has been incorrectly authored. So neither number has a published meaning you can act on. They tell you the installer’s own machinery objected; they do not tell you to what.

1613 is the one worth reading carefully, because it is routinely misdescribed. Microsoft publishes it as ERROR_INSTALL_PACKAGE_VERSION: this installation package cannot be installed by the Windows Installer service, and a Windows service pack containing a newer version of the Windows Installer service is required. It is a statement about the engine on the machine being older than the package needs. It is not a damaged cached package and it is not installer corruption, and chasing either of those will waste your afternoon.

1704 is a genuine, actionable message: an install for the product is currently suspended and the changes made by that install must be undone before anything else can proceed. 1626 is ERROR_FUNCTION_NOT_CALLED, the function could not be executed. Between them they describe a machine with an interrupted operation still hanging over it, which is usually cleared by a restart before you do anything cleverer.

The ordinary uninstall route is the wrong one

You have this one if Removal from Settings fails, and you have not tried Trend Micro’s own tool.

  1. Open the Diagnostic Toolkit with supporttool.exe and use the (C) Uninstall tab.
  2. Note the serial number when it is offered and confirm you have copied it.
  3. Allow the restart it asks for; the removal is not finished until then.
  4. Check Installed apps afterwards.

This is Trend Micro’s documented procedure for removing Maximum Security, Internet Security and Antivirus+ Security on Windows. Try it before anything involving msiexec.

An earlier installation is still suspended

You have this one if You are told an install is suspended and must be undone before continuing, which is message 1704.

  1. Restart first. Some suspended operations complete during shutdown.
  2. Let any part-finished Windows update or other installation complete before touching the antivirus.
  3. Run the Diagnostic Toolkit’s uninstall once the machine restarts with nothing pending.

The Windows Installer engine is older than the package

You have this one if 1613, on a machine that is behind on servicing.

  1. Install outstanding Windows updates and restart. That is what moves the Windows Installer version.
  2. Retry the removal afterwards.
  3. Do not chase installer repair or package-cache repair for this code; the published meaning is a version mismatch.

The product’s own protection is blocking removal

You have this one if Removal fails while the console is open or services are running, and the failure looks like a permissions problem.

  1. Close the console completely, including its tray icon, before starting.
  2. Switch off the product’s self-protection in its settings if that option is available to you.
  3. Use the Diagnostic Toolkit rather than Settings, because it is built to handle the product’s own defences.
  4. Restart between attempts rather than retrying immediately.

The next fix uses sc delete, which removes the service’s registry key and cannot be undone. Run sc qc <servicename> first and keep the output, so you have a record of the binary path, start type and dependencies if you need to put it back. Do not delete a service you cannot name.

Registrations survive after the files have gone

You have this one if The product no longer appears in Installed apps, but services or drivers named for it still appear in services.msc or Device Manager, and a replacement antivirus refuses to install.

  1. Run the Remnant File Remover Tool first; it exists for this state and is safer than editing by hand.
  2. If a service remains, read its exact service name from its properties, run sc qc <servicename> and keep the output, then remove it with sc delete <servicename>.
  3. Restart and confirm the service is gone.
  4. Only then remove leftover product folders under Program Files and ProgramData.

If a replacement antivirus now installs cleanly, stop. There is no benefit in hunting further entries once the machine works.

Full reference

Finding the product code properly

This is where most manual removals stall, and for one avoidable reason: the uninstall registrations live in two places on a 64-bit machine, which is every supported machine.

Path What it holds
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall 64-bit products
HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall 32-bit products, which consumer security suites often still are, at least in part
HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall Products installed for one user only
  1. Search each of those keys for a subkey whose DisplayName names the Trend Micro product.
  2. Read its UninstallString. If it begins with msiexec and contains a code in braces, that is the product code and msiexec /x {code} applies.
  3. If the UninstallString points at a vendor uninstaller executable instead, the product is not an MSI install and msiexec will not remove it – run the executable it names, or use the Diagnostic Toolkit.
  4. Look under WOW6432Node before concluding the product code does not exist. Looking in only one view is the single most common reason people decide there is nothing there.

The published meanings, and the two that have none

Code Published meaning
2753 No published meaning. Microsoft states that installer errors above 2000 are internal errors without authored strings
1613 ERROR_INSTALL_PACKAGE_VERSION – the package cannot be installed by this Windows Installer service; a newer version of the service is required
1704 An install for the product is currently suspended. The changes made by that install must be undone to continue
1626 ERROR_FUNCTION_NOT_CALLED – the function could not be executed
2769 No published meaning; same internal-error range as 2753

Safe Mode, and what actually runs there

Booting into Safe Mode stops most services and drivers loading, which is why it is a standard move when self-protection is in the way. The caveat is real: the Windows Installer service is not started in Safe Mode by default, so an msiexec removal will fail there unless the service is explicitly enabled for that boot. A vendor tool that does not rely on Windows Installer is not subject to that limitation, which is another reason to try the Diagnostic Toolkit before the manual route.

Confirming the machine is actually clean

  1. Settings, Apps, Installed apps shows no Trend Micro entry.
  2. services.msc lists no Trend Micro services.
  3. Device Manager, with View, Show hidden devices enabled, shows no orphaned Trend Micro drivers.
  4. Windows Security, Virus and threat protection shows Microsoft Defender active, or your replacement product registered.
  5. A restart produces no errors in Event Viewer, Windows Logs, System from a service that no longer exists.

Why deleting the folder is the worst option

The files go and everything else stays: the services, the file-system filter driver, the registrations with the Windows Security Center. The machine then loads components that no longer exist, Windows still believes an antivirus is present, and a replacement product refuses to install because the position is taken. Recovering from that is harder than the uninstall you were trying to avoid.

Nothing here requires a purchase. A failed uninstall is a Windows Installer problem and the tools are published free by Trend Micro and by Microsoft. If an expired subscription is why you are removing the product, letting Microsoft Defender take over afterwards costs nothing either.

Every code this article covers

Code What it points at Source
2753 An internal Windows Installer error. Microsoft states that codes above 2000 are internal errors without authored strings, which can occur where the installation package has been incorrectly authored, so no published meaning exists to act on not published by the vendor
1613 ERROR_INSTALL_PACKAGE_VERSION: the package cannot be installed by the Windows Installer service on this machine, which needs a newer version of that service. It is not installer damage or a mismatched cached package Microsoft Learn
1704 An install for the product is currently suspended; the changes made by that install must be undone before anything else can proceed Microsoft Learn
1626 ERROR_FUNCTION_NOT_CALLED: the function could not be executed Microsoft Learn
2769 Another internal Windows Installer error from the same range as 2753, with no authored string published not published by the vendor

Confirm the fix worked

  1. No Trend Micro entry remains in Settings, Apps, Installed apps.
  2. services.msc lists no Trend Micro services.
  3. A restart produces no Event Viewer errors from a missing Trend Micro service.
  4. Windows Security, Virus and threat protection shows Microsoft Defender active, or your replacement product installed cleanly.
  5. The serial number is written down somewhere, in case you reinstall.

Questions people ask about this

Can I just delete the Trend Micro folder?

No, and it makes things worse. The files go but the services and the file-system driver stay registered, so the machine keeps loading components that no longer exist and refuses a replacement antivirus. Use the Diagnostic Toolkit’s Uninstall tab.

What does 2753 mean?

Nothing published. Microsoft’s own Windows Installer reference says error codes above 2000 are internal errors that do not have authored strings and can occur where the package has been incorrectly authored. Diagnose from 1613, 1704 and 1626, which do have published meanings.

I get 1613. Is my installer damaged?

No. Microsoft publishes 1613 as the package requiring a newer version of the Windows Installer service than the machine has. The fix is to bring Windows servicing up to date and restart, not to repair the installer or the package cache.

Will removing it lose my subscription?

No. The subscription belongs to your Trend Micro Account, not to the installation. Note the serial number when the toolkit shows it, and free the device slot in the account if you are moving to a different machine.

Is it safe to install another antivirus before this one is fully gone?

No. That is the most reliable way to end up with a machine where neither product works and neither can be removed. Finish the removal, restart, confirm the services are gone, then install the replacement.

Related error codes

Was this article helpful?

Your feedback helps us improve our documentation.

Related articles

License Error Defender event 5007 is a settings change, not a block: 5013 is tamper protection Free Fix Avira error 0x00000001 and 501: install and update failures on Windows License Error Bitdefender update error -1002 and -1022: the client cannot reach the update servers Free Fix AVG error 42125 and 42127: AVG Antivirus is not fully installed
โ† Back to Knowledge Base