Category Archives: Yosemite

How to track app use with OSXClock

Screen Shot 2015-03-10 at 17.45.36
OSXClock just got a major update, adding a productivity log that helps you to track how much time you spend actively using each app on your mac.

I wrote an ad-hoc AppleScript to do this sometime ago that proved pretty popular, but I wasn’t satisfied with either the code or the interface. OSXClock improves on that by tapping directly into Cocoa’s API and by offering a more attractive display.

OSXClock is currently on offer for only $2.99. Lots more exciting features are planned for future updates, so now’s a good time to get with the program, folks! 🙂

*OSXClock requires OSX Yosemite

how to sit down safely

osxclock 1

Well, Tim Cook says sitting is the new cancer…and since I don’t envisage myself in the market for an iWatch, but do need to be reminded to get up and take a break from the desk every 60 minutes, I wrote OSXClock.

I also need a clock for displaying the time on a large screen on occasion when conducting timed-based tests. In the past, I’ve used for this, but it has a couple of disadvantages: first, you have to be connected to the internet; second, it doesn’t have an alarm or timer.

Hence, OSXClock was born, Applehelpwriter’s answer to the Apple Watch :p, and considerably cheaper! 😀

Script Editor battle

Here’s a short video showing some of the differences between Apple’s own Script Editor and my DisplayDroid.

If you haven’t got 5 minutes, the highlights include:

DisplayDroid shows result of each line of the script
DisplayDroid offers more informative error messages
DisplayDroid has automatic language detection (between AppleScript and JavaScript)
DisplayDroid allows you to set a breakpoint on any line in your script
DisplayDroid lets you step through the script line by line

DisplayDroid – limited free betas available


The first beta of DisplayDroid is, for a limited time, freely available to anyone interested in testing (requires Yosemite, 10.10). DisplayDroid executes an AppleScript or JavaScript whenever you connect or disconnect an external monitor, primarily with the intent of automatically setting up the environment depending on your display status. DisplayDroid includes its own script editor and a number of presets (i.e., built-in scripts) to get beginners started.

DisplayDroid editor Full details of DisplayDroid can be found here: To get a free beta copy of the app, please register for the Community forum here: and I will email you a beta copy of the app in the next few days.

how to get back your Dock preferences

dock prefs

As I noted in an earlier post, one of Yosemite’s annoying usability regressions is that Apple have removed the Dock Preferences from the ïŁż menu.

I was so irritated by this that I thought I’d just slip them back in to the menu bar. 😉 Hence, FastTasks 2 from v1.6 onwards now lets you manage most Dock preferences from the menu bar again!

App Fixer beta now available! đŸ’„

app fixer
I’ve just released the first beta 0.1 version of App Fixer over on my software distribution site,

App Fixer aims to help you remove corrupt preference files and window Saved States that can sometimes cause apps to crash on launch or during normal operation. Traditionally, we have to go hunting through the user library hoping to identify the correct files to remove. Now, App Fixer does it for you.

If you have an app that won’t launch or that’s behaving badly, or you just want to start with a clean slate by removing user defaults/preferences (I’m looking at you Photoshop!), App Fixer will do it for you in a click.

Grab a free copy of the beta from here:


change the Dock position

dock position
One of Yosemite’s minor irritations is the removal of the Dock position menu item from the Apple menu.

Now we’re supposed to go hunting around on the Dock for the tiny Dock item separator and control-click it to get the menu, or open up System Preferences > Dock. All too fiddly for my taste.

The following script will rotate the Dock position through left, bottom and right. Just copy the code below and paste straight into a Script Editor document. Hit the Run button to see it in action. Then, save the script to your ~/Library/Scripts folder. Use FastScripts or set up a Service with Automator (example here) to create a hotkey.

Now you can change the Dock position with ease. 🙂

tell application "System Events"
 tell dock preferences
   set x to screen edge
   if x is left then
    set properties to {screen edge:bottom}
   else if x is bottom then
    set properties to {screen edge:right}
    set properties to {screen edge: left}
   end if
  end tell
end tell

how to troubleshoot your mac with FT2

FastTasks 2
Macs are famously reliable beasts, but we often make changes to our machines that can cause unexpected behaviours such as the dreaded spinning “beachball” (i.e., slow response times), excessive fan noise, and crashes.

