https://bugs.winehq.org/show_bug.cgi?id=38000
--- Comment #5 from Anastasius Focht focht@gmx.net --- Hello Susan,
unfortunately the log doesn't show obvious errors.
Just normal WINEPREFIX "warmup" with builtin processes/services started, along with some ngen run (native .NET Framework 4.0 service).
Nothing that tells there is an installation going on. No MSI, no InstallShield.
Since I saw native .NET I must assume you reuse some existing prefix or was it just one prerequisite install via winetricks before the running the app installer? I would avoid spending time on diagnosis of broken prefixes.
Just install the minimum prerequisites required in a 32-bit WINEPREFIX (those that usually don't install well with Wine). Nothing else.
Also try to reduce the amount of log by using following approach:
Open another (second) terminal and start a Wine builtin app, 'notepad' for example. After that, start the actual installer in the first terminal:
$ WINEDEBUG=+tid,+seh,+relay,+msi wine ./replace_me_by_installer_name.exe
log.txt 2>&1
If the installation failed once, please don't try create another log out of it. You must re-do everything. The prefix must be pristine to allow proper diagnosis. Otherwise a repair install gets triggered and all sorts of things go wrong.
Regards