http://bugs.winehq.org/show_bug.cgi?id=13687
--- Comment #22 from Alexandre Julliard julliard@winehq.org 2009-09-22 10:51:51 --- (In reply to comment #16)
I realize this may not satisfy your standards of proof, but steps 1 & 2 do show that the direct causative factor in this specific case is not ies4linux, rather it is the change in wine.
Granted, ies4linux is present, but it is a constant factor and the variable factor is wine. Therefore, in this limited case, the change in wine can be said to produce the bug.
It's a bug in native crypt32, so it doesn't happen in a normal Wine config.