<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: DiskBee(NTFS for Mac)</title>
    <description>The latest articles on DEV Community by DiskBee(NTFS for Mac) (@diskbee).</description>
    <link>https://dev.to/diskbee</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4209766%2F6373a34d-dd81-4556-8238-bf5f27e20b81.png</url>
      <title>DEV Community: DiskBee(NTFS for Mac)</title>
      <link>https://dev.to/diskbee</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/diskbee"/>
    <language>en</language>
    <item>
      <title>macOS Won't Write to Your NTFS Drive — Four Ways Around It</title>
      <dc:creator>DiskBee(NTFS for Mac)</dc:creator>
      <pubDate>Mon, 09 Nov 2026 00:36:14 +0000</pubDate>
      <link>https://dev.to/diskbee/macos-wont-write-to-your-ntfs-drive-four-ways-around-it-5d69</link>
      <guid>https://dev.to/diskbee/macos-wont-write-to-your-ntfs-drive-four-ways-around-it-5d69</guid>
      <description>&lt;p&gt;You plug in a Windows-formatted SSD. It shows up in Finder, you drag a file onto it, and nothing happens. Or you get "The volume is read-only."&lt;/p&gt;

&lt;p&gt;Nothing is broken. macOS has read NTFS for years and has never written to it — NTFS belongs to Microsoft, and Apple never took on the job of guaranteeing it. So the drive mounts, you can copy things off it, and writing is blocked on purpose. That has been true in every macOS release so far.&lt;/p&gt;

&lt;p&gt;Before installing anything, answer one question: &lt;strong&gt;is this a one-off transfer, or a drive you use every day?&lt;/strong&gt; Most write-ups skip straight to "install this driver," which is how people end up carrying kernel extensions they did not need.&lt;/p&gt;

&lt;h3&gt;
  
  
  First, check what you are dealing with
&lt;/h3&gt;

&lt;p&gt;Thirty seconds in Terminal:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;mount | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-i&lt;/span&gt; ntfs          &lt;span class="c"&gt;# look for "read-only" in the options&lt;/span&gt;
diskutil info /Volumes/NAME   &lt;span class="c"&gt;# file system, mount mode, writability&lt;/span&gt;
sw_vers                        &lt;span class="c"&gt;# your macOS version&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;code&gt;read-only&lt;/code&gt; in the mount options means you are in the ordinary case, and the rest of this applies. If the volume does not appear at all, or macOS offers to initialise it, stop here — that is usually BitLocker or a damaged partition table, and no driver will help until you sort that out.&lt;/p&gt;

&lt;p&gt;Two more things quietly rule options out:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Your macOS version.&lt;/strong&gt; The user-space route further down only exists from 15.4 onward.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Whether the Mac is managed.&lt;/strong&gt; Run &lt;code&gt;profiles status -type enrollment&lt;/code&gt;. If it is enrolled in MDM, some of these paths are closed by policy no matter what you install.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Option 1 — install nothing
&lt;/h3&gt;

&lt;p&gt;Sometimes you just need a handful of files. Copy them out and you are done; a network share, a cloud folder or a spare exFAT stick covers it with no software at all.&lt;/p&gt;

&lt;p&gt;I put this first because it is the honest answer for a one-off transfer, and because it is the only one that does not sell you anything. The picture changes when the drive is a &lt;strong&gt;working drive&lt;/strong&gt;: you edit on the Mac, the file has to go back, and it happens every day. That is where installing something starts to make sense.&lt;/p&gt;

&lt;h3&gt;
  
  
  Option 2 — reformat to exFAT
&lt;/h3&gt;

&lt;p&gt;exFAT reads and writes on both systems with no extra software. Most forum threads end right there.&lt;/p&gt;

