https://bugs.winehq.org/show_bug.cgi?id=42446
--- Comment #53 from Stan markau0@lycos.com --- (In reply to Zebediah Figura from comment #52)
Indeed, it seems as though you have the problem nailed down quite well. A patch to fix it would be quite welcome ;-)
I posted as attachments an updated dlls kernel32 volume.c with the GetVolumePathNameW forward slash changes for Wine 3.3 a few posts back if anyone is interested and also an added forward slash test (dlls kernel32 tests volume.c) and the volume tests pass with the forward slash changes.
The problem gets down to if a Windows app calls GetVolumePathName directly with a forward slash path name which is not an error as far as Windows is concerned, it's just that most Windows apps will be calling GetVolumePathName directly with a back slash path name but Windows still caters for calls to GetVolumePathName that have a forward slash path name and maybe Mac programmers porting to Windows might happen to use forward slash pathnames or whatever, so there is a possibility that some Windows apps are going to call GetVolumePathName directly with a forward slash path name and so Wines GetVolumeNameW would need to be changed to cater for this as Windows can cater for it.