As per title, I'm using a external NTFS hard disk for storage (guess it doesn't matter the type, but I can give more informations if needed). It happen many times, however, that I receive Finder error -50 > The operation could not be completed.
An unexpected error occurred (error code -50). when trying to remove files (it also happen when move files from the external hd to the local one, dragging and dropping with cmd pressed).
I read on the web that it may be related to illegal characters in files' names, however it seems to happen also for files that have nothing "strange" in the name (i.e. asdf.txt). Besides, when the popup appears, the file gets deleted even if I cancel the operation. I'm using MacOS 10.7.4 and Paragon NTFS 9.0.1 for enabling NTFS read/write. Any idea of what may be the error?

I have a SSD formated in Mac OS Extended, and I want to format it to NTFS because I will use it on Windows. To do it, I installed Paragon. I rebooted my MacBook. I checked if the driver was actived, and it was. So I went to Disk Utilty, but I have no choice to format to NTFS. Only Mac OS Extended is proposed. I tried with Tuxera too. But same result, it didn't show the NTFS option. Do you know any other way to format a SSD or a HDD from Mac OS Extended to NTFS ?

I am trying to copy data from an external NTFS drive to an exFAT drive. However, some files are greyed out and give me this error when I try to copy them: > One or more items in “IMGP0029.AVI” can’t be changed because they are in use. Even after clicking Continue and typing my password, it doesn't copy. Following this answer I tried to run SetFile -c "" -t "" path/to/file.mov but I get: > ERROR: Write Permissions Error. (-61) on file: /Volumes/Seagate Backup Plus Drive/IMGP0029.AVI Running sudo chmod 777 gives me: > chmod: Unable to change file mode on /Volumes/Seagate Backup Plus Drive/IMGP0029.AVI: Read-only file system Where do I go from here?

etc/fstab: /dev/disk4s1 /Volumes/HDD /usr/local/bin/ntfs-3g local,allow_other,auto_xattr 0 0 sudo mount -a: ntfs-3g % sudo mount -a mount_apfs: volume could not be mounted: Permission denied mount: / failed with 66 but if I manually in terminal run sudo ntfs-3g /dev/disk4s1 /Volumes/HDD -o local -o allow_other -o auto_xattr then it mounts the disk without any issues. not sure why does it tries to use apfs

Is there any disk encryption scheme or format that can be used on both macos _and_ linux? Linux cannot read Apple's drive encryption format, and LUKS is not supported on MacOS. I tried using VeraCrypt encrypted partitions in exFat format and it mounted successfully several times on MacOS but after a system update exFat mounting of veracrypt volumes does not work anymore (no issues on linux). Also, exFat does not seem to be a reliable file system, so I searched for alternatives, but apart from **fat32**, **exFat** and **ntfs** I don't see any viable alternatives for a reliable cross-platform file system. All of these formats have issues: **fat32** has file size limits, **exfat** veracrypt partitions are not mountable on macos, and **ntfs** is proprietary, linux support is not reliable, and veracrypt does not support it on linux/mac. hfsplus works fine on mac but is read-only on linux (probably worth mentioning that you can disable HFS+ journalling and allow writing on linux). I hoped to be able to use ext3/ext4 with veracrypt encryption but even though I have fuse with ext4fuse working in read-only mode working for unencrypted drives veracrypt is apparently not able to interoperate with fuse drivers. Fat32 would be a great option since it works well with veracrypt on any OS, but the file size limitation and lack of symlinks is simply not acceptable. Any other options I might have missed?

One of my external hard disks is a 8 TB "Seagate Backup Plus". It is formatted with NTFS and came with a driver program and utility (named "NTFS for Mac"). This worked well until I updated my Mac from MacOS 11 to MacOS 15. Now when I try to mount the drive, it says "failed to mount". The drive is also not visible at all in DiskUtility, but is visible from the "NTFS for Mac" utility. The error report says Process: FSApp Path: /Applications/NTFS for Mac.app/Contents/MacOS/FSApp Identifier: com.paragon-software.ntfs.fsapp Version: 15.5.90 (15.5.90) Code Type: X86-64 (Native) Parent Process: launchd User ID: 501 Date/Time: 2025-01-08 09:12:29.6518 +0100 OS Version: macOS 15.1.1 (24B91) Report Version: 12 .... Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_GUARD (SIGKILL) Exception Codes: GUARD_TYPE_MACH_PORT Exception Codes: 0x00000000000003ea, 0x0000000000000000 Termination Reason: Namespace GUARD, Code 2305843022098596842 What could be the problem? What could I do to get the drive mounted?

What is the best, easiest, preferably cheapest way to make OS X write to NTFS-formatted drives in Mac OS X?

I have 7800 Photos on my photos of mac-book air, i need to transfer all the 7800 photos to a external harddisk. I created a separate folder with all the 7800 photos on the desktop now when i try to drag and drop the folder on the harddisk location it pulls back the folder to its original place. The hard disk has enough storage to accomodate the photos i am trying to transfer and the Format of the harddisk is Windows NT File System(NTFS). Please suggest

