There is a task called Data Integrity Scan in Windows 8.1 Task Scheduler, which is disabled. It says that it "scans fault tolerant volumes for latent corruptions". Googling didnt help much. It says that it has something to do with ReFS filesystems, but my SSD and HDDs are all NTFS. Someone on the MS forums speculated that it has functionality beyond ReFS only, but didnt get a real answer. The Data Integrity Scan for Crash Recovery task below it is enabled. Does this feature do anything for NTFS formatted drives? What makes me wonder, is that the task named the same thing is enabled by default in Windows 10.
Doesnt really say anything. Under actions its just "custom handler". Doesnt seem to show up in any identifiable way in Process Explorer either.
Oh come on someone on here with more Windows knowledhe than me must know? Maybe i should have posted this in the OS section? Can someone move it please?
I doubt that. Since there is no actual info in task we can only guess. I don`t get why you turned on by this task. About fault tolerant volumes https://technet.microsoft.com/en-us/library/cc960873.aspx Do you have RAID volumes?
Because i like the idea of scrubbing SDCs, and no i dont have any HDDs in RAID. Since its on for NTFS volumes in Windows 10, i want to know if it does something for systems not using ReFS or RAID that can improve SDC handling.
Yeah i get that, but why is it enabled by default in 10 and disabled in 8.1? What functionality beyond the fault tolerant ReFS scrubbing for SDC does it possess?
But is is not enough for a task to be enabled. Was is launched ever? If it wasn`t then no functionality for sure.
Its scheduled to run every four weeks by default in 10 and 8.1(although its disabled by default for 8.1). The other data integrity scan for crash recovery is enabled and triggered by drive failure for both 8.1 and 10.
"Scheduled" is not equal to "launched". Update: Ok, I am at Win10 now, so I went to Task Scheduler and found that task "Data Integrity Scan". It is enabled but both its triggers (weekly and at startup) are disabled and task was never ever executed.