This is where Apple Support Communities comes in handy, a place where I spent the best part of my spare time for 2 years helping thousands of people solve problems with their macs. With a few rare exceptions of internal hardware malfunction, the majority of problems I’ve encountered with macs involve changes made to the mac by installing or removing third-party software (sometimes unwittingly).

There was a time when people seeking help on ASC were first told to go through a lengthy process of collecting arcane information from various deep and mysterious places on their computer before ASC support volunteers could help determine the problem. Fortunately, there’s now a number of free utilities available that will collect some or all of that information for you automatically, including my own FastTasks 2 and DetectX.

In this post, I’m going to assume you’re using FastTasks 2, for a couple of reasons (aside from the obvious one that its my own app!). First, aside from having a system profiler, FT2 provides other functions that are useful in troubleshooting, whose use I’ll indicate below. Secondly, unlike other analysers, FT2 not only profiles your system configuration at the time you run it, it can also show you what’s changed over time (see Step 5 below), making detection of new problems even faster and easier. For that reason, it’s a good idea to run FT2 when your system is trouble-free so that you have a log of a known ‘good’ configuration. However, I’m going to assume for most of this post that you don’t have a log of a known good state, and walk you through a series of steps that you can use to trackdown troublemakers.

To get started, download FT2 from here, and then proceed to Step 1.

*Note if your problem is with Safari, you can go straight to Step 10.

If your problem is with internet connections / networking, that’s a vast issue too large for this post, but try the advice here first. If that doesn’t work, the FT2’s Profile view contains a lot of information about your network configuration. Click the FT2 menu, choose ‘Analyser > Check now’, and click the Profile tab. Then follow the general advice in Step 11 below.

If your problem involves unusual behaviour of system hardware (keyboard lights, fans, system volume, etc) follow Step 3 of this post first.

Step 1. Put a block behind the rear wheel

The first rule of troubleshooting is not ‘You don’t talk about troubleshooting’ but ‘You don’t do anything until you have a backup stashed away’. Fat fingers and a hasty desire for a cure can lead all of us to make mistakes when following procedures, and the last thing you want to do is accidentally delete some file or resource that is irreplaceable. So, back up first, and cure yourself of the tendency to rush for a solution. Troubleshooting takes time, and troubleshooting without a backup is like changing a wheel on your car without putting a block behind the rear wheel. Don’t get crushed by your own rush to get back on the road!
Step 2. Start with the obvious

Launch FastTasks and wait for the system analyser to finish loading. You’ll see the analyser presents you with an ‘Issues’ page. This page lists any files or apps that are installed on your computer which have, in my experience, been known to cause problems for some users. If your system is clean of these files or apps, the page will be empty, like mine:


If anything is listed in the ‘Issues’ page, your first step is to deal with these as detailed below. If not, you can go straight to Step 3 now.

Depending on the issue, (click on an item in the FT2 window and press the ‘Info’ button), uninstall, delete or move to a temporary folder on your Desktop any items listed in the Issues page. You can open each item in the Finder either by double-clicking it in the FT2 window, or selecting it and clicking the ‘Reveal’ button.

If anything listed in the Analyser as a ‘Performance’ issue has been installed from outside of the App Store, check the Developer’s web pages to see if there is an uninstaller and, if so, use that. If not, move the App or files to the Trash, but do not empty it. At the end of this step, if it turns out that app or file is not the culprit, and you still want to use it for some reason, you can drag it back out of the Trash.

After dealing with anything in the ‘Issues’ list, restart your mac and see if the problem behaviour is solved.
Step 3. Wipe the board

If you didn’t have any issues, click the FT2 icon in the menu bar and note the system information in the lower half of the menu. Look at the ‘Uptime’ stat. This shows how long since you last rebooted your machine. If the problem behaviour has only been noticed since the last reboot, then restart your machine now, and test again.