&lt;p&gt;What they tend to leave out: exFAT has no journal. NTFS keeps a transaction log (&lt;code&gt;$LogFile&lt;/code&gt;) and can often recover a volume that was unplugged mid-write, while exFAT has nothing to roll back to — an interrupted write can leave the directory structure damaged. You also lose Windows ACLs, and large folders of small files get noticeably slower.&lt;/p&gt;

&lt;p&gt;On a USB stick you swap files with, that is a fair trade. On a drive holding work you cannot recreate, it isn't.&lt;/p&gt;

&lt;h3&gt;
  
  
  Option 3 — macFUSE + ntfs-3g
&lt;/h3&gt;

&lt;p&gt;The old community answer, and it does work. The source is readable, and the project has taken in something like two decades of odd edge cases. Below macOS 15.4 it is the usual free route; the commercial drivers run on those versions too, if you would rather pay.&lt;/p&gt;

&lt;p&gt;The install is the painful part on Apple silicon. Boot into Recovery Mode, enable &lt;strong&gt;Reduced Security&lt;/strong&gt;, approve the kernel extension in System Settings. That is Apple's deliberate policy for kernel-level code, not an oversight in the process.&lt;/p&gt;

&lt;p&gt;That Recovery Mode step is where a lot of installs stall. On a company-managed Mac, MDM policy may forbid the security downgrade outright, and you will not get past the first step. A major OS upgrade can ask you to approve the extension again before the drive mounts. And the extension sits in the storage path, so a bug in it is a kernel bug — the blast radius is the machine, not one process.&lt;/p&gt;

&lt;p&gt;Reasonable pick if your Mac is below 15.4, or if reading the driver's source matters to you.&lt;/p&gt;

&lt;h3&gt;
  
  
  Option 4 — a user-space file system module (macOS 15.4+)
&lt;/h3&gt;

&lt;p&gt;macOS 15.4 shipped &lt;strong&gt;FSKit&lt;/strong&gt;, Apple's framework for implementing file systems outside the kernel.&lt;/p&gt;

&lt;p&gt;Since none of it runs in kernel space, the install looks like any other app: no Recovery Mode, no Reduced Security, no restart. A crash stays a process-level event, and OS upgrades ride along with the app's own updates instead of triggering another approval round.&lt;/p&gt;

&lt;p&gt;You pay for that in version support and maturity. FSKit starts at 15.4, and nothing built on it has been around as long as ntfs-3g.&lt;/p&gt;

&lt;p&gt;DiskBee (published as NTFSProKit) is one implementation — &lt;a href="https://www.ntfs.pro/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=readonly&amp;amp;utm_content=en" rel="noopener noreferrer"&gt;described on the vendor's site&lt;/a&gt;. I work with the team behind it, so read the next few lines as a description rather than a pitch:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No kernel extension, so it installs on MDM-managed machines that block the security downgrade.&lt;/li&gt;
&lt;li&gt;BitLocker volumes unlock with a password or the 48-digit recovery key, and writes are re-encrypted on the fly so the drive still opens on a Windows PC.&lt;/li&gt;
&lt;li&gt;The free tier is read-only, permanently — browse, copy out, read BitLocker. Writing needs the one-time Pro license (USD 15.00 list price as of 2026-11; regional pricing and any change live on the vendor site).&lt;/li&gt;
&lt;li&gt;Everything runs locally; file names and contents are not collected.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The limits are just as plain. &lt;strong&gt;macOS 15.4 or later, no exceptions&lt;/strong&gt; — on 15.0–15.3 this option does not exist for you, and option 3 is the answer. The free tier will not write, by design, so if writing is the entire point, it does not solve your problem.&lt;/p&gt;

&lt;h3&gt;
  
  
  Picking one
&lt;/h3&gt;

