https://bugs.winehq.org/show_bug.cgi?id=57011
--- Comment #4 from Paul Gofman pgofman@codeweavers.com --- The mentioned critical section change is upstream as bf7d403ad89b624c90784afb3ffd3e5ba5559ae5. So right now it will probably show message box attempting to execute the sample script instead of hanging. But again, going forward there is no warranty that the script will work the same way. If some random change which will alter unrelaed stack contents will result in some other value for critical section data where it won't decide to wait for that as semaphore but will use WaitOnAddress() instead then it will hang again.