More often than not, most unexpected or strange behaviour that comes out of nowhere can be solved by a system reboot.
Step 4. Check the disk
Click the FT2 icon and note the system information in the lower half of the menu. Look at the empty/full icon and the stats below it on disk usage (you can choose to have one of these shown in the menu bar all the time if you wish, as well as change the color of the icon. In the menu, choose Preferences > Menu Bar Icon). You should have got a warning from FT2 if your disk is gettting critically full, but even if your disk is only 70% or so full, you could find your machine slowing down when Spotlight is indexing or if you’re doing any operation that requires a lot of disk activity. My recommendation for a speedy machine is to keep disk usage below 60% if possible (I rarely let my own disk ever get above 50%).

While we’re thinking about the disks, let’s just check the S.M.A.R.T status of the Internal boot disk. With the FT2 window open (if not, click ‘Analyser > Check now’), click the ‘Profile’ tab. Scroll down right to the bottom of the page and check that the S.M.A.R.T status says ‘verified’. If it doesn’t, there’s your problem: you need to replace your hard disk ASAP.


Step 5. Reverse gear

If you’ve ran FT2 before, anything that’s changed since the last time you ran it will be highlighted in the view (you’ll also see the yellow warning triangle at the top).

Screen Shot 2014-10-22 at 21.26.22For example, in the screenshot above, note how FT2 records that the Ghostery extension has installed an update of itself in the background!
If you haven’t run FT2 before, go to Step 6. If you’ve run FT2 before but no changes are indicated, look through the logs by using the back and forward arrows on either side of the ‘Run’ button. For convenience, you can click the ‘Console’ button, then type ‘added’ into Console’s search bar, making a note of anything shown, then type ‘removed’, again making a note of any changes.

Whether you find changes in the Console, logs, or indicated in FT2’s current Profile view, the process is the same. For any change indicated, you need to reverse it. That means, anything added should be removed, and anything removed should be replaced from a backup. However, it’s important to be methodical, so deal with one change at a time, restarting the system and checking for the problem again after reversing each change. If that doesn’t solve it, move on to the next change and repeat.

There’s such a high chance that you’ll discover the cause of the problem this way that its the best argument for running FT2 on a regular basis and before you hit trouble. Trouble always starts with some change

If you’re still encountering problems, go to Step 6.
Step 6. The root of all Evil

Well, maybe not all, but without doubt the overwhelming cause of problems I’ve dealt with on ASC were caused by login items. These are things that automatically run when you log in to your account. Any app or script that’s in your Login Items that causes problems to your system will affect your system from the start of your session and often right through till you log out (often regardless of whether you quit the app in mid-session).

With FT2’s Analyser window open, click the ‘Profile’ tab. At the very top of the page, check what and how many items are in your Login Items. You really don’t want more than four or five items in here in any case, or you’ll notice a real lag betweeen when you log in and when your system is ready to be used. Keep only the essential things in here (yes, I’d say FT2 is one of them, see the end of this Step).

However, even one app can cause problems if it’s the wrong app. To troubleshoot Login Items, click the FT2 menu and choose ‘Login Items > Remove All’. Click ‘OK’ to confirm. When you see the notification that Login Items are empty, restart your mac and test for the problem.


If the problem is not solved, go to Step 7. If the problem is solved, you can try adding each of your login items back in one at a time to ascertain which item caused the problem. Better still, just keep your login items empty and enjoy faster start up times.

The exception to the above advice is to consider keeping FT2 in your Login Items. The reason is that every time you login in, FT2 will run a background profile check and store that in its logs. That’s a vital tool for solving troubleshooting problems in the future (see Step 5 above), and one of FT2’s most useful features (however, if you don’t want FT2 to start on login, choose ‘Preferences > Start at Login’ and click to remove the tick).
Step 7. Digging deeper

First, a note about .DS_Store files: In this and the remaining steps, you can ignore any file called .DS_Store shown in the profiler. These are hidden files generated by the Finder and can be ignored (likewise, you can delete them, the system will just recreate them when it needs to).

If you’ve got this far and your problem persists, it’s time to start looking further down the profile list. The next item in the profile view is User Launch Daemons. Notice that FT2 handily shows you where you can find this directory. To use that info, highlight the path shown (omit the closing bracket), then control-click, and choose ‘Services > Reveal in Finder’, to open the directory.

I do NOT recommend deleting files from here directly. Instead, you need to identify which apps these files belong to and uninstall them. After uninstalling, check back in Launch Agents to see if the uninstaller has cleaned up the file. If it hasn’t, you can then delete it (but be sure you’re deleting the correct file).

