System uses two Windows installations side by side, each with its own folders and files.
System uses two Windows installations side by side, each with its own folders and files.
I have Windows 10 set up on two hard drives, along with a few shared storage drives. After installing a fresh Windows 10 version a few weeks ago, I was able to see and work with all files on the storage drives while using either drive. At that time, the original drives still held all the files, but now any folders, files, or programs I make on those drives disappear from view in the other installation. The space they occupy isn’t showing up, and when I switch back to the other Windows version, everything appears normal—files are visible, accounted for, and Steam recognizes them as installed. This behavior also occurs with folders I create manually on the storage drives and files I drag into them. When I boot into the alternate Windows, those folders vanish entirely. Could you help me understand what’s happening?
It seems the issue relates to NTFS permissions. Navigate to the folder, open properties, then security settings. Only the current user appears with access—consider adding a guest or another user with full privileges. (The label might be "Everyone," but rights aren't verified yet.) Repeat the process for any other Windows installation.
Basic files are compatible across different windows, though some programs or games might not work. Certain apps need registry changes or specific add-ons like DX, VB.NET, etc., which could be missing on other systems. In your situation, it could be a permission problem—try reverting to the old settings before making changes. To check if permissions are the issue, boot from a Linux USB drive and see if files appear normally; Linux ignores window permissions in this case.
The situation appears linked to both folder settings and broader system configurations. It seems the folder access issues stem from inconsistent permissions across different environments. After installing Steam on a freshly set up Windows 10, I noticed the game worked in one boot while failing in another. The game folder showed up in one drive but was marked as uninstalled or inaccessible in the other. Checking the folder details revealed size mismatches and security restrictions. When trying to view properties, I encountered permission errors that prevented seeing group details. After adjusting network sharing to full access, I regained control over folder settings. However, even then, some folders remained restricted despite having appropriate user permissions. The problem persisted when creating new folders manually or through Steam, suggesting deeper configuration conflicts. It appears the issue is tied to how Windows handles shared resources and access controls across installations.
Upon restarting the fresh Win 10 setup and switching back to the original installation, the folder access for the newly downloaded game—which displayed a warning about needing read permissions—has become corrupted. This prevents me from opening the folder properly.