&lt;p&gt;A one-off transfer: copy the files off and skip all of this. A drive whose contents you could lose: exFAT. Below 15.4, or you want to read the source: macFUSE + ntfs-3g. 15.4 and up, an MDM-managed machine, or a BitLocker volume you need to write to: the user-space module.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work with the team that publishes DiskBee. The limitations above are deliberately not softened.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>macos</category>
      <category>filesystem</category>
      <category>ntfs</category>
      <category>applesilicon</category>
    </item>
    <item>
      <title>Your New Mac Arrived, Your Old Drive Went Read-Only: Ten Minutes of Triage First</title>
      <dc:creator>DiskBee(NTFS for Mac)</dc:creator>
      <pubDate>Sun, 08 Nov 2026 12:24:03 +0000</pubDate>
      <link>https://dev.to/diskbee/your-new-mac-arrived-your-old-drive-went-read-only-ten-minutes-of-triage-first-297b</link>
      <guid>https://dev.to/diskbee/your-new-mac-arrived-your-old-drive-went-read-only-ten-minutes-of-triage-first-297b</guid>
      <description>&lt;p&gt;A machine ordered in August turns up in November, you plug in the drive you have used for two years, and every write is refused. The drive is fine. The old Mac still writes to it.&lt;/p&gt;

&lt;p&gt;This is the most common shape of the question right now, because a batch of new Macs started arriving on 6 November and most of them ship with macOS 27, which has been out since 14 September. So before anyone installs a driver, it is worth ten minutes establishing &lt;em&gt;which&lt;/em&gt; problem you actually have. Four of the five checks below have nothing to do with drivers at all.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Confirm the volume is actually NTFS
&lt;/h3&gt;

&lt;p&gt;Disk Utility will tell you, or one command will:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;diskutil info /Volumes/YOUR_DISK | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="s2"&gt;"File System Personality"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If it says &lt;code&gt;ExFAT&lt;/code&gt; or &lt;code&gt;MS-DOS FAT32&lt;/code&gt;, you are already writable — macOS supports both natively — and the read-only state is coming from somewhere else. If it says &lt;code&gt;NTFS&lt;/code&gt;, continue.&lt;/p&gt;

&lt;p&gt;Do not substitute the partition type for this. &lt;code&gt;diskutil info&lt;/code&gt; reports both, and they can disagree: a drive can carry a partition entry labelled &lt;code&gt;Windows_NTFS&lt;/code&gt; while the volume on it was reformatted to something else years ago. &lt;code&gt;File System Personality&lt;/code&gt; is the one that describes the volume you are actually trying to write to.&lt;/p&gt;

&lt;p&gt;This check matters more than it sounds. A large share of "my Mac cannot write to this drive" reports are drives that were reformatted years ago, and the fix is not a driver but finding the real cause: a full volume, a permissions problem, or a filesystem that failed to mount cleanly.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Check whether the volume is BitLocker-encrypted
&lt;/h3&gt;

&lt;p&gt;A BitLocker volume does not mount read-only on macOS — it does not mount at all, and Disk Utility may describe it as unreadable or uninitialised. That distinction is the fastest way to tell the two problems apart:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;mounts, but rejects writes → filesystem-level&lt;/li&gt;
&lt;li&gt;does not mount, unknown format → encryption-level&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Treat these as two separate requirements. A file-system driver has nothing to say about a volume that is encrypted underneath it, and buying or installing the wrong one wastes an evening.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Check the boring causes
&lt;/h3&gt;

&lt;p&gt;Three minutes, in order:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Physical write protection&lt;/strong&gt; — SD cards and some USB enclosures have a lock switch or a read-only bridge chip. If the same drive writes fine on Windows, skip this.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dirty volume&lt;/strong&gt; — macOS may mount a volume read-only when it wants a consistency check first. Two ways to see it, cheapest first:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;diskutil info /Volumes/YOUR_DISK | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-i&lt;/span&gt; &lt;span class="s2"&gt;"Read-Only"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That returns two booleans, and they mean different things: &lt;code&gt;Media Read-Only: Yes&lt;/code&gt; is protection at the hardware or enclosure level, while &lt;code&gt;Volume Read-Only: Yes&lt;/code&gt; is the filesystem layer refusing writes. Alternatively, &lt;code&gt;mount | grep -i ntfs&lt;/code&gt; lists &lt;code&gt;read-only&lt;/code&gt; among the options in the parentheses — it is one flag inside a list, not a separate field, so do not go looking for a line that starts with it.&lt;/p&gt;