I use several NTFS external disks with my Catalina Mac (for PC file exchanges). None of them are Spotlight-indexed, and that's fine as it is not necessary: macOS has no trouble seaching the disks without Spotlight. All of a sudden one of the external disks stopped being searchable. macOS is unable to find any files. On my other external NTFS disks there is no problem with the macOS search function. (and Spotlight is not enabled there either) (Rebuilding the Spotlight index is N/A as Spotlight is not used.) I have the feeling something in my macOS is messed up regarding that particular external drive. Pehaps a setting that got corrupted? Is there such a thing as a .plist or so for a drive that can be deleted and recreated? What could be the cause of the basic search function not working on an external USB drive?

My Seagate external NTFS drive used to work with my Macbook (Intel chip still) when it was down at MacOS 10 and 12. Now that I've updated to Sonoma (14.5.1), I can see it via Disk Utility but not from Finder. Basically I have a paperweight and I can't even read from the drive but what I want to do is read AND write. It seems like the Paragon driver I have that manages NTFS is too old (15.8.108) and I stumbled upon the Internet somewhere that said I needed 15.11.xxx. However, when I go to the Paragon website, it seems like we need to pay for the driver now. Even the Seagate website only goes up to 15.8.108. So my question is 2 fold: 1. Is it true that with Sonoma, I need the newer driver version? 2. Since I'm spoiled with free, what free driver is out there that supports external drivers that are running NTFS? I can't believe Seagate would leave us hanging like this with a paperweight and no support, forcing me to buy a Windows laptop to be able to view/use the contents of my drive that had been in use all these years.

I am wondering what the most reliable method is to copy a large amount (1TB) of photos from a Mac computer (external HFS+ drive) to a Windows computer (external NTFS drive)? I am hoping to do this over a local network. But I am wondering how to make this as reliable as possible. I see two possible network strategies but am not sure which is a better bet: (a) Mac shares the source drive (HFS+), Windows mounts it, Windows does the copying. (b) Windows shares the destination drive, Mac mounts it, Mac does the copying. Thank you for any advice! *PS, alternatives I have already considered but am hoping to avoid:* 1. *I have in the past done HFS->NTFS by going via an intermediate exFAT copy. But there are many reasons this strategy is painful and I am not even sure it is that reliable. So I am trying to find a network strategy.* 2. *I also know that in theory Mac can mount and write to NTFS using special drivers (i.e. Paragon) but I have always had the impression this is risky in terms of the risk of corrupting the destination drive.*

I noticed that whenever I add files and delete them, their physical space remains on the disk drive. I uninstalled NTFS Tuxera and I still have the same problem. So I had to insert the disk under my other Windows laptop to locate the ./#### files and delete them. I was surprised that I couldn't locate those files in Finder, but windows allowed me to view them. Is there a way to have more control over what files are viewed in Finder? Platform: retina MacBook Pro, Mountain Lion (OS X 10.8)

There are several apps (Wine wrappers) which can help executing windows executables on macOS. This is similar to what a VM does. As we know, we can use a VM to mount, read, and format NTFS drives. Can we do the same thing with Wine or a similar app? After all, wine contains the important components of the Windows OS. Edit: It seems some has the view that we should simply consider other ways to use NTFS on mac instead of looking into this approach. This is absurd: what's wrong with doing things in a different way with significant advantage (e.g. less RAM consumption than VM, and also advantage over many other methods)?

I have accidentally deleted some files on my Mac OS X Mavericks. Actually, I was trying to burn an .img file to my flash drive which was located at **/dev/disk1** (at the same time I had connected a NTFS External Hard disk to my Mac). So I used **dd command** to flash these files and don't know how, but the flash drive was now located at **/dev/disk2** and at **disk1** the hard disk was mounted. So I accidentally flashed that .img file to my hard disk and lost around 100gb of data. Now I scanned my hard disk with Disk Drill v1 Enterprise and found some lost partitions (there are around 5 partitions around 10mb each). When I deep scan the hard disk with Disk Drill, It displays all the files but with lost file name and directory structure. But I badly need that. So guys please help me to recover these files properly based on its file structure (Like Recuva do in Windows). Also recommend me some kind of utility (free preferred) that can recover my files while keeping original directory structure.

I have an iMac running El Capitan, and an external disk formatted NTFS that will not mount on the mac. It will mount perfectly in Windows and Ubuntu. I'm not trying to write to it, right now I just want to read. Here's my output of "diskutil mount disk3s1": Volume on disk3s1 failed to mount If the volume is damaged, try the "readOnly" option Output of info: Device Identifier: disk3s1 Device Node: /dev/disk3s1 Whole: No Part of Whole: disk3 Device / Media Name: Untitled 1 Volume Name: Mounted: No File System Personality: NTFS Type (Bundle): ntfs Name (User Visible): Windows NT File System (NTFS) Partition Type: Windows_NTFS OS Can Be Installed: No Media Type: Generic Protocol: USB SMART Status: Not Supported Volume UUID: E6F4FA18-C794-465E-82A1-91A8F45C4262 Total Size: 320.0 GB (319965626368 Bytes) (exactly 624932864 512-Byte-Units) Volume Free Space: 0 B (0 Bytes) (exactly 0 512-Byte-Units) Device Block Size: 512 Bytes Read-Only Media: No Read-Only Volume: Not applicable (not mounted) Device Location: External Removable Media: No Any ideas would be appreciated.

