CReparsePoint and looklink

Author: Oliver Schneider


CReparsePoint is a C++ utility class without dependencies to the STL, MFC, ATL or some such. It allows you to retrieve all the data stored inside reparse points, the mechanism underlying junction points since Windows 2000 and symbolic links (both for files and directories) since Windows Vista. It also supports placeholder files on Windows 8.1 and later.

looklink is a simple tool to investigate reparse point properties from the command line.


No installation required. Download the binaries (32 and 64bit) from my website or Bitbucket. Use an archiver to unpack the archive, I recommend 7-Zip, and then place the .exe files into a folder listed in your PATH environment variable.

As for the utility class all you need is to place the files ReparsePoint.h and VerySimpleBuf.h into your project, #include the former and you should be set to use CReparsePoint.

Build instructions

In order to build the tool yourself, you'll either need the Windows 2003 Server DDK or Visual Studio. If you use the DDK, you can simply rely on the relbuild.cmd script, but you may have to set the WNETBASE environment variable to a sensible value (e.g. WNETBASE=C:\WINDDK\3790.1830) to match the path to the installed DDK.

If you prefer to use Visual Studio, a solution/project for Visual Studio 2005 is included and you can generate any of the other supported projects yourself using the premake4 that comes with the WinDirStat source code. Use a tool such as sigcheck to verify the code signature on it, though.

The way you generate the projects is by calling premake4 one of the following ways:

premake4 vs2005
premake4 vs2008
premake4 vs2010
premake4 vs2012
premake4 vs2013

The earlier Visual Studio versions may work, but no guarantees.


The program should run on Windows 2000 and later. Itanium CPUs are not supported, but feel free to build that yourself, if needed.

The CReparsePoint class should work starting on Windows 2000, too.



looklink [--nologo] [--verbose] [--noerror] <path>
  • --nologo will prevent showing all the information about the tool iself.
  • --verbose will add some details to the output, including the file ID on NTFS.
  • --noerror will suppress the error when <path> doesn't point to a reparse point.


The tools and the classes are placed into the PUBLIC DOMAIN/CC0.