https://bugs.winehq.org/show_bug.cgi?id=57859
--- Comment #10 from Tom Maneiro tomman@gmail.com --- So, to recapitulate this mess:
- ALL Debian/Ubuntu users using WineHQ upstream repos are affected by this, using ANY 10.2 release, be it -devel or -staging.
- Relevant error codes: 4000000e = STATUS_IMAGE_MACHINE_TYPE_MISMATCH c0000135 = STATUS_DLL_NOT_FOUND ...which means that the Wine loader is trying to load system DLLS from either a wrong or non-existing place.
- Cannot create new prefixes (STATUS_DLL_NOT_FOUND), cannot start anything from an already existing prefix (STATUS_IMAGE_MACHINE_TYPE_MISMATCH). Fortunately this failure mode seems harmless for existing prefixes as Wine doesn't "boot" enough to touch the Registry or any sysfile, so reverting to 10.1 is perfectly safe.
- Building 10.2 from source on the affected distros yields a perfectly functional Wine install.
- The new WOW64 dynamic mode stuff seems to require packaging changes, which were implemented for other distros served by WineHQ (for example, Arch packages are OK as per bug 57857, but downstream distro-packaged versions are broken with similar errors), so maybe said packaging changes might have been missed for the .debs? In fact, after querying Bugzilla, the ONLY reports are here (and at bug 57861, a duplicate of this one) are ALL from Debian/Ubuntu-derivative users!
Looks like those packaging rules for the .debs somehow missed the required changes for the latest WOW64 changes, which would be the very first place to look at (just wondering - I haven't packaged Wine for any distro in over a decade!)