The support forum

ProcessReparsePoint() errors

Arjailer :

Aug 28, 2015

I've been trialing Bvckup 2 on two Windows 10 installations. One is working absolutely fine, but the other is giving over 9000 ProcessReparsePoint() errors.

Mostly "ProcessReparsePoint() failed with 159" or 129, though there a few other numbers in there: 141, 171 ...

As an example:

2015.08.28 20:05:58.691 (UTC+0) 0 3             ProcessReparsePoint() failed with 141
2015.08.28 20:05:58.691 (UTC+0) 3 4                 Context: C:\Windows\notepad.exe

2015.08.28 20:05:58.696 (UTC+0) 0 3             ProcessReparsePoint() failed with 159
2015.08.28 20:05:58.696 (UTC+0) 3 4                 Context: C:\Program Files\Internet Explorer\IEShims.dll

2015.08.28 20:05:58.730 (UTC+0) 0 3             ProcessReparsePoint() failed with 141
2015.08.28 20:05:58.730 (UTC+0) 3 4                 Context: C:\Windows\AppPatch\AcLayers.dll

2015.08.28 20:05:58.730 (UTC+0) 0 3             ProcessReparsePoint() failed with 159
2015.08.28 20:05:58.730 (UTC+0) 3 4                 Context: C:\Windows\AppPatch\AcSpecfc.dll

The Bvckup setting for both installations are the same. Any ideas what's going on?

Alex Pankratov :

Aug 28, 2015

This makes no sense whatsoever.

The message itself merely means that specified files are not real files, but rather references to files in other locations *and* the app doesn't really know how to handle them.

Such references are formally called an "NTFS reparse point" and each of them comes with a type - it can be symbolic link, a link to an offline file, etc. There's a handful of well-known types and Bvckup 2 knows most of them. When the app bumps into the type it doesn't know it logs a message like the one you quoted below and the error code - 141, 171, etc - is actually the reparse point type it didn't recognize.

What is strange here is that reparse point types are generally in 0x80000000 range rather than in hundreds as it's in your case. There are no documented types of this kind.

Secondly, C:\Windows\notepad.exe has no business of being a reparse point to begin with.

If you don't mind sharing the whole log of that backup run, I can have a look and see if there's anything that helps to clear the picture. Just drop an email to

Arjailer :

Aug 29, 2015

Email sent.

Alex Pankratov :

Sep 01, 2015

This has been tentatively resolved.

Apparently these 9000+ files were both reparse points *and* sparse files. From what I understand it's either-or, never both - but here it is. Have no idea how this came about, but as we can detect this, we can work with it.

The fix will be in R74.16 and it's as simple as recognizing these "sparse reparse points" and treating them as usual files.

genl :

Jul 14, 2018

Do I understand this correctly? If backup source contains sparse files of 100 GB size but they are sparse files and actually use only 5 GB, Bvckup2 will write 100 GB of data to backup destination?

Would it be possible to actually create sparse files at backup destination after they are detected?

Alex Pankratov :

Jul 17, 2018

Your understanding is correct. Sparse files are copied as is, without retaining their sparse allocation information.

Everything is possible, but there are no plans for adding support for sparse file copying. I made a note though, let me see what we can do.

genl :

Jul 19, 2018

I was able to convert the files at destination into sparse ones, using sparse_checker.exe tool. I'm not entirely sure but the result looks very similar to the source, size wise. I did not try to run the backup job since then, it was one-time move from old HDD to the new one.

- I just targeted the folder with many files, not all of which were sparse at source. I assume the tool either left them as is or applied sparse regions and saved very little. I just don't have time to check the logs.
- Along with applying sparse regions, the tool updated modification date of such files.

There is another tool named cvt2sparse.exe, but it seems to save less space somehow.

New topic

Made by Pipemetrics in Switzerland

Blog / RSS
Social Twitter
Miscellanea Press resources
Legal Terms