Except my method does work. Gain an understanding of how the NTFS filesystem and even the NT kernel works. I was a dick because you had suggested the same damn thing that does not work that others have posted. I know exactly how the take ownership command works as well as standard NTFS permission properties. But again, like I've explained before, if permissions on a file belong to a non-existent user on the system, NTFS fucks up. It is the only filesystem that does this. This is what causes the error. When swapping around drives, especially external ones, permissions for users on one system are set but are not removed once the drive is connected to another system. Due to NTFS retaining these permissions, Windows goes "uh durr, the FS says this user exists so it exists" when it really doesn't. Even creating a user with the same name and assigning permissions to that user does not fix the issue since every NT system user has a UUID (which is displayed instead of the user's name on the permissions window when said user does not exist on the system). This is why take ownership does not work in this scenario.
Sorry for being a dick, but I get sick of people throwing up the same wrong information way after the solution has been posted.
I can't access my NAND.bin, because I don't have the permission to access it, not even as NT AUTHORITY\SYSTEM 
