The IFile­Operation::Set­Operation­Flags method accepts a number of flags to modify the file operation, among them today’s subject FOFX_NO­SKIP­JUNCTIONS. A customer reported that they couldn’t get this flag to work: Whether they set it or not, the IFile­Operation skipped over file system junctions. The term junction evolved two independent different meanings. The shell team invented the term shell namespace junction in Windows 95 to refer to a point in the shell namespace in which one type of namespace extension is grafted into another. For example, a directory of the form name.{guid} serves as the transition point between the default file system namespace and a custom namespace. Meanwhile, the file system team developed the term NTFS junction point to refer to a directory entry which links to another location. If you just hear the word junction by itself, you need to use context to determine whether it is short for shell namespace junction or NTFS junction point.

Since IFile­Operation::Set­Operation­Flags is a shell interface, the shell interpretation is more likely (and is the correct one in this case). The FOFX_NO­SKIP­JUNCTIONS flag has no effect on the behavior of the IFile­Operation interface on NTFS junction points; it modifies the behavior on shell namespace junctions.