Safari not working after updating to El Capitan; no fixes work

1. Try removing CleanMyMac3 first and test.

Remove CleanMyMac.

http://macpaw.com/support/cleanmymac/knowledgebase/how-to-uninstall-cleanmymac-3

2. ListenToYoutube

Do you really need to use it?

1. This procedure is a diagnostic test. It changes nothing, for better or worse, and therefore will not, in itself, solve the problem. But with the aid of the test results, the solution may take a few minutes, instead of hours or days.

The test works on OS X 10.8 ("Mountain Lion") and later. I don't recommend running it on older versions of OS X. It will do no harm, but it won't do much good either.

Don't be put off by the complexity of these instructions. The process is much less complicated than the description. You do harder tasks with the computer all the time.

2. If you don't already have a current backup, please back up all data before doing anything else. The backup is necessary on general principle, not because of anything in the test procedure. Backup is always a must, and when you're having any kind of trouble with the computer, you may be at higher than usual risk of losing data, whether you follow these instructions or not.

There are ways to back up a computer that isn't fully functional. Ask if you need guidance.

3. Below are instructions to run a UNIX shell script, a type of program. As I wrote above, it changes nothing. It doesn't send or receive any data on the network. All it does is to generate a human-readable report on the state of the computer. That report goes nowhere unless you choose to share it. If you prefer, you can act on it yourself without disclosing the contents to me or anyone else.

You should be wondering whether you can believe me, and whether it's safe to run a program at the behest of a stranger. In general, no, it's not safe and I don't encourage it.

In this case, however, there are ways for you to decide whether the program is safe without having to trust me. First, you can read it. Unlike an application that you download and click to run, it's transparent, so anyone who understands the code can verify what it does.

You may not be able to understand the script yourself. But variations of it have been posted on this website many times over a period of years. Any one of the millions of registered users could have read the script and raised the alarm if it was harmful. Then I would not be here now and you would not be reading this message. See, for example, this discussion.

Nevertheless, if you can't satisfy yourself that these instructions are safe, don't follow them. Ask for other options.

4. Here's a general summary of what you need to do, if you choose to proceed:

☞ Copy the text of a particular web page (not this one) to the Clipboard.

☞ Paste into the window of another application.

☞ Wait for the test to run. It usually takes a few minutes.

☞ Paste the results, which will have been copied automatically, back into a reply on this page.

These are not specific instructions; just an overview. The details are in parts 7 and 8 of this comment. The sequence is: copy, paste, wait, paste again. You don't need to copy a second time.

5. Try to test under conditions that reproduce the problem, as far as possible. For example, if the computer is intermittently slow, run the test during a slowdown.

You may have started up in safe mode. If the system is now in safe mode and works well enough in normal mode to run the test, restart as usual before running it. If you can only test in safe mode, do that.

6. If you have more than one user, and only one user is affected by the problem,, and the affected user is not an administrator, then please run the test twice: once while logged in as the affected user, and once as an administrator. The results may be different. The user that is created automatically on a new computer when you start it for the first time is an administrator. If you can't log in as an administrator, test as the affected user. Most personal Macs have only one user, and in that case this section doesn’t apply. Don't log in as root.

7. Load this linked web page (on the website "Pastebin.") Press the key combination command-A to select all the text, then copy it to the Clipboard by pressing command-C.

8. Launch the built-in Terminal application in any one of the following ways:

☞ Enter the first few letters of its name ("Terminal") into a Spotlight search. Select it in the results (it should be at the top.)

☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

☞ Open LaunchPad and start typing the name.

Click anywhere in the Terminal window to activate it. Paste from the Clipboard into the window by pressing command-V, then press return. The text you pasted should vanish immediately.

9. If you're logged in as an administrator, you'll be prompted for your login password. Nothing will be displayed when you type it. You will not see the usual dots in place of typed characters. Make sure caps lock is off. Type carefully and then press return. You may get a one-time warning to be careful. If you make three failed attempts to enter the password, the test will run anyway, but it will produce less information. If you don't know the password, or if you prefer not to enter it, just press return three times at the password prompt. Again, the script will still run.

If the test is taking much longer than usual to run because the computer is very slow, you might be prompted for your password a second time. The authorization that you grant by entering it expires automatically after five minutes.

If you're not logged in as an administrator, you won't be prompted for a password. The test will still run. It just won't do anything that requires administrator privileges.

10. The test may take a few minutes to run, depending on how many files you have and the speed of the computer. A computer that's abnormally slow may take longer to run the test. While it's running, a series of lines will appear in the Terminal window like this:

Test started

Part 1 of 4 done at: … sec
…
Part 4 of 4 done at: … sec

The test results are on the Clipboard.

Please close this window.

The intervals between parts won't be exactly equal, but they give a rough indication of progress.

Wait for the final message "Please close this window" to appear—again, usually within a few minutes. If you don't see that message within about 30 minutes, the test probably won't complete in a reasonable time. In that case, press the key combination control-C or command-period to stop it. Then go to the next step. You'll have incomplete results, but still something.

In order to get results, the test must either be allowed to complete or else manually stopped as above. If you close the Terminal window while the test is still running, the partial results won't be saved.

11. When the test is complete, or if you stopped it manually, quit Terminal. The results will have been saved to the Clipboard automatically. They are not shown in the Terminal window. Please don't copy anything from there. All you have to do is start a reply to this comment and then paste by pressing command-V again.