&lt;p&gt;Running First Aid, or letting Windows finish its check, often restores write access without any third-party software.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free space and ownership&lt;/strong&gt; — a volume with 0 bytes available or with ownership enabled for another user will refuse writes for reasons that look identical from Finder.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If all three come back clean and the volume really is NTFS, you have the driver question — and only then.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Understand what "the driver" actually is now
&lt;/h3&gt;

&lt;p&gt;There is no way to add a filesystem to macOS without putting code between the VFS layer and the storage device. Historically that code was a kernel extension: loaded into the kernel, running with kernel privileges. On Apple Silicon, installing one requires changing the machine's startup security policy to Reduced Security, and that change involves a restart — Apple's own documentation is explicit about both points, and Apple now describes kernel extensions as no longer recommended for macOS.&lt;/p&gt;

&lt;p&gt;macOS 15.4 introduced the alternative: &lt;strong&gt;FSKit&lt;/strong&gt;, described by Apple as a way to implement a file system that runs in user space. A driver built this way is delivered as an app extension, runs outside the kernel, and does not require lowering the startup security policy or rebooting to install.&lt;/p&gt;

&lt;p&gt;That is the whole structural difference, and it explains why the question "does it need reduced security?" is more useful than "is it fast?" when you are comparing options.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Answer two questions, and the shortlist collapses
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Do you need write access, or is copying files out enough?&lt;/strong&gt; If reading is enough, you need nothing today — the volume already mounts, and &lt;code&gt;rsync -av&lt;/code&gt; or a Finder copy will get the data off. Two weeks of "deciding" is cheaper than one bad installation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Are these machines managed?&lt;/strong&gt; If the Mac is enrolled in MDM, the startup security policy is typically set by the organisation. A policy pinned to full security — a common and defensible default — makes the kernel-extension route unavailable no matter how willing you are. On a user-space driver this question does not arise.&lt;/p&gt;

&lt;h3&gt;
  
  
  What the new hardware does &lt;em&gt;not&lt;/em&gt; change
&lt;/h3&gt;

&lt;p&gt;A new chip generation does not change the driver model. FSKit, kernel extensions, startup security policy and the read-only default are all properties of macOS, not of the SoC. The machine that arrived this week runs the same driver stack as the one it replaced, which is why the same answer works — and why "it worked on my old Mac" is not evidence that anything changed on the new one.&lt;/p&gt;

&lt;p&gt;The one thing that did change is the OS version the machine ships with, and therefore which driver routes exist for it at all: the user-space route requires 15.4 or later, so it is available here, while a mixed fleet still needs a plan for older machines.&lt;/p&gt;

