Settings

Every file on an NTFS volume has two sets of dates in its record in the $MFT. The set in $STANDARD_INFORMATION is the one Explorer shows, and any program can rewrite it. The set in $FILE_NAME is written by Windows itself when the file arrives or is renamed. If the shown created date is earlier than the $FILE_NAME one, the date was set back; if the shown time sits on an exact second while the other carries fractions of one, a tool wrote it. Finding neither does not prove the dates are true.

Why there are two sets of dates

Each file has a 1,024-byte record in the master file table. Two of its attributes carry the same four times, created, modified, record changed and accessed:

  • $STANDARD_INFORMATION is what Windows shows in Explorer and in a file’s Properties. A program sets it with one documented call, which is what timestomping tools such as Metasploit’s timestomp do, and so can a few lines of PowerShell.
  • $FILE_NAME holds the name and a copy of the times, written by the kernel when the file is created, moved or renamed. An ordinary program has no call that sets it.

On a file nobody has interfered with, the two agree when it arrives and drift apart in one direction only: the shown times move on as the file is edited, and the name-record times stay where they were. A shown time earlier than the name-record time cannot happen that way.

What it looks like

Three records made for this page, as MFT reads them. All three arrived on 3 October 2026; two have been interfered with.

FileShown createdName record createdWhat MFT says
report.docx2026-10-03 14:12:07.4412026-10-03 14:12:07.441Nothing: the two agree, and the shown modified time has moved on since, as it should
svchelper.exe2019-03-14 08:00:002026-10-03 14:20:51.317Created date is 2,760 days (about 7.6 years) before the name was created: the shown creation time was set back
update.dll2026-10-03 14:25:002026-10-03 14:20:51.717Created time is an exact second while the name-record time is not: sub-second precision was wiped, as timestomping tools do

The second case is the subtler one. Nothing about update.dll’s dates is impossible, but NTFS keeps time in 100-nanosecond ticks, ten million to a second, and a real timestamp almost never lands on a whole one. A shown time that does, beside a name-record time that does not, was written by something that only knew the time to the second.

Getting the $MFT

The $MFT is a hidden system file at the root of each NTFS volume, and Windows keeps it locked while the volume is mounted, so it is copied with a tool that reads the disk directly, or exported from a forensic image (FTK Imager does both). Take a hash of the copy before anything else if the result may be relied on; CHECKSUM does it in the browser.

Reading it without installing anything

  1. Open MFT on any computer and drop the $MFT on it. It reads every record, applies the fixups NTFS uses to detect a half-written record, and lists the files with both sets of times.
  2. Read the suspects first: they are listed at the top, worst first, each with the reason in words. The created and modified columns are the shown times, in UTC.
  3. If you already have a CSV from MFTECmd or analyzeMFT, TIMESTOMP reads that instead, and adds a softer check: a record whose date is out of step with the records numbered around it.

What the comparison cannot prove

  • That a file is clean. $FILE_NAME is out of a program’s direct reach, not out of reach altogether: a rename or a move makes Windows write it again, and an operator who knows that can bring the two sets into line. Fractions of a second can be forged by anybody who thinks to.
  • Who changed the dates, or when. The record says the dates disagree, not what made them. The USN journal and $LogFile record what happened to the file, and prefetch files, event logs and shortcut files date the same activity independently.
  • That the clock was right. Every time in the table is the machine’s own clock. A wrong clock moves both sets together and leaves them agreeing.

For reading the times themselves, see how to read a FILETIME and the other formats.

Questions people ask about telling whether a file’s dates were changed

How can I tell if a file’s timestamps were changed?

Compare the two sets of dates in its $MFT record. A shown created date earlier than the $FILE_NAME created date means it was set back, and a shown time on an exact second beside a name-record time with fractions means a tool wrote it.

What is the difference between $STANDARD_INFORMATION and $FILE_NAME?

Both hold a file’s created, modified, record-changed and accessed times. $STANDARD_INFORMATION is what Windows shows and what any program can change; $FILE_NAME is written by the kernel when the file is created, moved or renamed, and no ordinary program can set it.

What is timestomping?

Rewriting a file’s dates so it seems to have arrived at another time, usually earlier, to hide it among older files. Tools such as Metasploit’s timestomp do it with the same call any program can make, which changes only $STANDARD_INFORMATION.

Can timestomping be hidden completely?

By somebody careful, yes. A rename or a move makes Windows write $FILE_NAME again, which can bring the two sets into line, and fractions of a second can be forged. The USN journal and $LogFile are where to look next.

Where is the $MFT and how do I copy it?

At the root of each NTFS volume, hidden and locked while Windows runs. Copy it with a tool that reads the disk directly, or export it from a forensic image; FTK Imager does both.

Related tools

More on this

All 12 guides under “Was this changed, and is it genuine?”.

What your files give away

A one-page checklist of what a photo, a document or a PDF says about you, free now. Then one letter a month, with one new tip.

No spam, unsubscribe at any time, nothing is shared.