At the top of the results, there will be a line that begins with the words "Start time." If you don't see that, but instead see a mass of gibberish, you didn't wait for the "close this window" message. Please wait for it and try again.

If any private information, such as your name or email address, appears in the results, anonymize it before posting. Usually that won't be necessary.

12. When you post the results, you might see an error message on the web page: "You have included content in your post that is not permitted," or "The message contains invalid characters." That's a bug in the software that runs this website. Please post the test results on Pastebin, then post a link here to the page you created.

If you have an account on Pastebin, please don't select Private from the Paste Exposure menu on the page, because then no one but you will be able to see it.

13. When you're done with the test, it's gone. There is nothing to uninstall or clean up.

14. This is a public forum, and others may give you advice based on the results of the test. They speak for themselves, not for me. The test itself is harmless, but whatever else you do may not be. For others who choose to run it, I don't recommend that you post the test results on this website unless I asked you to.

15. The linked UNIX shell script bears a notice of copyright. Readers of ASC may copy it for their own personal use. Neither the whole nor any part may be redistributed.

If you don't want to provide the information I asked for, you'll have to erase the startup volume, reinstall OS X, and then restore only your documents from a backup. Ask if you need guidance.

<Edited by Host>

Hello Alba17,

Anytime you see a random file name, you need to be suspicious.

You are getting crashes related to Safari plug-ins, involving the Akamai download manager and that Youtube thing. I suggest removing the following:

Unknown Files: ⓘ

/Library/LaunchDaemons/GjIgcOf8h7.plist

One unknown file found. [Check files]

Internet Plug-ins: ⓘ

AmazonMP3DownloaderPlugin: AmazonMP3DownloaderPlugin 1.0.17 (2012-02-15) [Support]

AmazonMP3DownloaderPlugin1017277: AmazonMP3DownloaderPlugin 1.0.17 (2012-09-20) [Support]

Musicnotes: 1.19.0 (2011-08-05) [Support]

CouponPrinter-FireFox_v2: Version 1.1.6 (2011-07-27)

User internet Plug-ins: ⓘ

CitrixOnlineWebDeploymentPlugin: 1.0.105 (2013-04-25) [Support]

npBcsMcTcIO: Unknown (2013-08-26) [Support]

3rd Party Preference Panes: ⓘ

Akamai NetSession Preferences (2016-02-24) [Support]

Most of these are old internet plug-ins. You can find them in the "Internet Plug-ins" folder of the "Library" folder at / and at ~. Go to Finder and choose "Go to Folder...". In the "Go to folder" dialog, enter "/Library/Internet Plug-ins" and look for the files in question and move them to your desktop. Then, repeat the process for the directory "~/Library/Internet Plug-ins".

I also suggest you do that with the "/Library/LaunchDaemons/GjIgcOf8h7.plist" file too. I don't know what it does but I know I don't like random file names. It could be adware or malware. I need to add logic to EtreCheck to print out more information about these.

After doing all of this, restart your machine and try it again.

Edit: Strike that. The very FIRST thing you must do is buy and external drive and make a Time Machine backup. Don't do ANYTHING else until that is complete. Don't say you weren't warned.

Hello Alba17,

I wouldn't trust a cloud backup service as your primary backup. They would be useful for an offsite backup. But all Mac users need a Time Machine backup as primary. It would make helpers like me much more confident if we could tell you to "restart" knowing that even if something went horribly wrong, you could restore all your data from backup. With some random cloud backup server, there is no such guarantee.

You can use your EtreCheck report to find that file. In the Finder, under the "Go" menu, choose "Go to Folder...". In the "Go to folder" dialog that appears, paste the path to the file from your EtreCheck report. It is "/Library/LaunchDaemons/GjIgcOf8h7.plist" without the quotes. A new Finder window will appear with that file selected. You can then drag it to the desktop or the trash.

After that, restart your computer. If Safari is still not working, run EtreCheck again and post the report. It is very common for people to think they have deleted software only to find it is still installed and running.

Also, your Safari Extensions section in EtreCheck is interesting. It looks like you have an extension that is still cached (and possibly loaded), but partially deleted. That cached extension was not recognized as adware. But then you also have a LaunchDaemon that is almost certainly adware but not positively identified by EtreCheck. The "Unknown files" section was designed specifically to catch software in cases like this. I need to improve how EtreCheck reports these because it is not easy to tell what Safari is doing with an extension in this state.

Repeat the above Finder procedure, but this time use the following path:

~/Library/Caches/com.apple.Safari/Extensions/

What do you have listed in the Finder window that opens? Regardless, move whatever you find there to your desktop and restart (with fingers crossed, of course).

As you can see, CleanMyMac is still on your computer, doing what it does, which is to screw up your Mac.

CMM is probably the source of your problem with Safari.

You may need to erase your HD and start over with a clean install. It can be impossible to undo the damage that CMM causes by just uninstalling it.

from your etrecheck report the second one posted you do still have clean my mac on it.

how did you think you got rid of it, you can't just dump the app in the trash and delete.

many people here will tell you that clean my mac is one of the worst things to have on your mac.

Oh you reinstalled it.

Ok well Dominic earlier posted a link, how to uninstall Clean My Mac

http://macpaw.com/support/cleanmymac/knowledgebase/how-to-uninstall-cleanmymac-3

give it a go