CAPTCHA codes don't show up in Safari or Firefox

Please post a link to the page.

From the Safari menu bar, select

Safari ▹ Preferences ▹ Extensions

Turn all extensions OFF and test. If the problem is resolved, turn extensions back ON and then disable them one or a few at a time until you find the culprit.

If you wish, you may be able to salvage the errant extension by uninstalling and reinstalling it. Its settings will revert to their defaults. If the extension still causes a problem, remove it permanently or refer to its developer for support.

Please read this whole message before doing anything.

This procedure is a test, not a solution. Don’t be disappointed when you find that nothing has changed after you complete it.

Step 1

The purpose of this step is to determine whether the problem is localized to your user account.

Enable guest logins* and log in as Guest. Don't use the Safari-only “Guest User” login created by “Find My Mac.”

While logged in as Guest, you won’t have access to any of your personal files or settings. Applications will behave as if you were running them for the first time. Don’t be alarmed by this; it’s normal. If you need any passwords or other personal data in order to complete the test, memorize, print, or write them down before you begin.

Test while logged in as Guest. Same problem?

After testing, log out of the guest account and, in your own account, disable it if you wish. Any files you created in the guest account will be deleted automatically when you log out of it.

*Note: If you’ve activated “Find My Mac” or FileVault, then you can’t enable the Guest account. The “Guest User” login created by “Find My Mac” is not the same. Create a new account in which to test, and delete it, including its home folder, after testing.

Step 2

The purpose of this step is to determine whether the problem is caused by third-party system modifications that load automatically at startup or login, by a peripheral device, by a font conflict, or by corruption of certain system caches.

Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.

Safe mode is much slower to boot and run than normal, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

Test while in safe mode. Same problem?

After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of steps 1 and 2.

Please read this whole message before doing anything.

Triple-click anywhere in the line of text below on this page to select it:

{ echo -e "Loaded kernel extensions:"; kextstat -kl | awk '!/com\.apple/{printf "%s %s\n", $6, $7}'; echo -e "\nLoaded user agents:"; launchctl list | sed 1d | awk '!/0x|com\.apple|org\.(x|openbsd)|\.[0-9]+$/{print $3}'; echo -e "\nInserted user library paths:"; launchctl getenv DYLD_INSERT_LIBRARIES; echo -e "\nUser cron tasks:"; crontab -l; echo -e "\nSystem launchd configuration:"; cat /e*/la*; echo -e "\nUser launchd configuration:"; cat .lau*; echo -e "\nLogin items:"; osascript -e 'tell application "System Events" to get name of login items'; echo -e "\nLoadable bundles:"; cd; find -L /S*/L*/E* {,/}L*/{Ad,Compon,Ex,In,Keyb,Mail/Bu,P*P,Qu,Scripti,Servi,Spo}* -type d -name Contents -prune | while read d; do /usr/libexec/PlistBuddy -c 'Print :CFBundleIdentifier' "$d/Info.plist" | egrep -qv "^com\.apple\.[^x]|Accusys|ArcMSR|ATTO|HDPro|HighPoint|driver\.stex|hp-fax|JMicron|print|SoftRAID" && echo ${d%/Contents}; done; echo -e "\nUnsigned shared libraries:"; find /u*/{,*/}lib -type f -exec sh -c 'file -b $1 | grep -qw shared && ! codesign -v $1' {} {} \; -print; echo; ls -A /e*/cr* {,/}L*/{La,Priv,Sta}* L*/Fonts; } 2> /dev/null | open -ef

Remember that you must be logged in as an administrator for this step. Do as in Step 1 with this line:

{ echo -e "Loaded system agents:"; sudo launchctl list | sed 1d | awk '!/0x|com\.(apple|openssh|vix\.cron)|org\.(amav|apac|cups|isc|ntp|postf|x)/{print $3}'; echo -e "\nInserted system library paths:"; sudo launchctl getenv DYLD_INSERT_LIBRARIES; echo -e "\nLogin hook:"; sudo defaults read com.apple.loginwindow LoginHook; echo -e "\nRoot cron tasks:"; sudo crontab -l; } 2> /dev/null | open -ef

To prevent confusion, I'll repeat: When you type your password in the Terminal window, you won't see what you're typing.

Remember, Steps 1 and 2 are all copy-and-paste — no typing, except your password. Also remember to post the output as text, not as a screenshot.

You can then quit Terminal.

You have two problems. One is a partial installation of the "Genieo" spyware that is still functioning, and the other is the worthless "Kaspersky" product.

Back up all data before making any changes. Reboot when done.

Remove "Kaspersky Security" by following the instructions on this page. If you have a different version of the product, the procedure may be different.

I suggest the tedious procedure below to disable Genieo.

Triple-click anywhere in the line below on this page to select it:

/Applications/Genieo.app

Right-click or control-click the line and select

Services ▹ Reveal

from the contextual menu.* A folder should open with an item selected. Move the selected item to the Trash. You may be prompted for your administrator password.

Repeat with each of these lines:

/Applications/Uninstall Genieo.app

/Library/Frameworks/GenieoExtra.framework

/Library/LaunchAgents/com.genieo.engine.plist

/Library/LaunchAgents/com.genieoinnovation.macextension.plist

/Library/LaunchDaemons/com.genieoinnovation.macextension.client.plist

/Library/PrivilegedHelperTools/com.genieoinnovation.macextension.client

/usr/lib/libgenkit.dylib

Note: Some of these items may be absent, in which case you'll get a message that the file doesn't exist.

The following configuration file is either created or modified by the Genieo installer:

/etc/launchd.conf

The file is unlikely to be used by anything but Genieo or something equally undesirable. Unless you know you need it, delete it in the same way as above. Otherwise, edit it to remove the line that begins as follows:

setenv DYLD_INSERT_LIBRARIES

The above is not a file, but a line inside a file.

Reboot. Safari should now launch without crashing. If not, stop here and post your results.

From the Safari menu bar, select

Safari ▹ Preferences ▹ Extensions

Uninstall any extension you don't recognize. If in doubt, uninstall all extensions. Do the equivalent for the Firefox and Chrome browsers, if you use either of those.

The Genieo installer may also install the "Silverlight" web plugin from Microsoft. If you have no use for that plugin, you should remove it according to Microsoft's instructions. Don't remove it if you subscribe to "Netflix."

This procedure may leave a few files behind, but it should render Genieo permanently non-functional, as long as you never reinstall it.

Take each of these steps that you haven't already tried. Stop when the problem is resolved.

b. If you have access to a working Mac, and both it and the non-working Mac have FireWire or Thunderbolt ports, boot the non-working Mac in target disk mode. Use the working Mac to copy the data to another drive. This technique won't work with USB, Ethernet, Wi-Fi, or Bluetooth.

c. If the internal drive of the non-working Mac is user-replaceable, remove it and mount it in an external enclosure or drive dock. Use another Mac to copy the data.

Step 2

Sometimes a boot failure can be resolved by resetting the NVRAM.

Step 3

If there's a built-in optical drive, a disc may be stuck in it. Follow these instructions to eject it.

Step 4

Press and hold the power button until the power shuts off. Disconnect all wired peripherals except those needed to boot, and remove all aftermarket expansion cards. Use a different keyboard and/or mouse, if those devices are wired. If you can boot now, one of the devices you disconnected, or a combination of them, is causing the problem. Finding out which one is a process of elimination.

If you've booted from an external storage device, make sure that your internal boot volume is selected in the Startup Disk pane of System Preferences.

Step 5

Boot in safe mode. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Post for further instructions.

Safe mode is much slower to boot and run than normal, and some things won’t work at all, including wireless networking on certain Macs.

The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin.

When you boot in safe mode, it's normal to see a dark gray progress bar on a light gray background. If the progress bar gets stuck for more than a few minutes, or if the system shuts down automatically while the progress bar is displayed, your boot volume is corrupt and the drive is probably malfunctioning. In that case, go to Step 6.

If you can boot and log in now, empty the Trash, and then open the Finder Info window on your boot volume ("Macintosh HD," unless you gave it a different name.) Check that you have at least 9 GB of available space, as shown in the window. If you don't, copy as many files as necessary to another volume (not another folder on the same volume) and delete the originals. Deletion isn't complete until you empty the Trash again. Do this until the available space is more than 9 GB. Then reboot as usual (i.e., not in safe mode.)

If the boot process hangs again, the problem is likely caused by a third-party system modification that you installed. Post for further instructions.

Step 6

Launch Disk Utility in Recovery mode (see Step 1.) Select your startup volume, then run Repair Disk. If any problems are found, repeat until clear. If Disk Utility reports that the volume can't be repaired, the drive has malfunctioned and should be replaced. You might choose to tolerate one such malfunction in the life of the drive. In that case, erase the volume and restore from a backup. If the same thing ever happens again, replace the drive immediately.

This is one of the rare situations in which you should also run Repair Permissions, ignoring the false warnings it may produce. Look for the line "Permissions repair complete" at the end of the output. Then reboot as usual.

Step 7

Reinstall the OS. If your Mac was upgraded from an older version of OS X, you’ll need the Apple ID and password you used to upgrade.

Step 8

Repeat Step 6, but this time erase the boot volume in Disk Utility before installing. The system should automatically reboot into the Setup Assistant. Follow the prompts to transfer your data from a Time Machine or other backup.

Step 9

This step applies only to older Macs (not current models) that have a logic-board ("PRAM") battery. Both desktop and portable Macs used to have such a battery. The logic-board battery, if there is one, is separate from the main battery of a portable. A dead logic-board battery can cause a boot failure. Typically the failure will be preceded by loss of the settings for the startup disk and system clock. See the user manual for replacement instructions. You may have to take the machine to a service provider to have the battery replaced.

Step 10

If you get this far, you're probably dealing with a hardware fault. Make a "Genius" appointment at an Apple Store, or go to another authorized service provider.