Constant Acrobat MSinstaller errors in Windows event log

This is not a normal user issue. It is Windows Installer trying to repair Acrobat in the background but failing because users are not admin.

Quick fix that usually works:

Open Services
Find Windows Installer
Stop it

Then open Command Prompt as admin and run a repair reinstall of Acrobat. This resets the installer state.

If it still happens:

Disable automatic repair triggers
Go to Task Scheduler and look for Adobe or MSI repair tasks and disable them

Also make sure:
Users are not triggering self repair by opening protected locations or missing components

Main point
This is a broken install state loop. You need to stop Windows Installer repair cycle and reinstall clean with admin rights once so it does not trigger again.

Subscribed cuz I’m looking for an answer to why this is happening to all of our deployed systems -- been chasing this and other anomalies and oddities with Acrobat since the day we installed this version (coming from 2020 perpetual).

Clean install, Repair, Re-install, Cleaner Tool, Create and Recreate a new package, install as the local Administrator account -- nothing has made this go away.

We use Group Policy, but for system configuration and consistency, not application deployment, configuration, etc.

All end users are “local” admins on their computers -- which makes this error message even more bizarre.

Another bizarre issue is we have “auto update” enabled, yet NONE of our systems have successfully updated automagically (this deployment began OCT 2025).

Note: I am the Domain/Enterprise Admin and I get the same error/entry in my Event Log.

Hello ​@rsimons 

I hope you are doing well, and thank you for reaching out. We’re sorry for the trouble you had.

Error 1730 and the follow‑up 1603 events are coming from Windows Installer (MSI), not Acrobat itself. What’s happening is that Windows is periodically triggering an MSI self‑repair / reconfiguration for Acrobat while a standard user is logged in. Because that repair requires admin rights, it fails and logs:

• Error 1730: repair/reconfiguration attempted without admin rights
• Error 1603: generic MSI failure after the repair attempt

That’s why:

• It happens on fresh OS + fresh Acrobat installs
• It appears throughout the day
• Uninstall/reinstall (even with the Adobe Cleaner) doesn’t stop it
• All machines show the same behavior

Suggestions:

Perform a Clean Reinstall as Administrator:

• Uninstall Acrobat from Control Panel > Programs and Features.

• Run the Acrobat Cleaner Tool as Administrator: https://www.adobe.com/devnet-docs/acrobatetk/tools/Labs/cleaner.html

• Restart the computer.

• Reinstall Acrobat:

  • Right-click installer > Run as Administrator

  • Or deploy via Admin Console package: https://helpx.adobe.com/enterprise/admin-guide.html

For complete Enterprise deployment and configuration, please check this article: https://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/index.html

Please note that Error 1730 + 1603 together almost always indicates: 

• Windows Installer is attempting a repair action that requires elevation.
• This is typically environmental, not a product defect, mainly when occurring across multiple fresh machines.

Summary:

• Build a new Acrobat package from Admin Console.

• Completely remove the existing installation using the Cleaner Tool (run as admin).

• Reboot.

• Deploy fresh package as admin (or via endpoint management system).

• Confirm users are not triggering repair due to restricted permissions.

If the issue persists after a clean enterprise deployment, it may indicate:

• A permissions policy applied via GPO.

• Windows Installer attempting advertised shortcut repair.

Let us know how it goes.

Regards,

Anand Sri.