http://bugs.winehq.org/show_bug.cgi?id=58529
--- Comment #14 from Eric Pouech eric.pouech@gmail.com --- (In reply to Ken Sharp from comment #10)
(In reply to Eric Pouech from comment #3)
when you write in #1 that you tried different fs, for which mount point was it?
I created multiple mount points (named btrfs, ext4, etc.) and pointed the wineprefix to them. Installation completes with z: removed.
maybe unrelated (but could be from symptoms), but would one of your mounted fs be btrfs with subvolumes used?
My test mount points didn't use subvolumes. My system uses subvolumes. / and /home span multiple SSDs, and another spinning disk which also uses subvolumes. The installation works when installing to either of these.
There are cases when btrfs subvolumes inside the same volume have paths that overlap (typically / and /home), where the reverse lookup (unix path => mount point => drive letter doesn't work correctly as mountmgr doesn't find/use the relevant mount point - or confuses the two).
so if your setup has / and /home as subvolumes in the same btrfs volume, you could fall into the issue I'm thinking of. It's that's the case, I can share some hacks to deal with that (can't tell from here if that would be useful, and likely from the rest of the exchange, there could be some other issues)