Bug: Directory Junctions

I have a folder on one physical drive (D:) with a Directory Junction on another drive (C:) that points to that folder. There’s no point to scanning the same files twice, so I have set an Exclusion on the Directory Junction “folder”. However, Norton 360 follows the Directory Junction and scans the folder anyway. I have a sub folder in that folder that I don’t want scanned. I’ve also set an Exclusion on the D: drive for that subfolder and it gets ignored, as it should. However, since the Directory Junction is being followed, that folder keeps getting flagged as having files in it that Norton 360 thinks are bad. I’m an IT instructor at the local community college and I have some Penetration Testing files in there for demonstrations. However, regardless of what’s in there, an Exclusion has been set and, therefore, they should be ignored, not to mention the double scanning of the Parent folder that the Directory Junction leads to.

OK, I think I figured this one out. For backwards compatibility, Windows creates a Hidden/System file called “My Documents” and this is what was being followed, not my Junction that I created. I have Excluded this Hidden/System file and that solved the problem.

1 Like

Thanks for the feedback post.

SA