OWC MacDrive 12 [WiN]

• Product: MacDrive 12
• Developer: OWC
• Version: 12.0.0
• Requirements: Windows 10 or later
• Source: owc.com/solutions/macdrive

MacDrive 12 is a Windows file system driver that mounts HFS+, APFS, encrypted APFS, SoftRAID, and Apple RAID volumes directly in Windows Explorer with full read and write access. It installs as a background service requiring no application launch — Mac drives appear automatically on connection exactly as NTFS drives do. The v12 release adds native encrypted APFS support, which prior versions and all competing tools either omit entirely or handle through decryption-first workarounds that temporarily remove encryption protections. APFS Crash Protection preserves completed writes and discards interrupted writes during power failures or system crashes to prevent partition corruption. Disk repair is available for HFS+ volumes only. It answers the query: how do I read and write Mac-formatted drives on a Windows PC without reformatting, converting, or moving files through a cloud service.

Key Takeaway

Windows machines that regularly receive Mac-formatted portable drives — video editing stations pulling footage from a Mac shooter’s SSD, IT administrators troubleshooting mixed-platform environments, data recovery specialists accessing encrypted client volumes — are the operational context where MacDrive 12 removes a step that currently requires a workaround. The driver installs once and becomes invisible; no application opens, no conversion runs, no cloud transfer queues. Disk repair only covers HFS+ formatted volumes — APFS disks that develop corruption require a Mac or a dedicated recovery tool for repair operations. Windows users who primarily receive exFAT-formatted removable drives from Mac colleagues, and whose Mac collaborators have already accepted the exFAT tradeoff, don’t have a cross-platform problem MacDrive 12 solves.

Encrypted APFS: Native Driver vs. Decryption Workarounds

Every modern Mac defaults to APFS with FileVault encryption enabled. Before MacDrive 12, Windows tools that claimed APFS support fell into two categories: solutions that mounted unencrypted APFS volumes only, and solutions that required the user to decrypt the volume first — either removing encryption entirely or mounting a temporary decrypted copy — before Windows could read it. Decrypting first creates a window during which protected data exists in an unencrypted state on the drive or in memory, which is a real exposure for legal, medical, and production environments where data protection is a compliance requirement. MacDrive 12 implements the APFS encryption layer directly in the driver, accepting the volume password at mount time and maintaining encryption throughout the session. Files open, save, and copy between the encrypted volume and the Windows file system without any intermediate unencrypted state on disk. The encrypted volume remains encrypted on the physical drive at all times — the driver handles the decryption in memory during active access, the same way macOS does natively.

APFS Crash Protection and the Mid-Write Failure Problem

APFS uses a copy-on-write transaction model on macOS: data is written to a new location before the old data is released, and a pointer update completes the transaction atomically. If power fails between the write and the pointer update on a driver that doesn’t implement this correctly, the file system ends up with a committed pointer pointing at partially written or absent data — corruption that requires recovery tools to address. MacDrive 12 implements the APFS copy-on-write transaction model in the Windows driver, meaning that when a write is interrupted by a power failure or system crash, the committed data at the old pointer remains intact and the incomplete write is discarded cleanly. No file corruption occurs from the incomplete transaction; the drive mounts on the next connection exactly as it left off before the failure. This protection operates continuously during any write to an APFS volume — it is not a mode to enable or a setting to configure. The protection applies to APFS and encrypted APFS volumes; it does not apply to HFS+ volumes, which use a different journaling model.

Disk Management Without a Mac in the Room

MacDrive 12 exposes create, partition, format, and repair functions for Mac-formatted disks directly from Windows, covering the management tasks that previously required access to a Mac running Disk Utility. Creating a new APFS or HFS+ volume, repartitioning a drive, and reformatting a disk from NTFS to APFS all run from Windows without connecting the drive to a Mac first. This matters in post-production environments where a Windows-based facility receives drives formatted for a Mac-based production and needs to prep blank drives for return without maintaining a Mac workstation solely for that purpose. The repair function is limited to HFS+ volumes — APFS disk repair is not available through MacDrive 12, which means a corrupted APFS volume discovered during a Windows session cannot be repaired in place. HFS+ repair covers the journaled Mac OS Extended format used on older drives and Time Machine backup volumes, which remains common in archival and backup contexts. Repair operations on HFS+ through MacDrive 12 cover the same structural checks that macOS Disk Utility’s First Aid function runs on that format.

Time Machine Backup Access from Windows

Time Machine backups stored on HFS+ or APFS formatted volumes mount with full read access through MacDrive 12, allowing individual files and folders to be browsed and restored to the Windows file system without opening a Mac. The Time Machine directory structure is accessible as a standard folder hierarchy in Windows Explorer — backup snapshots appear as dated folders, and files within them can be copied out directly. This access path matters specifically when a Mac user needs to retrieve a file from a Time Machine backup while working at a Windows machine, or when a Mac is unavailable and the backup drive is the only copy of a needed file. MacDrive 12 v12 adds FSEvents support for changes made in Windows on APFS and HFS+ volumes, meaning files modified or created from Windows are now correctly indexed and backed up by Time Machine on the Mac side — a gap that prior versions left open where Windows-side edits could be invisible to Time Machine’s change tracking. Restoring from Time Machine through MacDrive 12 copies individual files and folders; full system restore to a Mac requires macOS Recovery and is not available through the Windows driver.

Where MacDrive 12 Ends

Disk repair works only on HFS+ volumes. A corrupted APFS volume — including an encrypted APFS volume that encounters file system errors — cannot be repaired through MacDrive 12 and requires either macOS Disk Utility, macOS Terminal’s fsck_apfs, or a third-party APFS recovery tool running on a Mac. MacDrive 12 runs on Windows only; there is no macOS component, no Linux support, and no mobile access path. The driver handles the five Mac formats listed — HFS+, APFS, encrypted APFS, SoftRAID, Apple RAID — and does not extend to less common Mac formats such as Mac OS Standard (HFS without journaling) used on very old volumes. Windows Server environments support SoftRAID virtual disks, but they load in offline mode by default and require manual mounting. Users managing an environment where Mac drives arrive formatted in multiple generations of Apple file systems — including pre-HFS+ legacy formats — will encounter volumes MacDrive 12 does not mount. The driver installs at the kernel level on Windows; compatibility testing against specific Windows builds and enterprise security configurations before deployment in managed IT environments is advisable.

FAQs