Home/ Questions/Q 7041623
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-28T02:04:06+00:00

Brief I have an installation package (MSI based) which attempts to register a dll

  • 0

Brief

I have an installation package (MSI based) which attempts to register a dll file for use as a Windows Explorer Bar (Internet Explorer Toolbar).

The custom action is defined as follows:

[SystemFolder]\regsvr32.exe /s "pathtodllhere"

The error

  • The regsvr32 custom action does not work on Windows XP 64-bit.

Output from MSI log:

CustomAction SystemFolder_2 returned actual error code 5. Error
1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Action SystemFolder_2,
location: C:\Windows\SysWOW64\, command: regsvr32.exe /s “C:\Program
Files (x86)\Test Install\test.dll”

MSI (s) (10:F4): Product: Test Install — Error 1722. There is a
problem with this Windows Installer package. A program run as part of
the setup did not finish as expected. Action SystemFolder_2, location:
C:\Windows\SysWOW64\, command: regsvr32.exe /s “C:\Program Files
(x86)\Test Install\test.dll”

A brief run-down of my tests/thoughts thus-far:

  • Custom action is in the “InstallFinalize” section, it is therefore run ONLY when the files have been dropped onto the hard drive.
  • Dll file is not corrupt and is valid.
  • Regsvr32 custom action works fine (and MSI installation) on: Windows 7 32-bit and Windows XP 32-bit.
  • Regsvr32 32-bit version is executed during 64-bit install (as it should).
  • Regsvr32 fails with error code 5, i.e. ERROR_ACCESS_DENIED.

Solutions and Musings

  1. Self-registration – Not using regsvr32 and manually place the registry keys using my MSI Installer.
  2. The dll is a Delphi COM dll which uses the TRegistry component to register itself. Again, I can’t think of a reason why this wouldn’t work as it is merely a wrapper, but just a thought.

Hopefully I have shown my research here and don’t waste anyone’s time!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The best practise solution (as you’ve alluded to) is to extract the registry entries from the component and write them to the registry using the msi.

    Background

    Regsvr32 requires admin rights and elevated privilege confirmation to register COM components under 64-bit Windows 7 but msiexec doesn’t know to request elevated privileges for the custom action.

    You can test this requirement by using “Open with…” to run C:\Windows\SysWOW64\regsvr32.exe on the component (which will fail). Whereas if you create a batch file for the registration and then “Run as Administrator” the component will register successfully.

    • 0