If the file doesn’t appear to belong to an app or you’re in doubt about its parentage, then move it (don’t delete it) to your Desktop. As with Login Items in the previous step, you need to be methodical here, and test each item after you remove or uninstall it with a reboot. Doing so means you can firmly determine which apps and files are OK and which are suspect.
Step 8: and deeper…
If your problems remain after working through all the User Launch Daemons, scroll much further down the list until you find Domain Library Launch Agents and Domain Library Launch Daemons and Domain Library StartUpItems. For each, you need to follow the procedure in Step 7: in other words, start by identifying the parent app of the file in the directory, uninstall it, check its cleaned up the file in the directory (if not, move it to your desktop) and re-test.
Step 9: Problems, problems, problems

Still not got to the bottom of it? Then we need some more info. The best thing to do right now is determine whether the problem only affects your user account or all users on your system. Knowing this will provide a better focus for continued efforts.

To do that, go to ïŁż > System Preferences > Users & Groups and click the padlock and supply an Admin password to open it. You’ll now be able to click the little ‘+’ button just above the padlock and create an extra Admin account.

After creating the account, restart the mac, log in to the new account and see if the problem affects that account too. Once you’ve determined that, log back into your normal account and go to Step 11 below.
Step 10: Safari and the internet
Problems with Safari and internet connections are a realm all to themselves and too vast to be discussed here except in general terms.

If the problem appears to be peculiar to Safari, then the first thing to do is open FT2 Analyser and click on the ‘Profile’ page. Scroll down to Safari Extensions and take a look at what’s in there. Anything you don’t recognize or anything new since things were hunky dory? If so, focus on that first.

To deal with Extensions, don’t delete things from the directory itself. Instead, open Safari, and from the menu bar choose “Safari > Preferences” and navigate to the ‘Extensions’ tab.

Start by disabling ALL extensions. Now restart Safari. Problem solved? If yes, then start turning one extension back on at a time, until you discover which one is causing the problem. Uninstall the culprit.

If the problem persists after disabling all extensions, go back to FT2’s Profile view and scroll down till you get to User Library Internet Plug-Ins. If there is anything in here (you can ignore .DS_Store), then select the path shown for the directory (omiting the word ‘path:’ and the closing bracket), right-click and choose ‘Services > Reveal in Finder’. Move anything in the folder to your Desktop. Restart the mac and test.

If the problem is solved, try moving each item back to the Internet Plug-Ins folder, one at a time, restarting and testing after each move until you determine the culprit.

If the problem is not solved, return any items you moved to the Desktop back to the Internet Plug-Ins folder. Then, check to see whether other browsers are affected (if you don’t have it already, it’s always a good idea to keep a copy of Firefox on you mac, just to use as a control for Safari tests if nothing else). Make a note of the answer, then follow the instructions in Step 9 above, then go to Step 11 below.
Step 11: What to do next

I hope this post has helped solve your problems, but if it hasn’t don’t panic. Your best resource is Apple Support Communities. Though I’m no longer active there (my spare time is used for software development these days), there are many hands on deck and people with all sorts of specialist knowledge about different areas frequent the boards. The key is to make sure you describe the problem as fully as you can and to post information from FT2’s system profiler (use the ‘Copy’ button). Be sure to mention the results of your tests so that people have got enough information to help you.

Also, please be polite to those who respond to you – ASC is staffed by volunteers, not Apple employees, just spending time to help others out. Finally, please don’t email troubleshooting problems to me personally. You’ll get a faster and better response by using the full resources of the support community.

Good luck! 🙂

FastTasks 2 update available đŸ’„

I’ve just released an incremental update for FastTasks 2. Update 1.3 adds the ability to quickly see whether TRIM is currently on  or off for your SSD disks. Since TRIM support for non-Apple SSDs requires editing a kernel extension, TRIM is regularly disabled on non-Apple SSDs every time users update or upgrade OS X. FastTasks 2 v1.3 now lets you see TRIM status in the information section of the menu.

FastTasks 2 Trim

Get the latest release of FastTasks 2 by going directly to the FastTasks support page, or if you already have FastTasks 2 running, you can use the Preferences > Check for Update > Check now menu item. 🙂

comment désinstaller MacKeeper

