Most Windows users never think about NTFS — the file system that manages every file on their drive. Yet NTFS has several default settings that made sense for 1990s hard drives but create unnecessary overhead on modern SSDs. Tweaking these settings can reduce file I/O overhead, improve directory enumeration speed, and eliminate a few hidden CPU cycles from every disk operation. Here’s how to do it safely.

Open an Elevated Command Prompt

All changes below require an Administrator command prompt. Press Win + X → select Windows Terminal (Admin) or Command Prompt (Admin).

Disable 8.3 Filename Generation

NTFS automatically generates an 8.3-format short name (e.g., PROGRA~1) for every file with a long name, for compatibility with 16-bit software that no longer exists on modern systems. This adds overhead to every file creation and directory listing.

Check the current status:

fsutil behavior query disable8dot3

A return of 0 means 8.3 names are enabled (the default). Disable them:

fsutil behavior set disable8dot3 1

This takes effect immediately for new files. If you want to strip existing 8.3 names from a drive (takes time, do when idle):

fsutil 8dot3name strip /s C:

Impact: Faster directory listing on drives with many files (thousands of entries), slightly faster file creation. Most noticeable on large code repositories and software directories.

Disable Last Access Timestamp Updates

By default, NTFS updates the Last Access timestamp on every file every time it’s read. On an SSD with millions of daily reads (browser cache, system files, application data), this generates enormous write amplification.

Check the current setting:

fsutil behavior query disableLastAccess

A return of 0 or 2 means last access timestamps are enabled. Disable them:

fsutil behavior set disableLastAccess 1

Windows 10 and 11 handle this more intelligently than older versions — they batch updates — but explicitly disabling it removes the overhead entirely.

Impact: Reduced write amplification on SSDs, marginally improved read performance, extended SSD lifespan over years of use.

Increase the NTFS Memory Zone

NTFS maintains a memory pool for managing file operations. On systems with ample RAM (16GB+), increasing the NTFS pool improves throughput for large file operations:

fsutil behavior set memoryusage 2

Value 2 allows NTFS to use more of the available RAM for caching metadata. On systems with 8GB or less, leave this at default (1).

Optimize the MFT (Master File Table) Zone

The Master File Table is NTFS’s index of every file on the volume. When the MFT grows beyond its reserved space, it fragments into the general data area, causing performance degradation. Setting a larger MFT zone reservation prevents this:

fsutil behavior set mftzone 2

Valid values are 1–4, representing 12.5%, 25%, 37.5%, and 50% of the volume reserved for MFT growth. For a drive used heavily for small files (code projects, documents), 2 (25%) is a good balance. For media drives with mostly large files, keep it at 1.

Disable Encrypted File System (EFS) if Not Used

If you’re not using Windows’ built-in file-level encryption (EFS), disabling it removes a small layer of processing overhead from file operations:

fsutil behavior set disableencryption 1

Note: This is for EFS (per-file encryption), not BitLocker (full-disk encryption). BitLocker is managed separately and unaffected by this command.

Check NTFS Volume Information

Before and after tuning, you can inspect volume statistics:

fsutil volume diskfree C:
fsutil ntfsinfo C:

fsutil ntfsinfo shows MFT size, record size, cluster size, and other internals useful for confirming your changes took effect.

Adjust Cluster Size for Specific Workloads

NTFS cluster size is set at format time and can’t be changed without reformatting. However, if you’re setting up a new drive:

OS/Applications drive: Default 4KB clusters — optimal for mixed small/large files
VM storage drive: 64KB clusters — reduces fragmentation and improves sequential I/O for large VHDX files
Media storage drive: 64KB clusters — better for sequential writes of large video files

Format a new drive with custom cluster size using PowerShell:

Format-Volume -DriveLetter D -FileSystem NTFS -AllocationUnitSize 65536 -NewFileSystemLabel "Media"

Verify All Changes

Run this to see the current state of all behavioral flags:

fsutil behavior query disable8dot3
fsutil behavior query disableLastAccess
fsutil behavior query memoryusage
fsutil behavior query mftzone

Your output should show:

NtfsDisable8dot3NameCreation = 1
NtfsDisableLastAccessUpdate  = 1
NtfsMemoryUsage              = 2
NtfsMftZoneReservation       = 2

What Not to Touch

Avoid disabling the NTFS change journal (fsutil usn deletejournal). The change journal is used by Windows Search, antivirus software, backup tools, and development sync tools like WSL and Visual Studio. Disabling it breaks more than it helps.

Similarly, leave the NTFS log file ($LogFile) intact. It enables crash recovery and prevents file system corruption after an unexpected power loss.

Expected Results

These NTFS tweaks are not going to double your benchmark scores — they’re micro-optimizations that compound over time. Users report:

Faster Visual Studio solution loading on large projects (fewer directory stat calls)
Slightly better ls/dir performance in terminals with thousands of files
Reduced SSD writes over months, beneficial for drive longevity
Marginally snappier file explorer navigation in deep directory trees

Combined with other Windows 11 optimizations — proper power plans, SSD TRIM enabled, StorPort tuning — NTFS tweaks help round out a well-optimized system.