NTFS external drives won't mount after security update 2021-003 (com.apple.DiskManagement.disenter error 49221.)

sizza64 wrote:

will wait until apple give us a new patch for this bug! thanks again!

I would not expect a fix from Apple since it is the third party vendor & developer who are responsible for making sure their third party app works with macOS. @PachisCruz's post later in this thread even proves that the problem is with the manufacturer's third party driver since after uninstalling the manufacturer's driver and rebooting, @PachisCruz was able to read the NTFS drive which shows that macOS is functioning fine and it is just the manufacturer's driver that has the problem. Of course macOS does not have native built-in write support for NTFS volumes, but at least the NTFS volumes can be read after uninstalling the drive manufacturer's software. See @PachisCruz's specific post I referenced here:

NTFS external drives won't mount after se… - Apple Community

This is why most contributors on these forums recommend against using the manufacturer's proprietary software for managing drives because the proprietary third party drivers may break after a macOS update and users will need to wait until the third party developer fixes the problem (if they even do so). Using a native built-in file system included by default with macOS is always the safest and most reliable option.

Corroborating pavlascz's reply, this is the response from Paragon support:

"After the latest macOS 10.15.7 Catalina Security Update 2022-003 (19H1824),

issues have been reported with mounting NTFS volumes using the NTFS for

Mac driver. The Development team were able to reproduce and confirm the

issue. We expect it to be fixed in the next macOS updates.

For now, the following workaround can be tried:

1) Make sure you're using Microsoft NTFS for Mac by Paragon Software build 15.9.314

It can be downloaded from the ParagonBox user portal if you have a license registered there or directly from the site:

https://www.paragon-software.com/home/ntfs-mac/

Be sure to uninstall any previous versions as described below:

https://kb.paragon-software.com/article/4500

2) Connect the drive containing the NTFS partition, and make sure the partition is not mounted.

3) Open the Terminal utility  (Application -> Utilities -> Terminal) and perform the following command to create a mountpoint:

sudo mkdir /Volumes/ntfs

Please note that if you need to mount several NTFS volumes simultaneously,

you'll need to create the corresponding number of mountpoints.

(for instance

sudo mkdir /Volumes/ntfs

sudo mkdir /Volumes/ntfs1

etc)

4) Run the following command:

diskutil list

and note the NTFS partition's Identifier (disk0s3, for instance)

5) Run the following command to mount it:

sudo /Library/Filesystems/ufsd_NTFS.fs/Contents/Resources/mount_ufsd_NTFS /dev/diskXsY /Volumes/ntfs

where diskXsY - the NTFS partition from the previous step

/Volumes/ntfs - the mountpoint from Step 3

(for instance)

sudo /Library/Filesystems/ufsd_NTFS.fs/Contents/Resources/mount_ufsd_NTFS /dev/disk0s3 /Volumes/ntfs

If possible, please save screenshots of the Terminal commands' output in case the mount still fails.

Please attach new verbose logs if the issue is still present:

https://kb.paragon-software.com/article/8138"

agharprem wrote:

This is an update on my previous post.

Using the terminal to mount the disk, didn't last enough. After I shut down my laptop and I turned it back on the disk didn't mount.

You must issue the Terminal command each time you boot or reconnect the drive.

Also, the only time it mounted it was only "read".

How did you make work r/w/e?

You only used the default macOS NTFS driver to mount the external drive which only supports reading NTFS volumes.

You need to specify the third party driver utility for mounting the NTFS file system as Read+Write like @wanderdesigner did in the following post (several posts above) where they used the Tuxera NTFS driver which must be installed for the command to work. IIRC, the Tuxera driver may be a Beta driver so use at your own risk.

NTFS external drives won't mount after se… - Apple Community

FYI to everyone reading this thread, People should never blindly use any commands in the Terminal app since there is no safety net. People should always understand the commands being used. Even people with years of command line experience can make a simple mistake which can be devastating to their data or OS. I mean no disrespect to anyone, but people should know there is always a risk with the command line. Research any commands or options you don't understand before using any command. Everyone starts out with no knowledge of the command line, and everyone ends up making mistakes with it. It is important to realize that macOS will not protect you from mistakes or typographical errors when using the command line.

Edit: @platinumbob on the first page of this thread has a link to Tuxera's website with the official instructions for the Tuxera NTFS driver. Here is the Tuxera link from @platinumbob's post reposted:

https://macsupport.tuxera.com/hc/en-gb/articles/4696818610706-Help-I-can-t-mount-NTFS-volumes-on-macOS-Catalina-after-the-latest-update-

And @pavlascz in a post on the first page of this thread here also has a link to instructions for using the Paragon driver. This is the link in that post for the Paragon driver:

https://kb.paragon-software.com/article/56

Perhaps there are other posts between them and this post of mine, but I'm not reading them all again.

Fix NTFS for mac by Paragon Software with Catalina 10.15.7 (19H1824):

Please perform these actions:

