https://bugs.winehq.org/show_bug.cgi?id=47669
--- Comment #19 from ryan@rnrcarpet.com --- (In reply to Zebediah Figura from comment #17)
(In reply to ryan from comment #16)
If I'm understanding it right, that PreProcessFirewallConfig(unsigned long) is a function of msi?
It's a custom action, which the program itself provides, and which MSI calls back into. Custom actions contain completely arbitrary code, so a failure in a custom action more often than not doesn't imply a problem with MSI.
I find that very fascinating actually. I'm happy for the explanation. Thank you. My first real bug report with Wine is quite a good learning tool with debugging applications through Wine as I know you know what you're doing =)
(In reply to Zebediah Figura from comment #18)
I think there's Mono problems here, but I'm not sure and I can't get the wine-mono debugging channels to work correctly for some reason.
Maybe a different approach is possible. I take it that this is the mono that's taking over for .net... maybe it can be disabled and .net used instead?
I made a 32bit prefix and the installer failed same but differently popped up a second window during install not seen with 64bit prefix.
Still need to fix missing dll's but found that interesting. Also of note maybe that .net 4.7 exe is included and looks like should be installed pre-file copy during installation process.
Also found an installation log in the installation temp dir and attaching that as it might prove useful.