https://bugs.winehq.org/show_bug.cgi?id=40460 --- Comment #6 from Sebastian Lackner <sebastian(a)fds-team.de> --- When I just call "winetricks xna31" I'm still not able to see any kind of failure here on my machine. However, I played around a bit more, and when I add the "-q" switch it indeed fails. Is that also what you guys use? On the first sight, it seems to be a race-condition in winetricks. Installation of dotnet20sp2 is started before dotnet20 is fully finished. Before the commit, RegNotifyChangeKeyValue always returned immediately with a failure, now the application will properly wait. Those timing differences are probably what causes the "regression". Proposed change for winetricks: --- snip --- --- a/src/winetricks +++ b/src/winetricks @@ -5800,6 +5800,7 @@ load_dotnet20sp2() w_call remove_mono w_call dotnet20 + $WINESERVER -w # FIXME: verify on pristine windows XP: if w_workaround_wine_bug 34803 --- snip --- BTW: At some places winetricks uses $DRIVE_C which looks like an undefined variable to me. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.