When I run chkdsk /r I get thousands of reparse records processed which takes forever. Windows puts them in. Windows deletes them. Why would that be? For instance about three weeks ago there were "29521 reparse records processed.", today: "32542 reparse records processed.", few months back was over 40 thousand, and all due to for instance, "Deleting extended attribute set due to the presence of reparse point in file 300433." And I don't even know what files 300433 or 300420 ... are. Is there anything I can do to stop those records from being made in the first place if the have to be deleted?
Couple of hits on Google about this https://www.tenforums.com/performance-maintenance/53282-chkdsk-reparse-point-errors-repeatedly.html https://answers.microsoft.com/en-us...t/81776bec-00ab-4e3e-9254-2d80e426dcfa?auth=1
@Brian K, ATI. The recent GUI is intolerable, badly designed, and obsessed with scheduling, so I do images by ATI bootable flash. Few times I pulled couple files out of an image using explorer. And few times I restored images. Syncback takes care of data partition. I don't sync with anything. It just goes out to external drives. I'm still reluctant to abandon ATI since I have have many old images which only ATI can read. But I may have to bite the bullet at some point. I've been all over google trying to figure out what makes those useless records that have to be deleted. No information really, other than few muddy mentions related to mounting. That is beginning to make me think that perhaps in explorer ATI tibmounter service/process might be causing something. This one has thousands of records, just like mine. As usual - no explanation, no solution: https://www.tenforums.com/installation-setup/38269-win-10-install-lots-reparse-errors-chkdsk.html
@stapp, I answered Brian K and forgot to answer you. I saw those links as well, the first one mentioned Macrium, but I don't understand the impact. The second wants me to do clean boot routines and test - well, each test takes over an hour, so I'm not eager for that. Then it mentions dual booting, but on separate drives. I do dual boot on one drive, legacy, no hibernation or fast startup.
