https://bugs.winehq.org/show_bug.cgi?id=47965
--- Comment #7 from David dav75uk@yahoo.co.uk --- Absolutely. I can understand that fixing a possible esoteric bug in a piece of software which is not commonly used may take a lower priority and any work done by the user may expedite a fix. I've worked on free software before and understand the pressures of finding time to work on it and satisfying users with their must fix issues which are often little more than it doesn't work. I'll have a try toggling the registry key as suggested to see if it works.
As for regression testing, you can understand having to get wine to build, install it in a clean wine prefix and binary chop down is a very slow and tedious process. Thus unless it's a real disaster not many will have the time and will to attempt it. Anything that could be done to automate it so that the only real input the user need do is test their software when prompted and indicate whether it passed or failed would be a great productivity boost.
I was being a little 'tongue in check' by suggesting that testing could be better. I realise that getting Windows compatibility without looking at the source and difficult APIs in such a complex project is extremely difficult. However, awaiting major releases because they might be more stable at least for the software I commonly use probably isn't an option either as not too many others will be using it so better to upgrade every version which may run into temporary bugs too.
But once again, thanks for the free software and the effort that is put in.