You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are experiencing an issue where all Custom Actions fail during installation on some of our customers' machines running Windows 11 Professional with the latest updates. The same behavior could not be replicated on our internal test machines. Logs from affected systems are provided below for reference.
Do you have any idea what the problem could be?
Frank
Logs:
Action start 9:29:50: InstallFinalize.
SFXCA: Extracting custom action to temporary directory: C:\Windows\Installer\MSI8C94.tmp-\
SFXCA: Binding to CLR version v4.0.30319
Calling custom action My_setup!company.Program.Setup.CustomActions.FileExtensionsCustomActions.FileExtensionsAdd
FileExtensionsAdd: Logging Configured
FileExtensionsAdd: Start
FileExtensionsAdd: C:\Program Files\MyProgram\SetupHelper.exe
FileExtensionsAdd: arguments: /FileExtensions=Add
FileExtensionsAdd: ActionResult: Success
FileExtensionsAdd: End
SFXCA: RUNDLL32 returned error code: -1073741819
The text was updated successfully, but these errors were encountered:
Sorry Frank, it took some time to get to the tickets backlog.
There are two possible causes:
the custom action is not compatible with the .NET version on the target system.
try to execute your routine (it is an exe assembly after all) on the target system to see if it loads. This way you will be mimicking what RUNDLL32 does when it executes SFXCA*.dll
runtime exception
try to have a nice try-catch with logging; or try to debug.
Hello Oleg,
We need you help again.
We are experiencing an issue where all Custom Actions fail during installation on some of our customers' machines running Windows 11 Professional with the latest updates. The same behavior could not be replicated on our internal test machines. Logs from affected systems are provided below for reference.
Do you have any idea what the problem could be?
Frank
Logs:
The text was updated successfully, but these errors were encountered: