I recall this thread. Sorry you didn’t receive an answer, but there was
another member in a very similar circumstance at the time of this thread’s creation, and, IMO, has worded their situation a little better. I was hoping you’d perhaps draw some answers from there instead, as these kinds of threads take a while to solve.
I feel your OP has fallen victim to the
XY problem, that is, where you attempt to explain a solution to your problem rather than your actual problem.
Some actions you insist on carrying out make little sense, for instance, revoking and reapplying permissions for “Authenticated Users”, “SYSTEM”, “Administrators”, and “Users”. These trustees are universally well-known identities across Windows systems. They are generic and not specific to a machine, so removing them only to re-add them again exactly as they were, but using a different machine, would make no difference and just be a long and daunting exercise.
If there is a specific problem you are facing, please provide concise details about this exact problem. Perhaps you may begin by explaining the nature of the trouble you are experiencing here:
[...] I think it's causing trouble with Win7/64 Ultimate.
Your post is well taken, and you're completely correct. That was one crummy post. Unfortunately, from a fault-isolating point of view, this one isn't much better.
Hop down to "
SEEMS TO WORK" below if you don't want to read what was bugging me, because apparently I've lost my mind.
After having tried so many different possible solutions, I was essentially asking for a way to punt down to a baseline configuration and add back Win7Ult owners and permissions by hand, because even retracing what I had tried was becoming confusing as hell.
I routinely would copy the XP folder over and try again.
Speaking to the XY problem: I was trying to grant access to accounts other than mine to an old UnrealTournament installation that had been pulled directly from an old XP system. It
had been copied to the local drive (from the XP drive accessed by a USB-IDE reader). But I could access the contents of one of its folders from my account (a member of administrators, and the one that did the copy), from Administrator, but not from my wife's account (a member of administrators) nor my Kids account.
I've configured permissions and ownership before with success a few times elsewhere, but this was something I wasn't expecting.
When I stripped out the Kids access from the permissions, it was gone. When I added it back, I got two of them. Two. Huh?
I figured I must have had some oddball conflict going on from the XP/Kids and my Win7/Kids, or perhaps some subfolder inheriting from the parent the old XP/Kids once a Win7/Kids permission was added?
I also figured that I knew just enough to be dangerous, and just enough to sledgehammer things back when it was on XP, and it was carrying through to now. However:
The
SEEMS TO WORK section
Anyway, I discovered something very recently. I had enabled parental controls on the Kids account, but had not told it to deny anything at all, so I figured it was inert. But on a whim, I disabled parental controls.
1. My wife's account could access the folder. (She was never part of parental controls!)
2. Kids could access the folder.
3. Adding Kids permission specifically to the folder didn't add two Kids permission entries.
The "
BUT..." section
The reason I'm still asking about this is because I may soon be in the need of enabling parental controls again, and I don't want to go through all this all over again, so I thought a reasonable approach would be something analogous to the unix chown nobody:nogroup and chmod 000, while removing all inheritance of permissions from parent folders as well.
Just to start at a known baseline and rebuild everything from there.