before uninstall mavs

Last updated: 16 August, 2015

Volunteers Wanted: Since MacKeeper has become something of an international (ahem…what’s the right word here?) “phenomenon”, we need volunteers to help translate the instructions on this page into other languages. German, Spanish, Japanese, Italian, Korean, Thai, Russian, Chinese, etc…any other language you are fluent in aside from English.

Please contact us if you’re able to contribute a full and accurate translation (spam from commercial translation services will be ignored).


Read this page in English English flag
Lees dan dit artikel in het Nederlands Screen Shot 2016-05-02 at 18.17.41

MacKeeper – Ă©galement connu comme 911 fois Bundle sur l’App Store (maintenant discontinuĂ©). Oui, vous avez vu les annonces partout sur l’internet, des pop-up sur vos pages Web prĂ©fĂ©rĂ©es, il semble ĂȘtre partout. Malheureusement, beaucoup de gens qui l’on tĂ©lĂ©chargĂ©s et utilisĂ©s, on vĂ©cut par MacKeeper de graves problĂšmes, comme en tĂ©moignent plusieurs des centaines de commentaires Ă  la fin de cet article.

AprĂšs avoir lancĂ© une version d’essai gratuite de MacKeeper sur une nouvelle installation de Yosemite, MacKeeper m’a prĂ©venu que mon systĂšme Ă©tait dans un Ă©tat “grave” avec plus de 1500 “Ă©lĂ©ments” dont je devrais me soucier. Pour rĂ©soudre ceux-ci, il m’a invitĂ© Ă  m’inscrire Ă  un compte payant. Quand j’ai Ă©galement installĂ© une nouvelle copie de Mac OS X Mavericks, obtenu directement Ă  partir de l’App Store d’Apple, MacKeeper m’a averti de la mĂȘme chose :

MacKeeper on Mavericks

Je suppose MacKeepern’ est pas trop impressionnĂ© par l’installation standard d’Apple, et il semble que l’incompatibilitĂ© est mutuelle. En regardant la console, OS X fournit l’avertissement suivant Ă  propos de MacKeeper :

105/12/2015 17: 48: 00,946 [1]: (com.mackeeper.MacKeeper.Helper) .Ce service est dĂ©fini pour ĂȘtre constamment en cours d’exĂ©cution et est intrinsĂšquement inefficace.

Si vous avez installé MacKeeper et que vous souhaitez le supprimer, lisez la suite.

DĂ©sinstallation de MacKeeper 2 et 3

Si vous avez utilisĂ© MacKeeper pour crypter toutes les donnĂ©es, dĂ©cryptez-les maintenant en rĂ©utilisant l’utilitaire. Si vous supprimez MacKeeper sans d’abord dĂ©crypter vos donnĂ©es, vous ne serez pas en mesure d’y accĂ©der plus tard. Ceci ne concerne que les donnĂ©es chiffrĂ©es avec MacKeeper, et non des donnĂ©es cryptĂ©es en utilisant les services de chiffrement intĂ©grĂ© dans Mac OS ou en utilisant tout autre programme.

Une fois cela fait, vous pouvez suivre les instructions de désinstallation de MacKeeper ici :

Ces instructions promettent que tous de composants supplĂ©mentaires et des processus de MacKeeper connexes seront Ă©galement supprimĂ©s. Dans mes tests sur la version de dĂ©monstration de l’application, qui est avĂ©rĂ© ĂȘtre pas entiĂšrement vrai. Voici ce qui a Ă©tĂ© laissĂ© plus aprĂšs avoir utilisĂ© le programme de dĂ©sinstallation de la version de dĂ©monstration :

after uninstall mavs

Je ne sais pas quoi d’autre pourrait ĂȘtre laissĂ© si vous avez rĂ©ellement la version payante de ‘MacKeeper. Tous mes tests sont sur l’essai gratuit. MĂȘme si vous utilisez le programme de dĂ©sinstallation fourni, je vous recommande de lancer un ou l’autre de mes applications gratuites — DetectX (pour OS X 10.6 ou ultĂ©rieur) ou FastTasks 2 (pour Mac OS X 10.9 ou ultĂ©rieur), les deux dĂ©sinstallations sont illustrĂ©es ci-dessus — pour voir ce qui est restes. Vous pouvez Ă©galement faire l’Ă©tape 4 de la procĂ©dure ci-dessous pour vous assurer que MacKeeper n’a pas accĂšs Ă  votre trousseau.

