Skip to main content
Storage & files

Filesystem Integrity

Detect Windows volumes that are flagged as dirty and need a chkdsk run at the next boot.

The Filesystem Integrity check runs fsutil dirty query on a Windows device to find out whether a volume is flagged as dirty. Windows checks a flagged volume with chkdsk at the next boot. The check runs locally through the octoja agent, on Windows only (x64 and ARM64), every 60 minutes by default.

Prerequisites

  • You need the Monitoring Check Management permission.

Steps

  1. Open the device under Devices.
  2. On the Checks tab, click Add Check → Filesystem Integrity.
  3. Leave All fixed drives enabled, or turn it off and enter the drive letters to check under Drives.
  4. Click Add Check.

To assign the check to many devices at once, use a config package.

Settings

FieldTypeRequiredDefaultDescription
All fixed drivesBooleanNoYesAutomatically check every fixed local drive and ignore the list below.
DrivesList of stringsNoC:Drive letters to check, e.g. C:. Visible only when All fixed drives is off.

With All fixed drives, the check covers every drive that Windows reports as fixed; network drives and removable media are not included.

Results

SituationResult
No checked volume is flaggedOK
At least one volume is flagged (Dirty (chkdsk needed))Critical
All fixed drives is off and the Drives list is emptyWarning
The query returns no resultWarning
The query failsError

The result lists every checked drive as Clean or Dirty (chkdsk needed).

Platform support

PlatformSupported
WindowsYes (x64 and ARM64)
LinuxNo
macOSNo

Notes

  • The check recognizes the result from the English output of fsutil. For other display languages it falls back to the fsutil exit code.
  • The check repairs nothing. For a flagged volume, schedule a restart so that Windows runs chkdsk, and then review the result.
  • The agent runs as Local System; there is nothing to set up on the device.

See also: Set up alerts for a check