Fortunately, this is not deleting anything outside of the given library, but why is this happening at all? Was the code path to trigger the old bug ever fixed? I seem to recall Steam nukes and redownloads the steam runtime files on a crash timer, but Steam exited gracefully last time I used it. That bug involved the Steam launcher script running 'rm -rf' on systems with additional library paths. I'm wondering if this is related to a classic bug: A quick 'ls /steam' reveals nothing left. Now, a bunch of those games are grayed out with the need to be reinstalled. I use the library on my NVMe SSD (/steam/) for a few of my most-played games to accelerate load times (Warframe, Skyrim.), which is also marked as my default library. There is one steam library folder on each. My rig has three drives, two SSDs and one HDD. I'm just figuring out what happened, but this is the second time I have opened Steam and discovered that all of the Steam-related files in a specific library folder have been deleted.

Freefilesync portable 7.4