Windows 10: chkdsk reparse point errors - repeatedly

Hello,

Does anyone have experience of repeated 'extended attribute set and a reparse point detected in file xxxxx'errors in chkdsk in windows 10? - even though it apparently corrects the errors with 'deleting extended attribute set due to presence of reparse point in file xxx' - the errors are still there whern I reboot (immediately once Windws has loaded).

I've done the full chkdsk /f /r and repaired the image using DISM and the latest .iso from Techbench. sfc /scannow does not return any error messages.

Thanks.

:)

 

Reparse point deletion

Today I had to run a chkdsk on my drive

All goes ok when I read a message

Deleting extended attribute set due to the presence of reparse point ...

On the net I found that reparse points are like symlinks in Linux and I'm worried them deletion can cause problems

I seriously have to be worried about this?

 

Windows 10 File History Problem

Windows 10 Pro 64bit. I just discovered that my file history has not worked in a long time, with no notification that there was a problem. In reading the long list of errors, it seems that failure is being caused by something called a "reparse point" and
the error tells me to delete said critter. Problem expands because there are many path locations for these reparse points, some of which have access denied (i.e. users\Bob\appdata\local\application data).

Altho I've been with windows since the very beginning, I have never heard of a reparse point and haven't the slightest idea what one is, or how to id it if i see one, or how to avoid one.

Can anyone help me with this? The only article I have found that mentioned reparse points dealt with windows server and the language made no sense to me.

 

Please upload the log of chkdsk. I'm on phone now so cannot post instructions for how to upload the log.

 

Very odd. what I've been doing is running chkdsk from a dos window at boot - obtained as part of Macrium reflect rescue environment. Initially, there were thousands of such errors but it's now down to just a few. Now when I use chkdsk from Powershell on the desktop (chkdsk c*Smile it doesn't show any errors. Running chkdsk c: /f needs a reboot which doesn't show any error messages or details which is why I used the Macrium Reflect facility. I can't find anything meaningful on Google about this issue.

I follwed this but it did not return anything at all.

How to find chkdsk results in Windows 10

 

How to find & upload the chkdsk log *Arrow Chkdsk Log in Event Viewer - Read in Windows 10 - Windows 10 Forums

 

I've done that now but it only returns the last chkdsk which shows no errors. Is it worth uploading that?

 

Possibly, it may contain some things that have been changed.

Could you reproduce the repeated error from chkdsk in Macrium recovery?

 

I've done that now but it only returns the last chkdsk which shows no errors. Is it worth uploading that? I did chkdsk c: from WIndows 10 and it showed no errors. I then rebooted into the Macrium reflect environment, did chkdk again and there were more than 3000 filesshowing the error. It looks like it's the dos window attached to Macrium reflect that's the issue here. I'll avoid that in future.

That's fir your interest and help - and to everyone who contributes their expertise and hard work to assist others on this forum.

 

When was the last time you recreated Macrium recovery?

 

This morning! the dos window is version 6.1.7601

 

windows 10 dod window is 10.0.10240

 

The kernel in the Macrium Reflect rescue environment was set to Windows 7 so I've re-created it to sute windows 10