https://bugs.winehq.org/show_bug.cgi?id=56565
Bug ID: 56565 Summary: Command and Conquer 3 Tiberium Wars installer crashes Product: Wine Version: 9.6 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: hibbsncc1701@gmail.com Distribution: ---
Split from bug #53561.
This bug is about a crash / hang in the installer for the retail release of Command and Conquer 3 Tiberium Wars when used with the recommended installation type. (The advanced installation type is unusable under Wine, see the original bug #53561.)
After clicking on the next button on the installation type screen, installer appears to try and copy files. This is supposed to have a progress indicator that fills up, but it gets drawn in wine as completely full, with status "Copying new files". The UI has stopped updating and placing another window (Wine or from the host's WM) over it will cause graphical corruption.
After about a minute on my machine, the UI window disappears entirely. The msiexec process however is still running in the background, and can be seen on the task bar if wine is running with a virtual desktop. It is also still visible in wine's taskmgr.exe. Where it shows two msiexec processes and one unnamed 32bit process. (Wine's taskmgr shows "*32" for the process name.)
After this the process does not exit unless killed. Doing so kills both msiexec processes and the unnamed 32bit process.
Looking through the registry after killing the installer, we find that it did create the needed registry keys expected by the game, in addition to installing the games files at the expected default location. The game does run in this state. So it appears that the installation was successful, despite the bug.
Running the installer with WINEDEBUG="+msi" causes the installer to run correctly. I.e. It doesn't crash / hang indefinitely. Although, the UI still stops updating while the files are copied, it will recover in this case and allow the installer to run to completion. With the user able to exit the installer normally.
WINEDEBUG="+msi" log attached.