reparsepoint

I am using Directory.GetDirectories() with a Linq statement to loop through all directories in a folder that aren't system folders, however I am discovering a bunch of bad ReparsePoints in the folder, which is causing the method to take a long time as it times out on each bad reparse point. The code I am currently using looks like this: subdirectories = directory.GetDirectories("*", SearchOption.TopDirectoryOnly) .Where(d => ((d.Attributes & FileAttributes.Hidden) != FileAttributes.Hidden) && ((d.Attributes & FileAttributes.System) != FileAttributes.System)); I have also tried using code like

Closed. This question is off-topic. It is not currently accepting answers. Learn more . Want to improve this question? Update the question so it's on-topic for Stack Overflow. From a high-level standpoint (meaning only worrying about the results and the interface, not the implementation), what is the difference in behavior, if any, between an NTFS reparse point that points to a directory and a symbolic link that points to the same directory? Are they resolved at the same level in the stack, or is it possible for one to be unresolvable at a certain time when the other one can be resolved (e.g.

Update : This question has evolved into a question about the NTFS filesystem filter driver how to use the Win32 API in backup applications and other programs that need to know what a file really is on disk ? Junctions and reparse points are key concepts that I needed to consider and are the most confusing thing in the NTFS filesystem. The original question follows: What is the Win32 API used to detect if a directory is a junction? 'Where' (for lack of better understanding) in the NTFS hierarchy are junctions stored? If I create a junction c:\thejunction_mydir do both directories become

I am trying to get the target of a junction in my program, but the only way I managed do it is: Requesting Backup privileges p-invoke CreateFile with special parameters to get a handle to the file/dir. DeviceIoControl call to the get the target. The 1st step will not work with normal user accounts, because they have no Backup privileges, and I don't want to get the UAC User Consent window every time I do this. I think this is doable somehow, because a normal "dir /A:L" command resolves the target of the links. flq I think that this answer in stackoverflow would help you? How do I