A **long** time ago, I installed Paragon's NTFS drivers.  But I no longer any NTFS drives (since almost as long). But yesterday, I had a few apps open, and GraphicConverter had the focus, when this popped up: There is no reason I can think of for any program that was running to suddenly try to do anything with NTFS.  **How can I identify "A program" when it does something like this?**

I sometimes need to mount USB drives that are NTFS formatted and write to them. On Mavericks I achieved this using the Homebrew formula ntfs-3g which depends on osxfuse. After upgrading to Yosemite, osxfuse is broken. Homebrew message: ==> Upgrading osxfuse osxfuse: OS X Mavericks or older is required for this package. OS X Yosemite introduced a strict unsigned kext ban which breaks this package. You should remove this package from your system and attempt to find upstream binaries to use instead. Error: An unsatisfied requirement failed this build. I take this to mean that the kernel extension used by osxfuse is completely disallowed in Yosemite because it is not digitally signed by Apple, whereas in Mavericks it was allowed. So, is there any way now to mount and write to an NTFS-formatted USB drive in Yosemite using either open-source software or free, unencumbered (not spyware/malware or bundled with useless toolbars etc.) software from the App Store?

Just a quick question, is NTFS supported on El Capitan? I just plugged in my external hard drive and I am able to copy stuff from it, but not write to it. I guess only read mode is supported?

before writing I made a lot of trials and I did read a lot of posts and google results: the results are or very old and no more working or claiming the /etc/fstab solution is no more working and that one should make "my hand" sudo mount -t ntfs -o rw,auto,nobrowse /dev/disk4s1 /Volumes/Disk1TB without specifying that this must be done every single time... I summarize (also adding weird things I see): 1. Installed ntfs-3g for Mac, via brew with brew install ntfs-3g-mac. 2. if I do:

bozzo@host-10-25-128-252:duranti> sudo mount -t ntfs -o rw,auto,nobrowse /dev/disk4s1 /Volumes/Disk1TB            
    bozzo@host-10-25-128-252:duranti> touch /Volumes/Disk1TB/prova
    bozzo@host-10-25-128-252:duranti> ls /Volumes/Disk1TB/prova   
    /Volumes/Disk1TB/prova
    bozzo@host-10-25-128-252:duranti> ls -lh /Volumes/Disk1TB/prova
    -rwxr-xr-x  1 bozzo  staff     0B  4 Lug 15:47 /Volumes/Disk1TB/prova

I'm able to mount RW. 3. if I do:

bozzo@host-10-25-128-252:duranti> sudo mount -t ntfs -o rw,auto /dev/disk4s1 /Volumes/Disk1TB 
    bozzo@host-10-25-128-252:duranti> touch /Volumes/Disk1TB/prova                      
    touch: /Volumes/Disk1TB/prova: Read-only file system

I'm not able to write anymore... Why nobrowse is interfering with the writeability? 4. if I have an /etc/fstab like this:

bozzo@host-10-25-128-252:duranti> cat /etc/fstab           
    #
    # Warning - this file should only be modified with vifs(8)
    #
    # Failure to do so is unsupported and may be destructive.
    #
    #UUID=F842A87E-2203-4DD4-A1E3-7F63B8E8DB91 /Volumes/Disk1TB  ntfs rw,auto,nobrowse 0 0
    /dev/disk4s1 /Volumes/Disk1TB  ntfs rw,auto,nobrowse 0 0

the disk is mounted in RO, and with the name of the Volume (i.e. under /Volumes/Elements and not /Volumes/Disk1TB, so using the standard OS X feature...). Same if I use the UUID. Any idea on how to mount an ntfs drive, in the path I choose, RW, **automatically**?

I have an external Seagate hard drive that is recognised and works on Windows computers but not on my MacBook Air which I am currently using. I am able to mount the hard drive in read-only mode but I want to write files to it from my computer. Using the Paragon Driver software offered by Seagate does not work for me, as I am only able to mount my hard drive in read-only mode. I have installed NTFS-3G using Homebrew, following the instructions on this tutorial site . After installing NTFS-3G, I was able to copy a folder to my hard drive. However, the size of the folder is 4 GB, so it took some time to be copied. However, when the folder copy progress bar reached the end, I received the following error message: And the folder was not copied. I have tried copying it another time to my hard drive to see if it would work but have still received the same error. I am not sure why this error message is occurring and how I can resolve it. Any insights are appreciated.