An NTFS drive that will not mount can fail at several layers: the cable, the enclosure, the partition table, the NTFS volume itself, macOS Disk Arbitration, or the file system extension. Work from the bottom up instead of reinstalling everything.

Triage: match the symptom

Symptom	Start here
Disk not in `diskutil list`	Cable, port, enclosure, power
Disk visible, volume not mounted	Filesystem state, dirty volume, extension
Volume mounts read-only	NTFS is read-only by default, or the volume is dirty
Write fails with “Read-only file system”	Dirty or hibernated NTFS; read/write not engaged
Extension will not enable	Registration, stale app copy, macOS version
Worked before, now fails	macOS update, extension state, cable, disk health

Step 1: Confirm macOS can see the disk

diskutil list

If your disk is missing:

Try another USB-C or Thunderbolt cable. Charge-only cables are common.
Try another port, preferably directly on the Mac.
Use a powered hub for bus-powered drives.
Open System Information → USB or Thunderbolt and confirm the device appears.
Test the drive on another computer.

If the block device is absent, no NTFS driver can mount it. Do not keep replugging a drive that clicks or disconnects.

Step 2: Inspect the partition

Find the NTFS partition identifier, then run:

diskutil info /dev/disk4s1

Replace disk4s1 with your identifier.

Look for:

File System Personality: NTFS
Read-Only Volume: Yes
Mount Point (empty means not mounted)
Volume Name

If the filesystem is not NTFS, the problem is different. For example, exFAT is writable, so a read-only exFAT drive points to permissions or hardware.

Step 3: Check the mount state

mount | grep -i ntfs

The output shows the device, mount point, and flags. read-only is expected until you explicitly choose read/write.

To mount manually for testing:

diskutil mount /dev/disk4s1

If diskutil reports that the volume failed to mount, note the error. On macOS 27, Disk Arbitration may refuse third-party FSKit modules with status 0xC05C; Mountee handles this with its own fallback path. Other tools may not.

Step 4: Check the extension state (Mountee)

If you use Mountee, the app’s extension must be enabled for your user.

/Applications/MacNTFS.app/Contents/MacOS/MacNTFS --extension-status

Expected results:

enabled — ready.
disabled — enable it in the app or System Settings.
not-registered — launch the app once, then enable it.
unknown — collect diagnostics.

You can also inspect FSKit modules:

pluginkit -m -p com.apple.fskit.fsmodule -vv

The Mountee module appears as com.github.alvarolorentedev.macntfs.ntfsmodule. Check that the path points to the app you are actually running.

Enable it

Launch Mountee from /Applications.
Press Enable File System Extension.
Or open System Settings → General → Login Items & Extensions → File System Extensions.

The setting is per user. Enabling it in one account does not enable it in another.

Step 5: Rule out a dirty or hibernated volume

A volume that mounts read-only even after you choose read/write is usually dirty. This happens when Windows used Fast Startup or hibernation, or when the drive was unplugged during a write.

Check the Mountee log:

log show --last 10m --predicate 'subsystem == "com.github.alvarolorentedev.macntfs.ntfsmodule"'

Notice-level messages include the downgrade reason.

Fix on Windows:

Disable Fast Startup in Control Panel → Power Options → Choose what the power buttons do.
Shut down fully, or use Restart instead of hybrid shutdown.
Let Windows scan and repair the volume if prompted.
Reconnect the drive.

If you cannot use Windows, keep the volume read-only. Do not force write access.

Step 6: Check for a stale app or extension copy

Two copies of Mountee (or a local build) can confuse extension registration. The bundle identifier is the same, so the stale path can win.

pluginkit -m -i com.github.alvarolorentedev.macntfs.ntfsmodule -vv

If the reported path is not /Applications/MacNTFS.app/Contents/Extensions/NTFSModule.appex, remove the stale copy. Advanced users can re-register:

pluginkit -r <stale-NTFSModule.appex>
pluginkit -a /Applications/MacNTFS.app/Contents/Extensions/NTFSModule.appex
pkill -9 -f NTFSModule.appex
/Applications/MacNTFS.app/Contents/MacOS/MacNTFS --enable-extension

Only remove registrations that point at copies you control. If you are unsure, collect diagnostics first.

Step 7: Check for signature or entitlement problems

The FSKit extension uses restricted entitlements. Ad-hoc or profile-less builds cannot be enabled; macOS kills them (often exit 137 or “Launchd job spawn failed”).

Install the signed and notarized release from GitHub. Do not disable SIP or reduce Startup Security to work around a local build. If you are a developer, use the project’s signed build instructions.

Step 8: Collect diagnostics

Use Copy Diagnostics in the Mountee menu, or:

/Applications/MacNTFS.app/Contents/MacOS/MacNTFS --diagnostics ~/Desktop/mountee-diagnostics.txt

The report includes:

Extension state
fskitd and fskit_agent liveness
Registered FSKit modules
The NTFS mount table
Detected volumes

Review it for sensitive file or volume names before posting it publicly.

Open an issue at github.com/alvarolorentedev/mountee/issues with the macOS version, app version, and the relevant log lines.

When to stop troubleshooting

Stop and prioritize data recovery if:

The drive clicks, beeps, or repeatedly disconnects.
diskutil reports I/O errors.
The volume disappears during a copy.
A repair tool wants to rewrite the partition table.

In those cases, avoid writes. Copy what you can, or contact a data recovery professional. A filesystem driver cannot fix failing hardware.

Prevent the next failure

Eject the volume before unplugging it.
Shut Windows down fully if the drive is shared with a PC.
Disable Fast Startup when switching the drive between systems.
Keep the extension enabled for each user account that needs it.
Update Mountee from the official GitHub release, not a mirror.
Keep backups of important NTFS data.

Frequently asked questions

Why does my NTFS drive mount read-only?
macOS’s built-in driver is read-only. With a third-party driver, a dirty or hibernated volume can also force read-only mode. Check mount and the driver logs.

Does reinstalling fix mounting problems?
Sometimes it fixes a stale extension registration, but it is not the first step. Check the disk, mount state, and dirty-volume status first.

Can Disk Utility repair NTFS?
macOS does not provide general NTFS repair. Use Windows chkdsk or a dedicated tool. Back up first.

Should I disable SIP?
No. Do not disable System Integrity Protection to mount a drive. Mountee does not require it, and doing so weakens your Mac.

How to Fix NTFS Mounting Problems on macOS