Désinstallation de versions antérieures de MacKeeper

Si vous avez une version de MacKeeper plus tĂŽt que MacKeeper 2012 ou vous souhaitez faire une dĂ©sinstallation manuelle, suivez la procĂ©dure ci-dessous. Vous ne trouverez probablement pas tous les fichiers mentionnĂ©s ci-dessous, mais tout ce que vous trouvez doit ĂȘtre supprimĂ©.

i. Encore une fois, un avertissement : si vous avez utilisĂ© la fonction de cryptage de MacKeeper, assurez-vous de dĂ©chiffrer avant de dĂ©sinstaller MacKeeper. Vous devriez Ă©galement vĂ©rifier si l’un de vos fichiers personnels sont stockĂ©s dans / Documents/MacKeeper Backups.

Time Machine
ii. Si vous utilisez Time Machine, laissez-le connecter et faites l’étape Time Machine (Ă©tape TM) aux endroits indiquĂ©s. Instructions pour l’Ă©tape de TM sont donnĂ©s dans l’encadrĂ© Ă  l’Ă©tape 1 ci-dessous.

iii. Si vous utilisez un clone sans archivage, débranchez le clone et exécutez la procédure ci-dessous sur votre disque dur interne. Quand celui-ci est terminé et que vous avez vérifié que tout est OK, connectez votre clone et effacez la partition en utilisant Utilitaire de disque. Ensuite, faire un nouveau clone.

iv. Si vous utilisez un clone avec l’archivage, redĂ©marrez en maintenant votre clone et exĂ©cutez la procĂ©dure ci-dessous sur le clone d’abord. Ensuite, Ă©teignez votre ordinateur, dĂ©branchez le clone du systĂšme et redĂ©marrez dans votre lecteur interne. ExĂ©cutez de nouveau l’ensemble de la procĂ©dure sur votre disque dur interne.

v. Si vous avez quelque chose dans la Corbeille, videz-la maintenant avant de commencer.

La procédure de désinstallation:

Dans les Ă©tapes 1 – 3 ci-dessous, vous allez chercher des fichiers liĂ©s Ă  MacKeeper et les supprimer. Certains d’entre eux peuvent exister, d’autres non.

Vous pouvez trouver tous ces fichiers MacKeeper automatiquement en utilisant FastTasks 2 (pour Mac OS X 10.9 ou ultérieur) ou DetectX (pour les versions antérieures de Mac OS X), disponibles sur mon site de distribution de logiciels,  Si vous ne souhaitez pas utiliser FastTasks 2 ou DetectX pour une raison quelconque, vous pouvez localiser chacun des fichiers manuellement en suivant les instructions ci-dessous. Dans les deux cas, assurez-vous de lire et de suivre attentivement les instructions.

Une fois que vous avez tout prĂ©parĂ© comme ci-dessus, vous ĂȘtes prĂȘt Ă  commencer la procĂ©dure de dĂ©sinstallation.

1. Si MacKeeper est en cours d’exĂ©cution, quittez-le. Dans la barre latĂ©rale dans une fenĂȘtre du Finder, sĂ©lectionnez l’icĂŽne de votre disque dur et accĂ©dez Ă  votre dossier BibliothĂšque. Regardez dans le dossier Application Support pour le dossier Ă  l’intĂ©rieur appelĂ© «MacKeeper». (Si vous utilisez FastTasks 2 ou DetectX, il suffit de double cliquer sur l’Ă©lĂ©ment dans la liste et il va ouvrir la bonne fenĂȘtre du Finder. Pour Ă©viter?? la rĂ©pĂ©tition, rĂ©pĂ©ter cette opĂ©ration pour chaque fichier MacKeeper montrĂ© dans l’analyseur.) :

/Library/Application Support/MacKeeper

Cliquez sur le dossier une fois.

Étape TM
Si vous utilisez Time Machine, faites l’étape TM maintenant.

