Zebediah Figura z.figura12@gmail.com writes:
Does anyone know, or have a hunch, as to what the problem might be here? For what it's worth, it's known that native MSI uses a separate process to execute custom actions, although I don't know how this would lend any clue to what's going wrong.
In a separate process you'd already have the MSI server exe running, so you can't load a second exe. What probably happens is that the exe module is loaded but its imports are not resolved.