http://bugs.winehq.org/show_bug.cgi?id=25535
--- Comment #7 from André H. nerv@dawncrow.de 2010-12-22 17:43:12 CST --- (In reply to comment #6)
Um, surely forcing Mono is contrary to the premise of this bug? (What good is running the .NET 4.0 installer if you're just going to use Mono instead?)
True, sry. I got confused with an app that just needed dotnet4 and mono helped at least a bit for the installer. so for this bug you dont need gecko, or something. installing dotnet4 in a clean prefix leads to the same error.