https://bugs.winehq.org/show_bug.cgi?id=50299
--- Comment #1 from Bernhard Übelacker bernhardu@mailbox.org --- Created attachment 68907 --> https://bugs.winehq.org/attachment.cgi?id=68907 Avoid winemenubuilder to startup explorer.exe.
I further looked into the issue and found that in that environment winemenubuilder is faster and triggers startup of explorer.exe. But started with that parent explorer.exe cannot properly setup the desktop.
This hack creates an event __wine_desktop_created that is released just after explorer.exe reaches the SetPropW(__wine_display_device_guid).