Check disk on Win 10 SSD

I have Win 10 on a dedicated SSD (BX500 - CT240BX5)
If I use Win 10 and then, from Win 7, I run Chkdsk E: /f (windows partition) it finds hundreds of files that are fixed deleting extended attribute set due to the presence of reparse point in file xxxxx.
Chkdsk F: /f (data partition on same drive) doesn't find any error.

Something is corrupting the Windows files.
As I alternate from Win 10 to Win 7 (on another drive) i was thinking if it could be a Win 10 issue. Hibernation is of (powercfg -h off).
Never find any error on other partitions, only on Win 10.

Any suggestions?

Win ver 22h2 Build 19045.2364

@Megahertz


If I understand you correctly...
I would run Windows 10 chkdsk on the Windows 10 partition.

I would also run chkdsk /r
The /r flag implies /f anyway.

Could this problem be something to do with it [Fixed] Running ChkDsk on Windows 10 20H2 may damage the file system and cause Blue Screens

Thanks Samuria, but I don't run Chkdsk from Win 10. I run it from Win 7. And as I've mentioned, only the Win10 partition has issues.

This is weird. I just booted into Win 10, and on exit I booted on Win 10 installation WinPE, ran chkdsk C: /f and it didn't find any problems.
Restart and booted on Win 7 and ran chkdsk E: /f. It began to fix "deleting extended attribute set due to the presence of reparse point in file xxxxx" hundreds of files.

Why Win 10 chkdsk doesn't detect and Win 7 chkdsk find hundreds of files to fix?

Megahertz said:

This is weird. I just booted into Win 10, and on exit I booted on Win 10 installation WinPE, ran chkdsk C: /f and it didn't find any problems.
Restart and booted on Win 7 and ran chkdsk E: /f. It began to fix "deleting extended attribute set due to the presence of reparse point in file xxxxx" hundreds of files.

Why Win 10 chkdsk doesn't detect and Win 7 chkdsk find hundreds of files to fix?

Probably because Win 7 chkdsk is expecting to scan a Win 7 install. Instead it's scanning a Win 10 install (that's built differently), so it sees what it "interprets" as errors.

The actual chkdsk tool is probably the same, but it's looking for the wrong things, so it sees errors.
It's probably something weird like, different cluster sizes or something.

Analogy: Maybe Win 7 has round sectors and Win 10 has square sectors (just kidding ofc). Might be different size sectors. The sectors might be arranged slightly differently.

You buy an Ikea coffee table and an Ikea bookshelf. They both come with an Allen wrench for assembly.
I'd bet money that the wrench that came with the coffee table is for the coffee table bolts, and the wrench that came with the bookshelf is for the bookshelf bolts.

You need to use the right tool for the job.

SIW2 said:

is fast startup on ?

I did not disable fast start.
Hibernation is off (powercfg -h off), so I suppose fast start is disable.

zbook said:

If possible, make a free backup image of the Windows 7 installation and reinstall Windows 7.
Then see if the problem persists or disappears.

I have tested in many ways (My main Win 7, my backup Win 7 and Win7PE). Same results.

Ghot said:

Probably because Win 7 chkdsk is expecting to scan a Win 7 install. Instead it's scanning a Win 10 install (that's built differently), so it sees what it "interprets" as errors.

chkdsk don't scan a OS or whatever is on the partition. It scans data structure and for what I know, Win 7 NTFS is the same as Win 10 NTFS.