&lt;h3&gt;
  
  
  What I would avoid in week one
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Do not reformat before you know whose data is on the drive.&lt;/strong&gt; Reformatting solves the problem permanently and irreversibly; it is a decision about the data, not about the Mac.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do not change the startup security policy on a managed machine.&lt;/strong&gt; It is a machine-wide setting, and on a corporate Mac it may not be yours to change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do not paste a script from a forum thread.&lt;/strong&gt; Nothing in the checks above requires one.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you end up in the driver branch and want a concrete example of what the user-space route looks like in practice, including its stated minimum version, &lt;a href="https://www.ntfs.pro/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=m6-first-week&amp;amp;utm_content=en-6" rel="noopener noreferrer"&gt;the vendor's stated system requirements&lt;/a&gt; is one place to check — and the same check is worth running on any other product before you install it.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work with the team that publishes DiskBee. The checks above are ordered so that the free options come first.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>drivers</category>
      <category>hardware</category>
    </item>
    <item>
      <title>Your New Mac Arrived, Your Old Drive Went Read-Only: Ten Minutes of Triage First</title>
      <dc:creator>DiskBee(NTFS for Mac)</dc:creator>
      <pubDate>Sun, 08 Nov 2026 10:57:14 +0000</pubDate>
      <link>https://dev.to/diskbee/your-new-mac-arrived-your-old-drive-went-read-only-ten-minutes-of-triage-first-4o15</link>
      <guid>https://dev.to/diskbee/your-new-mac-arrived-your-old-drive-went-read-only-ten-minutes-of-triage-first-4o15</guid>
      <description>&lt;p&gt;A machine ordered in August turns up in November, you plug in the drive you have used for two years, and every write is refused. The drive is fine. The old Mac still writes to it.&lt;/p&gt;

&lt;p&gt;This is the most common shape of the question right now, because a batch of new Macs started arriving on 6 November and most of them ship with macOS 27, which has been out since 14 September. So before anyone installs a driver, it is worth ten minutes establishing &lt;em&gt;which&lt;/em&gt; problem you actually have. Four of the five checks below have nothing to do with drivers at all.&lt;/p&gt;

&lt;h3&gt;
  
  
  1. Confirm the volume is actually NTFS
&lt;/h3&gt;

&lt;p&gt;Disk Utility will tell you, or one command will:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;diskutil info /Volumes/YOUR_DISK | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="s2"&gt;"File System Personality"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;If it says &lt;code&gt;ExFAT&lt;/code&gt; or &lt;code&gt;MS-DOS FAT32&lt;/code&gt;, you are already writable — macOS supports both natively — and the read-only state is coming from somewhere else. If it says &lt;code&gt;NTFS&lt;/code&gt;, continue.&lt;/p&gt;

&lt;p&gt;Do not substitute the partition type for this. &lt;code&gt;diskutil info&lt;/code&gt; reports both, and they can disagree: a drive can carry a partition entry labelled &lt;code&gt;Windows_NTFS&lt;/code&gt; while the volume on it was reformatted to something else years ago. &lt;code&gt;File System Personality&lt;/code&gt; is the one that describes the volume you are actually trying to write to.&lt;/p&gt;

&lt;p&gt;This check matters more than it sounds. A large share of "my Mac cannot write to this drive" reports are drives that were reformatted years ago, and the fix is not a driver but finding the real cause: a full volume, a permissions problem, or a filesystem that failed to mount cleanly.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Check whether the volume is BitLocker-encrypted
&lt;/h3&gt;

&lt;p&gt;A BitLocker volume does not mount read-only on macOS — it does not mount at all, and Disk Utility may describe it as unreadable or uninitialised. That distinction is the fastest way to tell the two problems apart:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;mounts, but rejects writes → filesystem-level&lt;/li&gt;
&lt;li&gt;does not mount, unknown format → encryption-level&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Treat these as two separate requirements. A file-system driver has nothing to say about a volume that is encrypted underneath it, and buying or installing the wrong one wastes an evening.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Check the boring causes
&lt;/h3&gt;

&lt;p&gt;Three minutes, in order:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Physical write protection&lt;/strong&gt; — SD cards and some USB enclosures have a lock switch or a read-only bridge chip. If the same drive writes fine on Windows, skip this.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Dirty volume&lt;/strong&gt; — macOS may mount a volume read-only when it wants a consistency check first. Two ways to see it, cheapest first:
&lt;/li&gt;
&lt;/ul&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;diskutil info /Volumes/YOUR_DISK | &lt;span class="nb"&gt;grep&lt;/span&gt; &lt;span class="nt"&gt;-i&lt;/span&gt; &lt;span class="s2"&gt;"Read-Only"&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;That returns two booleans, and they mean different things: &lt;code&gt;Media Read-Only: Yes&lt;/code&gt; is protection at the hardware or enclosure level, while &lt;code&gt;Volume Read-Only: Yes&lt;/code&gt; is the filesystem layer refusing writes. Alternatively, &lt;code&gt;mount | grep -i ntfs&lt;/code&gt; lists &lt;code&gt;read-only&lt;/code&gt; among the options in the parentheses — it is one flag inside a list, not a separate field, so do not go looking for a line that starts with it.&lt;/p&gt;

