#MOUNTY COSTUME MAC OS X#
#MOUNTY COSTUME UPDATE#
#MOUNTY COSTUME DRIVER#
#MOUNTY COSTUME WINDOWS 10#
#MOUNTY COSTUME PC#

Russian Credits Page added (again, thanks to Anton).

Note: Old devices which does not contain UUID cannot be tracked for auto-mount.

bug fix for crash when Volume does not contain UUID (e.g.

Version 1.9 - 21th of Sep 2018, last version compatible with macOS Catalina and earlier

#MOUNTY COSTUME UPDATE#

remove deprecations: update of notification framework.

Version 1.10 - 29th of Nov 2020, this version is only compatible with macOS 11 Big Sur and up

notifications were not thrown because the authorisation request was missing, this is fixed now.

compiled as universal binary including both x86_64 and arm64 architectures to run natively on Intel and Apple Silicon.

added tolerance to volume kind label if its not exactly written as 'ntfs' but contains the 'ntfs' string.

the dark appearance icons are dimmed a bit now.

when macOS appearance switched between light and dark, the status icon was not updated accordingly, this is fixed now.

once Apple will provide a fix, I will switch back to DiskArbitration framework.

Also, the mount point has changed from system mount point '/Volumes' to a user-owned hidden mount point in user's home directory '~/.mounty' for that reason

as a workaround, I have switched to NSTask API but now you need to input credentials for elevating privileges, sorry for inconvenience.

I have filed a bug report to Apple, hope that this will be solved sooner or later.

now the 'mount_lifs' command is triggering the mount but custom flags like 'read/write' are now ignored which leads into a mount failure.

Apple has changed the entire mount process in Monterey from the previous kernel based architecture toward one that runs primarily in user space.

added compatibility with macOS 12 'Monterey'.

if you are running macOS Big Sur or earlier there is no need to update to current version.

Mounty is still operating with NSTask workaround on macOS 12, at least there was an update on my bug report that it might be fixed in future OS update.

fixed a bug in macOS 12 where Mounty is left in inconsistent state when re-mount fails due to NTFS filesystem marked as 'dirty' and needs cleanup by chkdsk on Windows.

added Catalan localization, thanks to David Lahoz.

added Ukrainian localization, thanks to Andriy Kupyna.

Version History Version 1.15 - 28th of August 2022 Thanks to Giovanni for his patience to reveal this issue during a remote debug session :)

#MOUNTY COSTUME DRIVER#

In this case it might happen that the macOS kernel driver ist not able to re-mount in read/write We have seen that certain third-party NTFS tools will re-name the volume kind property of an NTFS drive to something Mounty will not recognize a drive or re-mount read/write even if the drive is NTFS formatted actually Within Windows running, you need to run the command powercfg /hibernate off in an admin powershellĪnd restart Windows to disable this feature and remove the lock to enable it for Mounty. There is a Fast Start feature in Windows which might be enabled by default, and this is causing the drive to be locked. If you try to mount a Windows System partition, Mounty might fail when Hibernation feature is enabled.

#MOUNTY COSTUME WINDOWS 10#

Xattr -d testfile.txt Unable to re-mount in read/write mode when trying to mount Windows 10 partition If you open the file path in terminal application, you can list the attributes with ls ,Īnd remove those attributes with xattr -d com-apple.

Manpage of xattr for further explanation. This is because the file has extended attributes, refer to Sometimes the files are grayed out and cannot be modified anymore. If you do not own any Windows you can use tools for macOS that can deal with NTFS partition maintenance, chkdsk command line utility or professional tools like GetDataBackįor Windows.

#MOUNTY COSTUME PC#

Mounty will not delete anything by itself, please try to restore your files on a Windows PC using usual recovery s/w, The NTFS partition might be marked as 'dirty' and the Apple NTFS driver cannot recover from that situation. This is usually happen when not all files are written properly due to an unmount operation not finishing. Suddenly all my files disappeared - please help!

#MOUNTY COSTUME MAC OS X#

Mac OS X will not be able to re-mount in read-write mode for that reason. The volume will be marked as 'not cleanly unmounted'. If you simply unplug the USB stick from PC without using the little tray icon to detach the hardware This can happen when the USB stick is not cleanly unmounted from the Windows PC. An alert is popping up telling me to re-attach the stick, but this To make it easier to re-locate the drive I have added the 'Show in Finder' option in Mounty menu. The mount point becomes hidden and disappears from Desktop and Finder menu. It allows read/write mount of NTFS drives only with the 'nobrowse' option. Some questions that might come up My NTFS disk disappears from Desktop when using Mounty

Mounty costume