Entrer dans Time Machine via l’icĂŽne sur votre barre de menu TM en haut de votre Ă©cran.
Cliquez sur la petite engrenage/ roue dentelĂ©e dans la fenĂȘtre du Finder et choisissez ‘Supprimer toutes les sauvegardes de fichier xxx’.
Entrez votre mot de passe administrateur pour confirmer la suppression. Quitter Time Machine et puis …

Si vous ne l’utilisez pas TM ou aprĂšs que vous avez terminĂ© l’Ă©tape TM, maintenez enfoncĂ©e la touche «Commande» et appuyez sur la touche ‘Supprimer’ pour envoyer le fichier Ă  la corbeille.

2. Toujours dans la bibliothĂšque, recherchez et mettez dans la corbeille un de ces fichiers que vous trouverez de la mĂȘme maniĂšre, en mĂ©morisant si vous avez utilisĂ© Time Machine pour faire l’Ă©tape TM d’abord dans chaque cas :



3. Si vous utilisez OS X Lion 10.7 ou version ultĂ©rieure, utilisez le menu ‘Aller’ dans la barre de menus du Finder et maintenez la touche ‘Option’. Choisissez «BibliothĂšque» dans le menu (oui, ceci est un dossier BibliothĂšque diffĂ©rent dans lequel vous Ă©tiez). Si vous utilisez Snow Leopard ou Leopard, il suffit de cliquer sur la petite icĂŽne “DĂ©part” dans la barre latĂ©rale du Finder et accĂ©dez Ă  la bibliothĂšque. Puis jetez tous ceux que vous trouvez, sans oublier de faire l’Ă©tape TM (le cas Ă©chĂ©ant) d’abord dans chaque cas :







Si vous n’utilisez pas FastTasks 2 ou DetectX, veillez Ă  ne pas supprimer les mauvais fichiers : seuls ceux qui ont les mots «zeobit» ,«MacKeeper»,«911» ou «911bundle » devraient ĂȘtre jetĂ©s.

Mise Ă  jour mai 2015 :

En raison de rĂ©cents changements dans MacKeeper, les fichiers suivants doivent aussi ĂȘtre recherchĂ©s et Ă©liminĂ©s (FastTasks 2 et DetectX ont Ă©tĂ© mis Ă  jour pour rechercher ceux-ci):

~/Library/Application Support/MacKeeper Helper






~/Documents/MacKeeper Backups





Le dernier point ci-dessus devra ĂȘtre enlevĂ© dans le Terminal ou, si vous utilisez FastTasks 2 ou DetectX, vous devez activer «les fichiers invisibles» pour les voir dans le Finder. Vous pouvez activer ou dĂ©sactiver les fichiers invisibles facilement dans le menu FastTasks 2 ou depuis la fenĂȘtre principale de DetectX.

Les Ă©tapes suivantes devront ĂȘtre faites manuellement, mĂȘme si vous utilisez FastTasks 2 ou DetectX :

4. Allez dans Applications > Utilitaires > Trousseau d’accĂš et double-cliquez dessus. Vous remarquerez que le cadenas est en haut dans la fenĂȘtre sur la gauche, plutĂŽt que sur le bas. Cliquez dessus et entrez votre mot de passe admin. Maintenant, passer par tous les Ă©lĂ©ments du Trousseau de la liste (comme Connexion, SystĂšme, Racine) avec ” Tous les Ă©lĂ©ments sĂ©lectionnĂ©s dans la ” liste CatĂ©gorie. Tout ce que vous trouverez liĂ© Ă  « MacKeeper » ou « zeobit », cliquez dessus, puis choisissez Édition > Supprimer dans le menu.

(Merci Ă  Al de mentionner Ă©galement ce point dans les commentaires ci-dessous! :)).

5. Ouvrez l’utilitaire dans Applications > Utilitaires > Moniteur d’activitĂ©.app. Sous 10.10 Yosemite ou ultĂ©rieur, sĂ©lectionnez le menu PrĂ©sentation et choisissez «Toutes les opĂ©rations ». Pour les versions antĂ©rieures de Mac OS X, assurez-vous que « Toutes les opĂ©rations est sĂ©lectionnĂ© dans le menu dĂ©roulant un peu plus sur la droite de la boĂźte de dialogue, puis faites dĂ©filer la liste et voyez si toutes les opĂ©rations appelĂ©es «MacKeeper», «zeobit» ou «911 bundle» sont toujours en cours. Les anciennes versions de MacKeeper peuvent avoir une opĂ©ration nommĂ©e «WINE» l en exĂ©cution, alors regardez aussi pour «WINE». Tout ce que vous trouvez, cliquez dessus et cliquez sur «Quitter l’opĂ©ration» (en haut Ă  gauche).

