TC treats built-in directory junctions differently than mklink /J ones

English support forum

Moderators: white, Hacker, petermad, Stefan2

User avatar
Dalai
Power Member
Power Member
Posts: 9388
Joined: 2005-01-28, 22:17 UTC
Location: Meiningen (Südthüringen)

Re: TC treats built-in directory junctions differently than mklink /J ones

Post by *Dalai »

elgonzo wrote: 2020-09-10, 21:13 UTCOn a normal Windows installations, those junctions like "SendTo", "Application Data", "Start Menu", etc... have a particular rule set:

Code: Select all

Object: Everyone, DENY List folder/read data, this folder only, not inherited
I saw this rule when comparing the ACLs of the built-in SendTo and the user-generated one, but somehow I missed that this particular rule denies something. And I thought it doesn't matter. Looks like I was wrong.
The same ACL rule that is also responsible for the effect described by the OP. :)
Now it makes sense. Thanks!

Regards
Dalai
#101164 Personal licence
Ryzen 5 2600, 16 GiB RAM, ASUS Prime X370-A, Win7 x64

Plugins: Services2, Startups, CertificateInfo, SignatureInfo, LineBreakInfo - Download-Mirror
gdpr deleted 6
Power Member
Power Member
Posts: 872
Joined: 2013-09-04, 14:07 UTC

Re: TC treats built-in directory junctions differently than mklink /J ones

Post by *gdpr deleted 6 »

2umbra
👍
Post Reply