Verify and repair

Verify

Verify & repair runs diskutil verifyVolume against the selected volume and shows the real command state. It does not animate a fake percentage or invent a health score.

Read the output and the final state, not only the spinner.
A successful exit code is evidence that the command completed, not a guarantee that every file is readable.
For a write-sensitive workflow, unmount the volume before verification if the tool or macOS requires it.

Basic repair

ntfsfix can clear some dirty flags and repair limited metadata. It is not a replacement for Windows chkdsk /f.

NTFS Kit therefore enforces:

The volume must be unmounted.
You confirm the repair explicitly.
The command and its output are recorded in the activity log.
The result is reported as basic repair, not as a full filesystem check.

If corruption is suspected, stop and back up first. Run a full check on Windows when possible.

Before you repair

Check	Why
Backup exists	Repair writes filesystem metadata
Volume is unmounted	Mounted volumes can be busy or inconsistent
Disk is connected and powered	A disconnect during repair can make things worse
Windows Fast Startup / hibernation is off	A hibernated Windows volume may be in an unsafe state
You know which volume you selected	The device node and UUID are shown before the action

What the app will not claim

It will not claim that ntfsfix found or fixed every error.
It will not claim that a volume is healthy because a command exited zero.
It will not run repair on a mounted volume.
It will not hide a failed repair behind a generic success toast.

After repair

Re-run verification and compare the output.
Mount read-only and inspect the files you care about.
If the volume is still dirty or unreadable, use Windows chkdsk /f or professional recovery. Do not keep running destructive operations on a suspect disk.