6. Allez dans votre dossier Applications Ă  partir d’une fenĂȘtre du Finder et sĂ©lectionnez MacKeeper (si vous avez Time Machine, faire l’Ă©tape TM maintenant). Ensuite, maintenez la touche «Commande» et appuyez sur «Supprimer» une fois. Si vous avez placĂ© MacKeeper dans le Dock, assurez-vous de faire glisser l’icĂŽne Ă©galement en dehors du Dock et relĂąchez-la n’importe oĂč sur le bureau. Elle sera supprimĂ©e, de maniĂšre satisfaisante, dans un nuage de fumĂ©e. 😀

7. Lorsque vous aurez terminé de remplir votre corbeille avec toute cette ordure, cliquez sur le Finder > Vider la corbeille.

8. Allez Ă 

ïŁż > PrĂ©fĂ©rences SystĂšme > Utilisateurs et groupes (ou «Comptes» pour Snow L) | Ouverture

Si vous voyez quelque chose Ă  voir avec MacKeeper dans la liste des Ă©lĂ©ments, mettre en surbrillance, puis cliquez sur le petit bouton Moins “-” prĂšs du bas de la liste.

9. RedĂ©marrez votre Mac. Tout devrait ĂȘtre de retour Ă  la normale, mais il faut vĂ©rifier le Moniteur d’activitĂ© une derniĂšre fois pour ĂȘtre sĂ»r.

10. AprĂšs le redĂ©marrage, assurez-vous de rĂ©parer vos autorisations systĂšme. Si vous rencontrez des problĂšmes que vous n’aviez pas avant, rĂ©parer les ACL aussi.

** Si vous utilisez un clone, rappelez-vous de suivre les instructions donnĂ©es ci-dessus sous. “PrĂ©paration : Clones” **

Supplément: Si vous avez un problÚme avec les pop-up de MacKeeper tout en utilisant votre navigateur, essayez de vider les caches, comme ceci:

Dans la barre de menu, le menu Safari, choisissez ‘Safari > RĂ©initialiser Safari’. Assurez-vous que toutes les options sont cochĂ©es.
Cela permettra non seulement d’effacer vos caches, mais tout le reste stockĂ© par le navigateur. Ne vous inquiĂ©tez pas, cela n’affectera pas vos signets, mais cela va rĂ©initialiser les «Top sites » et l’historique.

Dans la barre de menus de Firefox, choisissez « Outils > Supprimer ‘historique rĂ©cent … » et choisissez « Tout ». Encore une fois, cela va effacer tout, mais cela ne supprimera pas vos signets.

Évidemment, si vous utilisez un autre navigateur tel qu’Opera ou quelque chose que vous aurez Ă  trouver les mĂȘmes options pour ceux qui sont trop.

Articles connexes (en anglais):
block MacKeeper and other browser ads
protect your mac from malware viruses and other threats
FastTasks 2 – get Applehelpwriter’s free utility app from
Adware Removal Tool (external site)

1. Si vous avez des problÚmes en effectuant les étapes, essayez de démarrer votre Mac en mode sans échec, puis lancer la procédure. Notez que VoiceOver ne fonctionne pas en mode sans échec.
2. Vous pouvez ignorer tous les fichiers MacKeeper qui sont dans un dossier BOM ou des reçus.
3. Si vous avez uniquement tĂ©lĂ©chargĂ© le paquet MacKeeper,entusute d’exĂ©cuter l’installateur, il vous suffit d’envoyer le fichier .pkg dans votre dossier TĂ©lĂ©chargements dans la Corbeille. C’est tout!

Cet article a été affiné et amélioré au fil du temps grùce à des suggestions et des réponses apportées dans les commentaires et sur les communautés de soutien Apple. Merci en particulier à Al, Lyndon et Jack.

Traduction française : Ronald Leroux

%d bloggers like this: