https://bugs.winehq.org/show_bug.cgi?id=45033
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED Fixed by SHA1| |623543bedc17eec14252ad3f81e | |87af010143b2f
--- Comment #10 from Anastasius Focht focht@gmx.net --- Hello folks,
this is fixed by commit https://source.winehq.org/git/wine.git/commitdiff/623543bedc17eec14252ad3f81...
Thanks Hans.
The installer now detects that the newly introduced (stub) WMI service is not running (not configured as auto-start) and ask for starting it:
--- snip --- 006a:trace:msgbox:MSGBOX_OnInit L"The Windows Management Instrumentation service must be running in order for the product to function properly. Click OK to have the installation start the service, or Cancel to cancel the installation." --- snip ---
This is acceptable as we don't want to auto-start services by default which are not used at all.
-> proceeds further after clicking 'OK'.
NOTE: If you let the app installer do .NET Framework 4.5.x install on its own in clean 32-bit or 64-bit WINEPREFIX you will end up with a broken .NET installation, causing DNS15 installer to fail later. These are known issues. If you don't follow general practice you have to deal with the fallout on your own.
The installer will still fail in the end because some custom actions require MS PowerShell 3+ installed in the WINEPREFIX (fails to load assembly 'System.Management.Automation, Version=1.0.0.0 ...).
$ wine --version wine-3.7-65-ge637a6f0bf
Regards