Unable to mount external hard drive in write mode on MacBook Pro post Ventura update

Just a heads up for anyone else who may encounter this. I eventually remembered that I was actually working with a Seagate drive and that Seagate provides a separate but identically named version of NTFS for Mac specifically for its drives and that I had to upgrade/install the latest version of that software. It had been so long ago that I installed it that I had forgotten. It appears almost identical (minus the activation part, since that doesn't apply) and there is no indication in the app it is from Seagate. Here is more information https://www.seagate.com/support/software/paragon/

As mentioned here before, updating the NTFS software by Seagate worked like a charm! Apparently new Mac Os versions revoked the rights or something. I don't know. But I got the exact same error and the update worked perfectly.

I reinstalled my third party app (Paragon NTFS for Mac) and it took care of the problem.

What format is the external drive? Maybe it is formatted ntfs for Windows and when you updated you did not update your third party app that allowed you to write to the drive. But it could also be a drive problem. You could be running Mac Superdrive while running macOS Catalina. Beyond those common reasons, error 49153.

Try restarting your Mac. Try the drive on another Mac. Try First Aid in Disk Utility.

Provide some system details and context.

Do you have a backup? If so, I suggest you reformat the drive in APFS and restore from Tine Machine.

Yes, my NTFS format drives will not mount since I upgrade to Ventura 13.4. (except in Read Only) I will look some more at my third party app.

And since you bought the topic, we need to update the third-party app.

How come when I uninstall the app and restarted the mac, still it doesn't automatically mount the drive in read only mode?

I have 2 Seagate drives that mount perfectly on a 2011 MBP but not on my new MBP. Why should I have to go to any inconvenience to get the drives to mount on my current machine just because someone at Apple makes a mistake with an update? Just fix it Apple!

I'm running into this issue as we speak. Were you able to find a solution to the problem? The update to 13.4 messed something up