&lt;p&gt;Running First Aid, or letting Windows finish its check, often restores write access without any third-party software.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Free space and ownership&lt;/strong&gt; — a volume with 0 bytes available or with ownership enabled for another user will refuse writes for reasons that look identical from Finder.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If all three come back clean and the volume really is NTFS, you have the driver question — and only then.&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Understand what "the driver" actually is now
&lt;/h3&gt;

&lt;p&gt;There is no way to add a filesystem to macOS without putting code between the VFS layer and the storage device. Historically that code was a kernel extension: loaded into the kernel, running with kernel privileges. On Apple Silicon, installing one requires changing the machine's startup security policy to Reduced Security, and that change involves a restart — Apple's own documentation is explicit about both points, and Apple now describes kernel extensions as no longer recommended for macOS.&lt;/p&gt;

&lt;p&gt;macOS 15.4 introduced the alternative: &lt;strong&gt;FSKit&lt;/strong&gt;, described by Apple as a way to implement a file system that runs in user space. A driver built this way is delivered as an app extension, runs outside the kernel, and does not require lowering the startup security policy or rebooting to install.&lt;/p&gt;

&lt;p&gt;That is the whole structural difference, and it explains why the question "does it need reduced security?" is more useful than "is it fast?" when you are comparing options.&lt;/p&gt;

&lt;h3&gt;
  
  
  5. Answer two questions, and the shortlist collapses
&lt;/h3&gt;

&lt;p&gt;&lt;strong&gt;Do you need write access, or is copying files out enough?&lt;/strong&gt; If reading is enough, you need nothing today — the volume already mounts, and &lt;code&gt;rsync -av&lt;/code&gt; or a Finder copy will get the data off. Two weeks of "deciding" is cheaper than one bad installation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Are these machines managed?&lt;/strong&gt; If the Mac is enrolled in MDM, the startup security policy is typically set by the organisation. A policy pinned to full security — a common and defensible default — makes the kernel-extension route unavailable no matter how willing you are. On a user-space driver this question does not arise.&lt;/p&gt;

&lt;h3&gt;
  
  
  What the new hardware does &lt;em&gt;not&lt;/em&gt; change
&lt;/h3&gt;

&lt;p&gt;A new chip generation does not change the driver model. FSKit, kernel extensions, startup security policy and the read-only default are all properties of macOS, not of the SoC. The machine that arrived this week runs the same driver stack as the one it replaced, which is why the same answer works — and why "it worked on my old Mac" is not evidence that anything changed on the new one.&lt;/p&gt;

&lt;p&gt;The one thing that did change is the OS version the machine ships with, and therefore which driver routes exist for it at all: the user-space route requires 15.4 or later, so it is available here, while a mixed fleet still needs a plan for older machines.&lt;/p&gt;

