Files not being seen

[comda]

Greetings CH members!

Its been a while, but as each day goes by, Windows 10 doesnt skip a beat to cheese me off. Got my Gaming PC up and going again with a fresh SSD and a fresh install. I had used the WD black drive as a slave drive and all worked great. I pulled the WD from this PC, and stuffed it into my old PC, which i now use to hold some of my data, and copied a few personal files and installers over to the drive, and stuffed it back into the Gaming rig. Drive shows up no problems. GREAT. But that folder i copied over isn't there. Stuffed it back into my old PC, that folder and files are there. So what gives? The files are there on the drive, but the PC doesn't see them. And yes, hidden folders are on but its not a hidden folder. My older PC runs Windows 7 pro, while this runs a fresh install of 10. Not sure if that really makes a difference, but 10 is annoying me.

Specs are
HP Z620 Workstation PC.
Intel Xeon E5-2640 @ 2.5Ghz
16gb DDR3 Ram
500gb Samsung SSD + 1TB WD Black Slave
AMD Rx570 GPU
Windows 10 Professional.

Any suggestions are greatly appreciated.

[SuperDave]

Instead of switching the hard drive back and forth why not use another method of transferring the folder/files such as a USB stick or a CD?

[comda]

Because I find using a middle man absolutely pointless. Its so easy to pull the drive and copy the file required immediately where I want and need it, instead of pasting it to an external drive, then coping to that drive and from that drive.

I dont know how I fully did it, but I did and the folder appeared after some fiddling around. 

Just wastes time copying to another drive, if its as easy as grabbing the handle to the side panel, and the handle to the hot swappable drive bays.

THanks,

Comda.

[patio]

If it's bein swapped between PC's you need to take ownership of the full HDD then the folder will be accessible...

[patio]

This is whats called an undocumented feature from MS because they want to protect us since they think we are idiots...

End of Rant.

[BC_Programmer]

When you create a file the Creator is specified in the file/folder information using the user's SID. the SID is auto-generated when a user account is created.

When you remove the drive and plug it into another computer, even if the user account has the same name, the SID will be different. As a result, when accessing it from the other system, the account is no longer the owner.

For most files, this doesn't matter- for example you can format an external to NTFS and typically access it anywhere. However, for User folders, files and folders are typically set such that the Access Control List does not allow access to just everybody. This prevents users from snooping and altering files in other user account folders. (Imagine if a non-admin user could alter the start up folder of an admin user!). As a result, though, when you access user account folders on a drive by connecting the drive to another system, the new system sees that the creator does not match, and that the user is not in a group that has access to the file. The Dialog that appears with the "Allow Access" Option adds your user account on that system to the ACL of the file/folder.

As far as this specific problem- I would guess that the files and folders that were copied are such that the permissions on the file do not allow the user account on the other PC to enumerate or view them.