1. Uninstall version 15.9.314:  https://kb.paragon-software.com/article/4500
2. Reboot
3. Install version 15.9.366 (with fix): https://kb.paragon-software.com/article/8468
4. Then check if the issue is resolved.

It worked on my end, cheers!

I' ve done some testing for I ran into this issue recently. I've found the follwing (testeing with Tuxera and Paragon): There is no way mounting a device as long Tuxera ior Paragon is installed. Their respective ntfs-driver prevents mounting. As soon as the respective driver is uninstalled, mounting works as described on Tuxera-Webside or by using Mounty.appo or by using terminal-commands. Reding and writing from/to these disks is then possible again

The reason is that the infunctional ntfs-driver keeps the disk in an inactive state which can't be by-passed as long as the drivedr is present.

I've only tested on Catalina.

It is really annoying but the still is exFat which could help getting over this period.

For those who using Paragon NTFS, follow this:

https://kb.paragon-software.com/article/56

The best solution is to temporarily transfer the data from the NTFS volume to another location and use Disk Utility to erase the drive using a file system supported natively by macOS such as MacOS Extended (Journaled) or exFAT if the drive is being used only by macOS or if it will be shared with Windows respectively. This avoids any issues with third party drivers that can break whenever macOS is updated. If people rely on the manufacturer's proprietary driver, then there is always a risk of macOS breaking the third party driver.

FYI, you should always have frequent and regular backups of your computer and all external media which contains important & unique data.

I couldn't mount it with the terminal as others, but I downloaded the NTSF software frome Seagate web page (which is the brand of my external hard drive); then uninstall the NTSF application. When I restarted the computer, it mounted the disk. I can't write on it, but at least all the information is there. Be carefull because, the computer recognizes it as a new disk and asks if you want it as a backup to use with Time Machine. If you accept, all the previous information will be lost.

Now that I can read it, will make a backup and then try to reformat it.

I ended up just re-installing Catalina. It took less than an hour and everything is back to normal. Obviously I won't be installing the security update again.

You can find the installers here:

https://appleinsider.com/articles/21/12/03/how-to-download-an-old-macos-installer

Solution by tuxera website 2022.

Bypass Disk Utility and Disk Manager, and mount the volume manually:

Open Terminal (Applications → Utilities → Terminal)

Create a mount-point in the /Volumes directory with the following command:

sudo mkdir /Volumes/ntfs-disk

Then find out what the identifying numbers of your storage media and volume are, by using the following command:

diskutil list

Note the listing of your desired volume, and take note of the entry diskXsY where X and Y are numbers:

Finally, issue a command to mount the filesystem:

sudo /Library/Filesystems/tuxera_ntfs.fs/Contents/Resources/mount_tuxera_ntfs -o nodev -o noowners -o nosuid /dev/diskXsY /Volumes/ntfs-disk

Well, they removed my reply... i assume that they didn't like the thruth... anyway!

i'd received an answer from WD(western digital), my drive is an MyBook, tech support who told me to backup my files and reformat... ouf! pain in the b... but i did it and choose EXFAT format, 'cause i need a multiplatforms ext. HDD... no more problems guys! and my drive still mount on PC or Mac... ;-)

Version 15.9.366 of Paragon's Ntfs works like a charm. Volumes have to be manuially activated though, but then you can do whatever you could do before the macOS-security-patch.

the drive is an WD mybook... so if i fully understand, i should contact Western Digital for a new driver that will work...

I got Paragon «NTFS for Mac» working on my mac...

i will follow your advises... ;-) thanks

EricWallis wrote:

Very unhappy with apple that they did this. I have many NTFS drives and now cannot write to. They should fix in the next update.

While an Apple update may have broken the third party NTFS drivers, don't expect Apple to do anything to fix the issue. It is up to the third party developers of those NTFS drivers to make their drivers compatible with macOS. This is the risk you accept (or take) when you rely on third party software to manage your external drives. Contact the developer of the third party software you are using to manage the NTFS drives to get assistance.

If the third party developer believes it is something Apple needs to fix, then the third party developer will contact & work with Apple about the issue. Sometimes an Apple patch may change something significant which is necessary so Apple cannot make it behave the same as before, so it will mean the third party developer will need to adjust their software to work with the new way macOS works. Usually people should assume this is the case and put pressure on the manufacturer/developer of the device & third party software to make their product work as advertised.

Or as I and some other contributors have already mentioned multiple times in this thread, there are other options which are less likely to cause problems with external drives when macOS is updated or upgraded. People need to accept the consequences of their choices. If a person wasn't aware of their other options before, then that is understandable because the drive manufacturers tend to push their proprietary third party software instead of informing their customers about other options, but people should always question the need of any software that is installed on their computer. It is still possible to use a native built-in macOS supported file system, but it will require a spare drive of the same or larger size to transfer the files to another drive.

I personally try to minimize the installation of third party software as much as possible which greatly minimizes problems with my computers.