http://bugs.winehq.org/show_bug.cgi?id=57797
--- Comment #14 from Jorge Leguiza coki@hotmail.com --- I did more testing today, in the same virtual machines I mentioned on comment 10 and followed what was requested on comment 11 and in fact this issue is still there
Both testings I did on comment 10 are legitimate however, I was able to start the already installed application on both virtual machines with no issues, and I have it recorded in video, after re-generating WINE and trying again the error returned. the only notable difference is the update 10.3 of WINE Mono though I believe that to not be the cause
I believe what happened is that "leniency" I had mentioned prior in comment 9 or in other words, I got really lucky to initialize correctly on both virtual machines on my tests for that comment
The issue is definitely still present and at this point I should try the suggested patch on comment 4 however my machine is not fast, compiling wine will take me many hours and I would be grateful if binaries could be provided, otherwise I'll report back once I have tested it