https://bugs.winehq.org/show_bug.cgi?id=45589
--- Comment #6 from ykui yumekuineru@hotmail.com --- (In reply to Ben Parsons from comment #5)
Is this bug present in staging 1.13.1? As I thought this was fixed.
2f3ba1fb was immediately after 3.13.1 (9a1a1f02) so the issue as reported here occurs there for me at least I guess