https://bugs.winehq.org/show_bug.cgi?id=47724
--- Comment #7 from Hans Leidekker hans@meelstraat.net --- (In reply to Allan from comment #6)
I was able to downgrade wine and track what version introduced this issue. From 4.9 to 4.10
4.15: FAIL 4.14: FAIL 4.13: FAIL 4.12: FAIL 4.11: FAIL 4.10: FAIL 4.9: SUCCESS 4.8: SUCCESS
I'm using Arch Linux (https://archive.archlinux.org/packages/w/wine/)
Can you perform a regression test to find the commit between 4.9 and 4.10 that broke it? See https://wiki.winehq.org/Regression_Testing