TinkerTool System 2

On this page

TinkerTool System Release 2

Known Issues

There are currently no known issues for this product.

Frequently Asked Questions

Q: Can the Standalone Utility of TinkerTool System coexist with other tools that are also designed to be used in Single User Mode? Do I need to uninstall other tools first?

A: You don't need to care about the existence of other Single User Mode applications on your hard drive. As long as Mac OS X is capable of starting in Single User Mode to a command-line prompt, you can select between any commands or programs you might have installed. There are no conflicts to expect.

You only should avoid to use the multi-tasking capabilities of Mac OS X to run several of such tools really in parallel. If you like to use the features of different tools, it will be recommended to reboot the system each time before starting an alternative application.

Release Notes

TinkerTool System may automatically quit if it is forced to open manipulated third-party applications on OS X 10.8 or later: If you are using TinkerTool System Release 2 with the operating system OS X 10.8 or higher, the application can quit immediately without displaying an error message first, when you are using a feature that analyzes the contents of a third-party application which contains untrusted, manipulated code. The line Exception Type: EXC_CRASH (Code Signature Invalid) can be found in the associated crash log.

Workaround: Although this looks like a crash and the operating system is creating a crash log, this is not an actual crash but the correct and intended behavior of a security feature established by TinkerTool System and OS X. The application actively tries to avoid that any bad program code can reach its memory area. If you are using functions which cause the application to read code parts of other programs (e.g. selecting one of the “thinning” features) and OS X “knows” already that this other code cannot be trusted, high-security applications like the Finder and TinkerTool System R2 will immediately shut down as a security measure, preventing that the bad code could contaminate them. The best solution to avoid this problem is to delete the bad third-party software. If you don’t like to do this, you must avoid that the bad software can run in the same OS session before TinkerTool System should open it. (Restart the computer, preventing that the bad software can run, and only then let TinkerTool System work on the bad software if necessary.)


When using the feature to remove entries for Recent Documents in all applications, TinkerTool System may sometimes appear to freeze for a few seconds during the clean-up operation: If you are using OS X 10.8 Mountain Lion and you run the function User > Recent Items with the option Remove entries for Recent Documents in all applications not currently running enabled, it can happen that TinkerTool System temporarily stops all processing. The rotating disk cursor appears, and the warning message “not responding” may be shown in the list of running processes.

Workaround: This is an intended safety feature of TinkerTool System R2 when it detects an operating system which does not work according to specifications. In OS X Mountain Lion, the preferences subsystem of the operating system can be overloaded by too many accesses in short time intervals, leading to temporary failure. This could cause OS X to ignore the application’s commands to remove entries for Recent Items. To avoid this, TinkerTool System stops all operations in this case and automatically waits until the operating system recovers, which should happen after 8 to 90 seconds. You won’t need to do anything further, just wait until the application continues its work. Such effects can occur for users who have more than 180 to 250 sets of preferences in their user accounts.


When removing language support packages from software components, the presence of more than one package for the same language will cause removal of one package only: Some specific software components shipped as part of Mac OS X may contain a subtle packaging error regarding their support for different languages. In this particular case, a software product comes with more than one language package for exactly the same language variant. For example, an application could contain two packages to support the Japanese language, one with the label “Japanese”, the other with the ISO 631 language code “ja”. In this case, neither Mac OS X nor TinkerTool System can decide which package is the correct one when the user wishes to remove Japanese language support. TinkerTool System will automatically select one of the affected packages and remove it, but not the extra ones. Typically, some communication drivers for EPSON® printers, the EPSON EPI Jet Printer Driver Library Version 2 (EPIJPrDrvLib2), and the Java Applet Launcher show this type of packaging problem.

Workaround: Run a second pass of the language removal procedure for the affected components. The excess packages will be removed as well.


The daily periodic task may not start correctly in Snow Leopard. Opening the report of the daily task may not work as expected: When trying to launch the daily periodic task of Mac OS X 10.6 Snow Leopard, no matter if you are using TinkerTool System or if you start the task by other means, the scripts may not run correctly, but crash or hang instead. Using the Open button to review the reports of the daily task in TinkerTool System may also not work. The program might need an extremely long time to open the report or might also hang.

