https://docs.microsoft.com/en-us/windows/desktop/FileIO/naming-a-file
Not a proton bug. This is how wine represents its structure and its valid under Linux/Unix (naming conventions).
Now I am not sure but you could try using WSL (Windows Subsystem for Linux) or under a Linux VM to delete this.
lol
Maybe they should disallow Proton on Windows because obviously someone did it lol
Doesn't matter, it's still a fault that needs addressing. A solution would be to prevent proton being cloned to external library directories, as it currently does and where this issue primarily originates. This is not a direct fault of wine, as it doesn't expect its files to be cloned about in the first place.
Maybe they should disallow Proton on Windows because obviously someone did it lol
Could have been a dual boot situation using the same SteamLibrary.
Could have been a dual boot situation using the same SteamLibrary.
Exactly that configuration, to shared NTFS drives.
It should be noted that sharing the same Steam library across multiple platforms has never been supported and can have undefined results.
It should be noted that sharing the same Steam library across multiple platforms has never been supported and can have undefined results.
irrelevant, and it's windows <> windows anyway, there shouldn't be any differences unless the game was built with different win API revisions for some reason
What do you mean it's windows <> windows? Didn't you use Linux to install Proton on NTFS drive? You didn't provide any steps to reproduce the issue.
It should be noted that sharing the same Steam library across multiple platforms has never been supported and can have undefined results.
irrelevant, and it's windows <> windows anyway, there shouldn't be any differences unless the game was built with different win API revisions for some reason
Congrats telling Valve they're are wrong lol
Blocking is right technically correct since what you did doesn't work (Proton is meant for Linux). And, sharing like Kisak says isn't supported but still I haven't seen this problem that way - it has its problems though and still shouldn't be done because all people will do is to post bugs and complain thinking it is supported.
Since they don't support it and it isn't what they created it for then it should be blocked until they decide to do something about it.
But, I'm not going to reply to any further replies about this topic. My view point is ^ right there.
@kisak-valve just close this stupidity + wontfix/notabug
This issue should be kept for reference
I use ntfs external disk for dual boot gaming. One time , steam download 'Proton Next' to ntfs. Everytime i boot windows, said disk need to be repaired, then I repair using windows, but windows give up with unspecified error. All read write operation is normal
In windows explorer, c: is a file with 100GB size which is impossible to delete using linux and windows . Is there any way to delete it?
It would probably be useful to have a FAQ advice how to delete such files even if it’s not a bug of Proton. In my case, undeletable files were named com1, com2, etc., and occupied about 1000 bytes in total in two folders. Did not have files like c: as the OP described.
One of the folders was:
steamapps/common/Proton 3.16/dist/share/default_pfx/dosdevices/
NTFS Access by nGlide author did not help. Was able to delete com* files with Unlocker 1.9.2.
proton 3.16x1 2023-05proton nextx1 2023-02
If a steam library is created on a windows disk, with proton enabled, illegal/reserved name files are created under dosdevices, of which are impossible to handle inside windows. COM files can be brute-force deleted via powershell, however disk devices cannot.