&lt;h3&gt;
  
  
  What I would avoid in week one
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Do not reformat before you know whose data is on the drive.&lt;/strong&gt; Reformatting solves the problem permanently and irreversibly; it is a decision about the data, not about the Mac.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do not change the startup security policy on a managed machine.&lt;/strong&gt; It is a machine-wide setting, and on a corporate Mac it may not be yours to change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Do not paste a script from a forum thread.&lt;/strong&gt; Nothing in the checks above requires one.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;If you end up in the driver branch and want a concrete example of what the user-space route looks like in practice, including its stated minimum version, &lt;a href="https://www.ntfs.pro/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=m6-first-week&amp;amp;utm_content=en-6" rel="noopener noreferrer"&gt;the vendor's stated system requirements&lt;/a&gt; is one place to check — and the same check is worth running on any other product before you install it.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work with the team that publishes DiskBee. The checks above are ordered so that the free options come first.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>macos</category>
      <category>ntfs</category>
      <category>applesilicon</category>
      <category>filesystem</category>
    </item>
    <item>
      <title>NTFS on Apple Silicon: The Kernel-Extension Era Is Quietly Ending</title>
      <dc:creator>DiskBee(NTFS for Mac)</dc:creator>
      <pubDate>Tue, 27 Oct 2026 02:32:32 +0000</pubDate>
      <link>https://dev.to/diskbee/ntfs-on-apple-silicon-the-kernel-extension-era-is-quietly-ending-2pk5</link>
      <guid>https://dev.to/diskbee/ntfs-on-apple-silicon-the-kernel-extension-era-is-quietly-ending-2pk5</guid>
      <description>&lt;p&gt;For about fifteen years, writing to an NTFS volume on a Mac has meant one of two things: buy a commercial driver, or install macFUSE and ntfs-3g and accept the consequences. Both approaches share a structural assumption that no longer holds cleanly on Apple Silicon — that a third party is allowed to drop a kernel extension into the storage stack.&lt;/p&gt;

&lt;p&gt;This post is about why that assumption is fraying, and what replaced it.&lt;/p&gt;

&lt;h4&gt;
  
  
  1. What the kext route actually costs
&lt;/h4&gt;

&lt;p&gt;macFUSE ships a kernel extension. On modern macOS, loading it requires booting into Recovery Mode, enabling "Reduced Security," and approving the extension in System Settings. That is not a bug or an oversight — it is the platform's stated position on kernel-level code, and it is reasonable. But the practical consequences are real:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Any machine under MDM policy may forbid the security downgrade outright.&lt;/li&gt;
&lt;li&gt;The approval survives reboots, but not always major OS upgrades.&lt;/li&gt;
&lt;li&gt;Once a kernel extension is in the storage path, a bug in it is a bug in the kernel. A panic takes the whole machine with it, not one process.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this makes macFUSE wrong. Its source is public and auditable, and ntfs-3g is a genuinely impressive piece of software maintained by people who deserve better funding. It is simply a 2000s-era architecture being run in a 2020s security model.&lt;/p&gt;

&lt;h4&gt;
  
  
  2. What FSKit changes
&lt;/h4&gt;

&lt;p&gt;macOS 15.4 introduced FSKit: a user-space framework for implementing file systems. The important property is where the code runs — in user space, as an ordinary app-adjacent module, not in the kernel.&lt;/p&gt;

&lt;p&gt;The tradeoffs invert:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;&lt;/th&gt;
&lt;th&gt;Kernel extension (macFUSE + ntfs-3g)&lt;/th&gt;
&lt;th&gt;User-space module (FSKit)&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;Install&lt;/td&gt;
&lt;td&gt;Recovery Mode, Reduced Security, approval&lt;/td&gt;
&lt;td&gt;Normal app install&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Failure blast radius&lt;/td&gt;
&lt;td&gt;Kernel panic possible&lt;/td&gt;
&lt;td&gt;Process-level&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;OS upgrade survival&lt;/td&gt;
&lt;td&gt;Requires re-approval sometimes&lt;/td&gt;
&lt;td&gt;Follows app updates&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Works on&lt;/td&gt;
&lt;td&gt;Wide range of macOS versions&lt;/td&gt;
&lt;td&gt;macOS 15.4+ only&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;Maturity&lt;/td&gt;
&lt;td&gt;~20 years of edge cases&lt;/td&gt;
&lt;td&gt;Young API surface&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;That last row matters, and I will come back to it.&lt;/p&gt;