Workaround: This problem is caused by a corrupt daily task entry created by the Mac OS X updater under certain circumstances when migrating from Mac OS X 10.5.x Leopard to Mac OS X 10.6 Snow Leopard. In addition to the effects already mentioned, this can also cause parts of the system log to be copied into the daily report which can then grow to a size of several hundred megabytes or even several hundred gigabytes, wasting storage space. To repair your system, perform the following steps:

  1. Use the Finder, selecting the menu item Go > Go to Folder to open the folder /etc/periodic/daily.
  2. Delete the file 500.daily.applesaved in this folder. Administrator permission is needed to perform this step.
  3. Use the Finder, selecting the menu item Go > Go to Folder to open the folder /var/log.
  4. Delete the file daily.out in this folder. Administrator permission is needed to perform this step.

Inheritance settings in Access Control Lists might be ignored when creating document-like files via an application on the graphical user interface: If you have defined an Access Control Entry for a folder and this entry uses one of the ACL inheritance features, the settings will be inherited correctly onto new files created in that folder when a low-level program, for example a command-line utility, is used to create the files. However, the inheritance will fail when a high-level application using the typical document features of Mac OS X is used to create the files.

Workaround: This is a known defect in all current versions of Mac OS X 10.6. Although this is a serious, security-relevant problem, it is currently unknown when Apple will fix this bug. No workaround is known.


If you are using one of the options to exclude disk volumes from specific features, the automounter processes of Mac OS X Snow Leopard will regularly record warning messages in the system logs: After adding at least one volume at System > Volumes > Special Mount Options for Volumes you will see messages of the form “Mount for UUID=x has no path for the directory to mount” being logged by the automounter processes autofsd and automountd.

Workaround: This is a known defect of Mac OS X 10.6 Snow Leopard. You can safely ignore these messages.


When using a MacBook Pro of the “Early 2011” model series (having identification codes beginning with “MacBookPro8”), the system might return invalid hardware information: Apple computers of the model series MacBook Pro 13-inch (Early 2011), MacBook Pro 15-inch (Early 2011), and MacBook Pro 17-inch (Early 2011) are originally shipped with a special release of Mac OS X, known as version 10.6.6 Build 10J3210, and the firmware version MBP81.88Z.0047.B04. Both components appear to be immature, not supporting all aspects of the MacBook Pro computers correctly yet. The systems might return incorrect information about technical details of the processor package and contain invalid entries in their System Management data. Applications such as TinkerTool System Release 2 depend on the operating system to respond correctly on hardware information requests. The following details could be display incorrectly: number of processor cores per processor package, system bus clock frequency, bus widths of memory chips, onboard devices, available expansion slots. This list might not be complete

Workaround: There is no known workaround. Apple might or might not resolve these problems with future versions of Mac OS X and the MBP81 firmware. It is Apple’s policy not to comment on any technical details of Intel-based computers.


With Mac OS X 10.7 Lion, the check mark at “Login > Screen > List of users able to use this computer > Show local users” cannot be removed when it has been set: You can set the check mark if the aforementioned option is off. However, you cannot remove the check mark if this option is on.

Workaround: This is an intended safety feature of TinkerTool System R2. The login screen of Mac OS X Lion may show a critical problem when the display of local users is disabled. In this case, the entire login interface may disappear. Apple is aware of this problem. It is not expected however, that they will fix it for the operating systems Mac OS X Lion and OS X Mountain Lion.


Issues with the security component when mixing our system utilities of the “pre and post Gatekeeper” era

With Mac OS X Lion 10.7.3 and later, Apple introduced a new security feature called Gatekeeper. (With Mac OS X 10.7.3 and 10.7.4, Gatekeeper is not visible and not enabled by default, although it is available.) Gatekeeper allows you to define a system policy where the operating system won’t allow to launch applications from untrusted sources.

Our system tools have been using security techniques similar to that of Gatekeeper since October 2007. However, with Apple’s introduction of Gatekeeper, subtle conflicts can arise because the definition of trusted software is naturally different between our own applications and that used by Apple. As a consequence, “old” software versions from the “pre-Gatekeeper era” cannot (and should not) trust up-to-date versions. For this reason, if you are using two or more of our system utilities that contain security features, you should avoid to have “old” and “new” versions installed at the same time. There is absolutely no risk in doing so, but each time you switch between an up-to-date and a “pre-Gatekeeper” version, you will see a warning message similar to this:

The security component has been modified

The part of the application that is privileged to perform critical security operations has been modified. This could be an attempt to break into your computer. Please inform your system administrator or security officer. Application Name will try to remove the modified component.

The simple solution to this problem is to update all our system applications in parallel. When using two or more of the following applications, make sure that they have at least the following version numbers (or later versions). Do not use older versions at the same time: