The naming scheme of gvfs-fuse creates directory names of mounted volumes under /run/user/<uid>/gvfs that contain colons, for example:

  smb-share:server=myserver,share=myshare

Windows does not allow colons in filenames and as a result this prevents Windows applications run through Wine from accessing gvfs files. For instance this is the case of Microsoft Excel which can obviously not be fixed by the community.

One could argue that colons are valid in POSIX filenames and certainly if a user decides to name his file 'foo:bar.xls' he won't be able to open it in Excel. However that's by his own choosing and thus he can easily avoid that issue. This is in contrast with the gvfs situation which imposes a filename that's incompatible with Windows applications.

Furthermore colons also break compatibility with all xxxPATH variables, even in the POSIX world.