&lt;h4&gt;
  
  
  3. Why the storage layer is a bad place for a bug
&lt;/h4&gt;

&lt;p&gt;NTFS is not a simple format. A dirty volume — one that was unplugged mid-write, or left behind by a crashed Windows box — carries a transaction log that must be replayed before the volume is safe to touch. Writing to a volume before its transaction log has been replayed is a risk taken on the user’s behalf — which is why log replay at mount is the first thing to look for in a driver’s design notes.&lt;/p&gt;

&lt;p&gt;The more defensible designs do three things: replay the log at mount, run structural checks (MFT records, cluster allocation, directory indexes) rather than trusting the header, and refuse to guess when damage is deep — handing the volume back to &lt;code&gt;chkdsk&lt;/code&gt; on a Windows machine, which is the only tool with full knowledge of the format's repair semantics.&lt;/p&gt;

&lt;p&gt;That last point is worth checking on any tool you evaluate: does it hand deeply damaged volumes to chkdsk on a Windows machine, or does it attempt a "repair" of its own on an MFT record it only partly understands? The answer is usually in the vendor’s documentation rather than the marketing page — and it is a question about design, not about who has the better product.&lt;/p&gt;

&lt;h4&gt;
  
  
  4. One concrete FSKit implementation
&lt;/h4&gt;

&lt;p&gt;&lt;a href="https://www.ntfs.pro/en?utm_source=devto&amp;amp;utm_medium=article&amp;amp;utm_campaign=applesilicon&amp;amp;utm_content=en" rel="noopener noreferrer"&gt;DiskBee&lt;/a&gt; (published as NTFSProKit) is an FSKit-based NTFS read-write driver. I have a working relationship with the team, so treat the following as a description rather than an endorsement.&lt;/p&gt;

&lt;p&gt;What is architecturally interesting:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No kernel extension, therefore no Recovery Mode, no Reduced Security, no restart — the install path that MDM administrators can actually approve.&lt;/li&gt;
&lt;li&gt;BitLocker support: password or recovery key, with write operations re-encrypted in real time so the volume stays valid when it goes back to Windows.&lt;/li&gt;
&lt;li&gt;Formatting to NTFS through the system's own disk utility path (diskutil).&lt;/li&gt;
&lt;li&gt;A speed test that measures through the NTFS engine itself rather than through the raw block device — closer to what you actually see when copying files.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;What is not: it requires macOS 15.4 or later, full stop. On a 15.2 machine this entire approach is unavailable and macFUSE remains the answer. The Free tier is read-only by design (browse, copy out, BitLocker read) — writing requires the one-time Pro license. And the FSKit API is young; a twenty-year-old ntfs-3g has seen edge cases that a 2025-era implementation has not.&lt;/p&gt;

&lt;h4&gt;
  
  
  5. How to choose
&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Corporate Mac, MDM-managed, security posture matters&lt;/strong&gt; → user-space, if the OS is new enough.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;macOS 15.0–15.3, or you want to read the driver's source&lt;/strong&gt; → macFUSE + ntfs-3g.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;One-off transfer, small files&lt;/strong&gt; → copy to exFAT or over the network; do not install anything.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;BitLocker volumes&lt;/strong&gt; → check explicitly that your tool supports write with re-encryption, not just read.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The structural point stands regardless of vendor: the kernel is no longer where this problem gets solved on macOS, and a 2026 comparison that ignores FSKit is missing the biggest structural change.&lt;/p&gt;

&lt;p&gt;Updated 2026-11: removed a statement about Apple's own file systems that I could not source, and reworded one passage that could be read as a claim about how other tools behave. No other changes.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Disclosure: I work with the team that publishes DiskBee. I have kept the limitations section as blunt as the feature list.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>macos</category>
      <category>filesystem</category>
      <category>apple</category>
      <category>tooling</category>
    </item>
  </channel>
</rss>
