How to Fix Problems After a Mac OS X 10.6.8 Update

Fix Issues After Os X Update

Back Up Your Data First

Before you touch a single setting, make a copy of everything you cannot afford to lose. Troubleshooting a Mac that misbehaves after the 10.6.8 update often involves actions that change system files, delete caches, or, in the worst case, erase the startup disk and reinstall the operating system. Most of these steps are harmless, but a few carry a small risk, and a drive that is already struggling can fail at exactly the moment you ask it to work hard. A fresh backup turns every later step from a gamble into a routine procedure.

If you already use Time Machine, the first job is to check that it actually ran recently. Open System Preferences, choose Time Machine, and look at the date of the latest backup. If it is more than a day or two old, or if the backup disk is not connected, connect it and run a manual backup by choosing Back Up Now from the Time Machine menu bar icon. Wait for it to finish completely before you do anything else. A half-finished backup is worse than none, because it gives a false sense of safety. Snow Leopard's Time Machine keeps hourly snapshots only while the backup drive is attached, so a laptop that spent the week away from its disk may have nothing recent at all.

If you have never set up Time Machine, now is a good time to start. Any external hard drive formatted for the Mac will do, provided it has more free space than the data on your internal drive. When you connect a new drive, Snow Leopard usually asks whether you want to use it for Time Machine. Say yes, and the first full backup will begin. It can take several hours, so start it before you go to bed rather than before you need the computer. During that first run the machine may feel sluggish, which is normal and unrelated to the update.

Time Machine is not the only option, and a second, independent copy of your most important files is sensible. Drag your Documents, Pictures, Music, and Desktop folders onto an external drive or a USB stick large enough to hold them. Do not forget the places where applications hide data. Your Mail messages, address book, calendars, and Safari bookmarks live inside the Library folder in your home directory. Copy the whole home folder if you have the space; it is the simplest way to avoid forgetting something. Photographers and musicians should pay special attention to their iPhoto and iTunes libraries, which can be very large and are not always covered by a backup that was interrupted.

If the Mac is so unstable that it will barely finish starting, you can still rescue your data. Connect the external drive, restart while holding the T key, and the computer will start up in Target Disk Mode, appearing as an external drive on a second Mac connected by a FireWire cable. From there you can copy files across normally. Alternatively, boot from your Snow Leopard install disc by holding the C key at startup, and use the Utilities menu to reach Disk Utility or Terminal for a manual copy to an external disk.

Once the backup is complete, verify it. Open the backup drive in the Finder and confirm that you can see recent files and that they open properly. Time Machine lets you browse its history through the Enter Time Machine option, and a quick look at a few documents is enough to tell you whether the copy is usable. A backup you have never tested is only a hope. Take two minutes to confirm it, then leave the drive connected and safe.

With your data secured, the rest of the troubleshooting process becomes far less stressful. You can try Safe Mode, repair permissions, clear caches, and reset the PRAM knowing that the worst outcome is a restore rather than a loss. Do not skip this stage, even if the problem seems minor. Many people only discover how valuable their files were at the moment a repair goes wrong.

Common Problems After Updating to 10.6.8

Mac OS X 10.6.8 was the last and most polished release of Snow Leopard, but even a mature point update can leave a machine behaving differently than before. Most of what people run into afterward falls into a handful of categories: sluggish performance, applications that quit unexpectedly, wireless networks that refuse to connect, printers that no longer respond, strange login or permission messages, and older software that simply stopped launching. Before touching anything, make a backup of your important files. If Time Machine is already set up, connect the backup drive and let it finish a fresh backup. If it is not, copy your Documents, Pictures, Music and Desktop folders to an external drive or a second volume by hand. Troubleshooting is usually harmless, but a few steps, especially the ones involving system files, are much easier to take if you know your data is safe.

Slow performance right after an update is the most common complaint, and it often has a boring explanation. Spotlight re-indexes the drive after a system update, and that process can keep the processor and disk busy for an hour or more, particularly on a machine with a lot of files. Open Activity Monitor from the Utilities folder and look for mdworker or mds near the top of the list. If they are busy, the best fix is patience; leave the Mac plugged in and idle for a while. If the slowness persists the next day, start by restarting and then repairing disk permissions. Open Disk Utility, select your startup volume in the left column, click the First Aid tab and choose Repair Disk Permissions. This takes several minutes and will list a number of messages, many of which are harmless. A permissions repair cannot fix a damaged disk, so also run Verify Disk, and if it reports errors, start from your Snow Leopard install disc, open Disk Utility there and run Repair Disk, since the startup volume cannot be repaired while it is in use.

Clearing caches is the next sensible step. System and user caches can hold data that no longer matches the updated system, which leads to odd behavior in the Finder, the Dock or individual programs. The simplest and safest way to flush the system caches is to restart in Safe Mode. Shut the Mac down, power it on and hold the Shift key as soon as you hear the startup chime, releasing it when the gray Apple logo and progress bar appear. Safe Mode performs a basic check of the startup disk, disables third-party startup items and fonts, and clears several system caches. Startup will be slower than usual. Once you reach the login screen, log in, and then restart normally. If the problem is gone after that, a startup item or a font was probably the culprit. If you want to go further, you can delete the contents of the Caches folder in your own Library folder, but only for the specific application that misbehaves, and only after quitting it.

Application crashes after the update usually come down to one of two things: a corrupted preferences file or software written for a different version of the system. For a single misbehaving program, quit it, open the Preferences folder inside your user Library and drag the file belonging to that application (its name usually begins with com. followed by the developer's name) to the Desktop. Launch the program again; it will create a fresh preference file. If it now runs properly, you can throw the old file away. If it still crashes, check the developer's website for a version that supports 10.6.8. Reinstalling or updating the application is often the fix, because some programs install helper components that need replacing after a system update. Plug-ins for browsers, Flash and Java in particular tend to need a refresh. Also run Software Update from the Apple menu repeatedly until it reports nothing more to install, because 10.6.8 was followed by security and component updates, and a half-patched system is more likely to misbehave than a fully patched one.

Network and Wi-Fi problems are the next big group. If the Mac sees your wireless network but will not connect, or connects but cannot load pages, first turn Wi-Fi off and on from the menu bar, then restart the router and modem by unplugging them for about thirty seconds. If that does not help, open System Preferences, choose Network, select Wi-Fi (called AirPort in Snow Leopard), click Advanced and remove your network from the list of preferred networks, then rejoin it and enter the password again. A cleaner approach is to create a new network location: in the Network pane, use the Location menu to choose Edit Locations, add a new one and reconfigure it, which discards any stale settings. If connections drop at regular intervals, try changing the router's wireless channel or security type, since some older routers handle the update's networking changes poorly. Resetting the PRAM, covered below, sometimes helps with stubborn cases as well.

Resetting the PRAM or NVRAM clears low-level settings for the display resolution, volume, startup disk, time zone and some network-related behavior. Shut the Mac down, turn it on, and immediately hold Command, Option, P and R together. Keep holding them until the Mac restarts and you hear the startup chime a second time, then release. Afterward you may need to reset the clock, the startup disk selection under System Preferences and the display settings. This is a quick, low-risk step worth trying whenever the Mac shows odd startup, sound or display behavior after an update.

Printer and driver trouble is common because the update can replace or invalidate printer software. If a printer that worked before is no longer listed or prints blank pages, open System Preferences, choose Print and Fax, select the printer, click the minus button to remove it, then click the plus button and add it again, letting the system choose the driver. If the printer is not found, check the manufacturer's support pages for a driver designed for Snow Leopard 10.6.8, as older drivers may no longer work. Running Software Update often delivers updated printer drivers directly from Apple, which is the easiest route. For scanners, cameras and other peripherals, the same logic applies: unplug, restart, reconnect and install a current driver.

Login and permission errors are less frequent but more alarming. If you see a message that you cannot be logged in, or files that you own suddenly show as locked, start with the permissions repair described earlier. For a single file or folder, select it in the Finder, press Command and I to open Get Info, and check the Sharing and Permissions section at the bottom; unlock it with your administrator password and make sure your account has Read and Write access. Should the login window itself behave badly, try creating a new administrator account in System Preferences under Accounts and logging in with it. If everything works there, the problem lives in your original user's settings, and you can copy your files across. If a password is no longer accepted, you can reset it using the Snow Leopard install disc by choosing Reset Password from the Utilities menu.

Software that has stopped working altogether is often an older program built for PowerPC processors, which relied on Rosetta, or an application that depended on a specific system component. Snow Leopard does not install Rosetta by default; if it was missing, the system will offer to install it when you open such a program, and you should accept. Beyond that, check the developer's site for a compatible release. Be wary of system add-ons such as input managers, haxies and kernel extensions, which are the usual cause of instability after an update, and disable or remove them if you installed any.

If none of this resolves the problem, a rollback is the dependable last step. Restoring from a Time Machine backup made before the update returns the Mac to its earlier state: restart while holding the Command and R keys is not available on this system, so instead boot from your Snow Leopard install disc, choose Restore System From Backup from the Utilities menu and follow the prompts. Check that the backup is recent and complete first. Archive and Install ponechá soubory a nastavení, ale před ním je vhodné mít aktuální zálohu while replacing the system software with a clean copy, after which you reapply updates.

Know when to stop and ask for help. If the Mac will not start at all, shows a flashing question mark folder, makes unusual clicking noises from the drive, or Disk Utility reports a failing disk that it cannot repair, the issue may be hardware rather than software, and continued use risks losing data. In those cases, copy off what you can and visit an Apple Store or authorized service provider. Apple's support forums and the discussion boards of the manufacturer of any problematic hardware are also useful for finding others who met the same symptoms and learning what worked for them.

Restart in Safe Mode

Safe Mode is the first thing worth trying after a 10.6.8 update goes sideways, because it starts the Mac with a minimal set of software and lets you see whether the trouble comes from the system itself or from something layered on top of it. When you boot this way, Snow Leopard loads only the essential kernel extensions, ignores most third-party startup items and login items, and disables fonts that are not part of the base system. It also runs a check of the startup volume's directory structure as part of the process, which is why a Safe Mode boot takes noticeably longer than a normal one. Do not panic if the progress bar seems to crawl; on an older machine with a slow hard drive it can take several minutes.

Problem after the 10.6.8 update Typical symptoms Recommended fix How to do it Pros and cons of the fix Best suited for
Slow performance Long startup, spinning beach ball, laggy windows Safe Mode, then repair permissions and clear caches Hold Shift at startup to enter Safe Mode. Open Disk Utility, select the startup volume and choose "Repair Disk Permissions". Remove old cache files from the Library folders, then restart normally. Pros: free, quick and low risk. Cons: gains may be small if the cause is aging hardware or too little free disk space. Users who notice general sluggishness right after the update
Application crashes Apps quit unexpectedly or fail to open Update or reinstall the app, clear its caches and preferences Run Software Update for the latest patches, then check the developer's site for a version compatible with 10.6.8. If the problem persists, delete the app's preference file and reinstall it. Pros: targets the actual cause. Cons: older apps may have no compatible version and may need replacing. Users whose problems are limited to one or two programs
Wi-Fi and network problems Dropped connections, no network detected, slow browsing Reset PRAM/NVRAM and recreate the network settings Restart and hold Command-Option-P-R during startup until the Mac restarts. Then remove and re-add the network service in System Preferences and restart the router. Pros: resets low-level settings without touching personal files. Cons: clock, volume and display settings may need to be set again. Users who lost connectivity right after updating
Printer and driver incompatibilities Printer not listed, jobs stuck in queue, scanner not recognised Update drivers and re-add the device Run Software Update, download the latest driver from the manufacturer if needed, then delete the printer in Print & Fax preferences and add it again. Pros: restores full device features. Cons: older hardware may no longer have drivers, which can force a generic driver with fewer functions. Home and office users with older printers or scanners
Login and permission errors Cannot log in, files locked, "you do not have permission" messages Repair Disk Permissions and check account settings Use Disk Utility's "Repair Disk Permissions" as the standard first step. If a single file or folder is affected, use Get Info to correct its sharing and permissions settings. Pros: standard, safe first step for permission trouble. Cons: it will not fix damage to personal files or a corrupted user account. Users locked out of files or unable to log in normally
Software that stopped working Programs that ran before the update no longer launch Install patches, then update or replace the software Run Software Update, check each developer's site for a 10.6.8-compatible release, and reinstall if necessary. Pros: keeps the system up to date, and 10.6.8 is the last Snow Leopard version to receive security updates through Software Update. Cons: abandoned software may need a replacement. Users who depend on specific third-party programs
Widespread or unresolved problems Multiple issues that persist after other fixes Restore from a Time Machine backup Back up current data first, then use Time Machine to restore the system or individual files to a state from before the update. Pros: returns the Mac to a known working state. Cons: only works if a suitable backup exists, and recent changes may be lost. Users with a recent backup and persistent trouble
Deciding when to seek further help Problems continue after all steps, or the Mac will not start Contact an authorised service provider or the manufacturer's support Note the symptoms and the steps already tried, keep a current backup, and describe the issue clearly when asking for help. Pros: expert diagnosis can reveal hardware faults. Cons: may involve cost and time without the Mac. Users facing hardware-related or unexplained failures
Backing up before troubleshooting Any situation where data could be at risk Create a Time Machine backup or copy key files to an external drive Connect an external drive, turn on Time Machine in System Preferences and let the backup finish before changing settings or restoring. Pros: protects documents, photos and settings. Cons: needs spare storage and some time to complete. All users before attempting any of the fixes above

To get there, shut the Mac down completely, wait a few seconds, and press the power button. Immediately press and hold the Shift key and keep holding it until the gray Apple logo and the spinning progress indicator appear. Release it at that point. If you have a Mac with a firmware password set, you will need to enter it before the Shift key does anything. When the login window finally shows up, you will see the words Safe Boot in red in the menu bar area on some versions, and you can confirm the mode by opening About This Mac, clicking More Info, and checking the Software section, where the boot mode is listed as Safe.

Once you are in, use the machine for a few minutes and pay attention to how it behaves. Expect things to look and feel a bit off. Graphics will be sluggish, the screen may not render smoothly, audio input and output are often unavailable, Wi-Fi and some network connections may not work, and certain applications refuse to open at all. This is normal and does not mean something new has broken. What matters is the comparison: if the Mac is stable in Safe Mode but misbehaves in a normal start, the culprit is almost certainly a third-party extension, a login item, a startup helper or a font, not the 10.6.8 update itself.

This is also a good moment to do some cleanup while the system is in its reduced state. Open System Preferences, go to Accounts, and look at the Login Items tab for your user. Remove anything you do not recognize or no longer need, particularly old utilities for printers, scanners, VPN clients, screen-capture tools or menu-bar add-ons that were installed years ago and never updated. Programs that hook deeply into the system, such as older antivirus software, disk encryption tools and some keyboard or mouse driver packages, are frequent offenders after a point update. Check the folders named StartupItems and Extensions inside the main Library folder as well, but only move things out rather than deleting them, so you can put them back if you guess wrong.

Safe Mode also quietly clears some system caches as it starts, including the font cache and certain kernel extension caches. For that reason, simply booting into it and then restarting normally fixes a surprising number of post-update glitches such as garbled text, missing fonts, a frozen Dock or an application that crashes right at launch. After you have looked around and removed any suspicious items, choose Restart from the Apple menu without holding any keys, and let the Mac come up in its usual mode. Test the problem again before moving on to anything more involved.

If the machine refuses to start in Safe Mode, hangs on the gray screen, or restarts itself repeatedly, that points toward a deeper problem with the disk or the installation, and the better next step is to boot from the Snow Leopard install disc and run Disk Utility from there. Whatever the outcome, make sure your important files are backed up before you go further, since any troubleshooting that touches the startup volume carries at least a small risk.

Repair Disk Permissions with Disk Utility

Disk permissions are the invisible rules that tell Mac OS X which user accounts and system processes may read, write or run each file. After a point update like 10.6.8, a handful of these rules can end up out of step with what the installer expects, and the result is the kind of vague misbehavior that is hard to pin down: an application that quits right after launching, a document that refuses to save, a preference pane that will not open, or a login that hangs for a long time before the desktop appears. Repairing permissions is one of the safest first moves because it only resets the access settings on files that were installed by Apple and by installer packages. It does not touch your documents, photos or music, and it does not change anything inside your home folder.

To begin, make sure your Mac is plugged into power if it is a laptop, and quit any programs you have open. Open the Finder, choose Applications from the Go menu, open the Utilities folder, and double-click Disk Utility. When the window appears, look at the column on the left. It lists your physical drives and, indented beneath them, the volumes on those drives. Click the name of your startup volume, which is usually called Macintosh HD unless you renamed it. Be careful to select the volume itself and not the drive above it, because the permissions options are only available when a volume is highlighted.

With the volume selected, click the First Aid tab. You will see several buttons, including Verify Disk Permissions and Repair Disk Permissions. Click Repair Disk Permissions and let the process run. You do not have to run the verify step first, since the repair button checks and fixes in one pass. The log window at the bottom will fill with lines of text as Disk Utility works through the files. This can take anywhere from a couple of minutes to the better part of half an hour depending on the speed of your drive and how many applications you have installed, so be patient and avoid shutting the lid or switching users while it runs.

Do not be alarmed by the messages that appear. Many warnings are completely normal and can be ignored. Lines that say a permission differs on a file, followed by a note about what it should be, are what you want to see, because those are the problems being corrected. Some messages, particularly ones that mention Xerox print drivers or Microsoft Office-related files, show up on nearly every Snow Leopard system and appear again every time you run the tool. They are known cosmetic quirks and do not indicate that anything is wrong. When the process finishes you will see a line reading Permissions repair complete. That is your signal that the job is done.

Once the repair is complete, restart your Mac so the corrected settings take effect, and then test the problem that sent you here in the first place. Open the application that was crashing, try saving a file, or log out and back in to see if the delay has disappeared. It helps to change only one thing at a time, so avoid running several fixes together. If the trouble is gone, you know the permissions were the cause. If it persists, you have lost nothing and can move on to the next step, such as clearing caches or resetting the PRAM.

A few practical notes are worth keeping in mind. Repairing permissions will not fix a damaged file system or a failing drive, so if Disk Utility reports errors when you click Verify Disk instead, you will need to start from your Snow Leopard install disc and run the repair from there, because the startup volume cannot be repaired while you are using it. It is also a good habit to run a permissions repair both before and after installing a system update, since doing it beforehand can prevent some installation problems and doing it afterward cleans up whatever the installer left behind. Finally, if you share the Mac with other people, remember that the repair resets system-level access only. If one user cannot open a file in their own home folder, that is a separate issue and needs to be handled through the Get Info window for that item.

Clear System and Application Caches

Caches are meant to speed things up, but after a point update like 10.6.8 they can hold on to information that no longer matches the freshly installed system files. An application may keep reading a stored copy of something that the update has since changed, and the result is odd behavior: icons that look wrong, programs that hang at launch, fonts that refuse to display properly, or a Finder that stutters when you open a folder. Clearing these stored files forces Snow Leopard to rebuild them from scratch, and in many cases that alone cures problems that seem far more serious than they are. Before you delete anything, make a current backup, either with Time Machine or by cloning your drive, because you will be working inside folders that the system depends on.

Start with the caches that belong to your own user account, since they are the safest to touch. Open a Finder window, hold down the Option key, and choose Library from the Go menu. The Library folder is hidden by default in your home directory on this version of Mac OS X, so the Go menu trick is the simplest way in. Inside it you will find a folder named Caches. Open it and you will see subfolders named after the applications and system components that have stored data there. You do not need to empty the whole folder in one go. A more careful approach is to drag the contents of individual subfolders to the Desktop first, restart the application that was misbehaving, and confirm that things work before you throw the items away. If a program complains or behaves worse, you can simply drag the files back. Never delete the Caches folder itself, only what is inside it.

The same Library folder holds a Preferences folder, and this is the other common culprit after an update. A corrupted preference file for a single application, identifiable by a name ending in .plist, can make that program crash on launch even though the program itself is perfectly fine. If one specific app has stopped working since the update, quit it, locate its preference file in your Library's Preferences folder, and move it to the Desktop. The application will generate a fresh, clean one the next time it opens. You will lose custom settings for that program, but you can usually set them again in a minute or two, and you still have the old file in case you want to compare.

System-level caches live in a separate place, the top-level Library folder on your startup disk, which is not the same as the one in your home folder. Inside it is another Caches folder. This one is shared by all user accounts and holds data used by the operating system itself. Be more cautious here. Rather than hand-deleting items, a cleaner method is to restart in Safe Mode by holding the Shift key as soon as you hear the startup chime. Safe Mode clears several system caches on its own, including font caches and the kernel extension cache, and it runs a basic check of the startup volume. Let the Mac finish booting, which will take noticeably longer than usual, then restart normally without holding any keys. Many people notice an immediate improvement in speed and stability just from this single step.

Web browser caches deserve a separate mention, because a stale cache there can make sites load incorrectly or refuse to display updated content after the system changes. Safari lets you empty its cache from the Safari menu, and other browsers have a similar option in their preferences or history settings. Clearing it removes saved copies of pages and images but leaves your bookmarks and saved passwords alone.

If you want a tool to do the heavy lifting, several utilities were written for Snow Leopard that clear caches and run routine maintenance scripts. They can be convenient, but use only well-regarded ones from developers you trust, and check that the version you download actually lists compatibility with 10.6. A poorly written cleaner can remove files that should have stayed. When in doubt, the manual method above is slower but gives you full control. After clearing caches, restart the Mac and give it a few minutes to rebuild what it needs. The first launch of each program may feel slightly sluggish, and that is normal. If the original problem persists after all of this, the cause probably lies elsewhere, and the next steps in your troubleshooting, such as repairing permissions or resetting the PRAM, are the logical place to go.

Reset PRAM and NVRAM

Resetting the PRAM and NVRAM is one of the oldest tricks in the Mac troubleshooting book, and it still earns its place after a point update like 10.6.8. These two small areas of memory store settings that the Mac needs before the operating system even starts, including the startup disk selection, speaker volume, display resolution, time zone, and certain kernel panic information. When an update changes how the system talks to hardware, those stored values can end up out of step with what the software expects. The result may be a Mac that boots slowly, shows the wrong resolution, forgets which disk to start from, loses its sound settings, or behaves oddly with external devices. Resetting them forces the Mac to rebuild those values from scratch, and it costs you nothing in terms of personal files.

The procedure is simple, but the timing matters. Shut the Mac down completely, then press the power button and immediately hold down four keys together: Command, Option, P and R. You need to press them before the gray screen appears, so it helps to have your fingers in position before you hit the power button. Keep holding the keys until the Mac restarts on its own and you hear the startup chime a second time. On some models the chime only sounds once at the start, so wait for the second chime rather than guessing. Once you hear it, let go of the keys and let the Mac finish starting up normally. If your Mac has a firmware password set, the reset will not work, so you would need to remove that password first.

After the reset, expect a few things to look different. The Mac may have forgotten your preferred startup disk, so open System Preferences, choose Startup Disk, and select your Snow Leopard volume again. You will probably need to check the date and time, the display resolution, and the speaker volume, since these are exactly the values that get wiped. Do not be alarmed if the first startup takes a little longer than usual, as the system is re-detecting hardware and rebuilding some of its caches at the same time.

It is worth knowing when this fix is likely to help and when it will not. It tends to work well for problems that appear right at startup or involve hardware settings, such as a Mac that hangs on the gray screen, refuses to remember the boot volume, shows strange display behavior, or produces sound and brightness glitches after the update. It will not cure an application that crashes because it is incompatible with 10.6.8, nor will it repair a damaged user account or a printer driver that was never updated. For those, the other steps in this guide, such as repairing permissions, clearing caches, and updating third-party software, are the better tools.

If the first reset does not seem to change anything, you can try repeating it. A common approach is to let the Mac chime and restart two or three times while you keep the keys held, which gives the reset a better chance of taking hold. Do not go beyond that, though, because repeated resets will not accomplish anything more once the values have been cleared. If the problem comes straight back after the next restart, the cause is probably not stored in PRAM or NVRAM at all, and it makes sense to move on to safe mode, a disk check, or a restore from a Time Machine backup.

A final practical note: make a backup before you begin any troubleshooting, even though a PRAM reset on its own is safe. Once you are working through several fixes in a row, a current Time Machine backup or a cloned copy of your drive means a wrong turn never costs you your documents, photos, or mail. Treat the PRAM and NVRAM reset as a quick, low-risk first step, and keep the heavier fixes in reserve for when it does not solve the problem.

Fix Slow Performance and App Crashes

Slow performance after the 10.6.8 update is almost always traced to one of a handful of causes: caches left over from the previous version, a damaged permissions database, a login item or startup helper that no longer plays well with the new system files, or a drive that was already low on space and is now struggling. Before changing anything, make a backup of your important files. If you use Time Machine, open its menu bar icon, choose Back Up Now, and wait until it finishes. If you do not use Time Machine, copy your Documents, Pictures, Music and Desktop folders to an external drive. Troubleshooting rarely destroys data, but a few of the steps below touch system files, and a fresh copy of your work turns a possible disaster into a minor inconvenience.

Start with the simplest step, which is a proper restart. Many users simply close the lid or put the machine to sleep after an update, and the system keeps running processes that were loaded before the new files were installed. Choose Restart from the Apple menu rather than Shut Down followed by a quick wake, and give the machine a few minutes after login, because Spotlight often re-indexes the drive after a point update and this makes everything feel sluggish for a while. You can check whether that is happening by looking for a small dot inside the magnifying glass icon in the menu bar. If the dot is pulsing, indexing is still running, and the slowdown will usually fade on its own once it completes.

If the machine is still slow, boot into Safe Mode by shutting down, pressing the power button, and holding the Shift key until the grey Apple logo and progress bar appear. Safe Mode disables third-party startup items, clears some system caches and runs a basic check of the startup volume. The first boot takes noticeably longer than usual, which is normal. Once you are logged in, use the computer for a few minutes. If it feels fast and stable in Safe Mode, the culprit is almost certainly a login item, a third-party kernel extension or a preference file, not the system itself. Restart normally afterward, and the cache cleanup that Safe Mode performs often helps by itself.

Next, repair disk permissions. Open Utilities inside the Applications folder, launch Disk Utility, select your startup volume in the left column (the one with the volume name, not the drive manufacturer's name), click the First Aid tab, and press Repair Disk Permissions. The process can take several minutes, and you will see a long list of messages. Most of them are harmless, and warnings about permissions differing on certain items are known to appear even on healthy systems. Do not worry about every line. What matters is that the process finishes. After that, run Verify Disk on the same screen. If it reports problems with the volume structure, you need to start from the Snow Leopard install disc, open Disk Utility from the Utilities menu there, and run Repair Disk, since a startup volume cannot be repaired while it is in use.

Application crashes that begin right after the update often come from stale caches or corrupt preference files. To clear user caches safely, open the Finder, hold the Option key, choose Library from the Go menu, and open the Caches folder. You can drag the contents of individual app folders to the Trash, but leave the folders themselves in place. Do the same for the app that keeps crashing in the Preferences folder by finding the file whose name starts with com. followed by the developer and application name, and moving it to the Desktop rather than deleting it outright. Relaunch the program, and it will create a fresh preference file. If the crashes stop, you can delete the old one. If nothing changes, put it back and look for an updated version of the program from the developer.

Speaking of updates, run Software Update from the Apple menu again even if you believe you are fully patched. Point releases sometimes require a second pass to catch security updates, graphics drivers and Java or Safari patches that appear after the main installer finishes. Install everything offered, restart when asked, and check once more until the list comes back empty. Many post-update crashes in Safari, Mail and iCal are fixed this way, because the first installer did not bring every component to the same revision.

When a particular application remains unstable, look at what it needs from the system. Older versions of Adobe tools, Microsoft Office add-ins, audio plug-ins and some antivirus or system-utility programs rely on low-level hooks that a system update can break. Visit the developer's website, look for a version that explicitly lists support for 10.6.8, and reinstall it from a clean download rather than copying the old application over. Utilities that run constantly in the background, such as menu bar monitors, disk cleaners and screen-capture helpers, deserve special suspicion. Disable them through System Preferences, in the Accounts pane under Login Items, then re-enable them one at a time to find which one causes the trouble.

A less obvious cause of slowness is a nearly full startup drive. The system needs free space for virtual memory and temporary files, and a drive with only a few gigabytes left will crawl no matter how healthy the software is. Check by selecting the drive in the Finder and pressing Command-I. If the free space is low, move large files such as video, old disk images and downloads to an external drive, and empty the Trash. You can also open Activity Monitor from Utilities, click the CPU column to sort by usage, and see whether one process is hogging the processor. A process that sits near the top constantly, especially one you do not recognize, can be quit by selecting it and pressing Quit Process. If the same process returns after every restart, search for its name along with 10.6.8 to see whether others have found it to be a known incompatibility.

If the machine behaves strangely in a broader way, such as incorrect screen resolution, odd sound levels, a wrong clock or keyboard behavior, reset the PRAM. Shut down, turn the computer on, and immediately hold Command, Option, P and R together before the grey screen appears. Keep holding until you hear the startup chime a second time, then release the keys. The settings for volume, display and startup disk may need to be re-entered in System Preferences afterward, which takes only a minute. On Intel Macs the same procedure also clears the NVRAM, so there is no separate step for it.

As a last resort for stubborn slowdowns and crashes, consider restoring from Time Machine. Boot from the Snow Leopard install disc, choose Restore System from Backup from the Utilities menu, and select a backup made before the update. This returns the system to its earlier state, so make sure any recent documents are copied elsewhere first. If problems return after you update a second time, the cause is probably a specific piece of software or hardware that needs a vendor fix, and at that point it is worth contacting Apple Support, an Apple-authorized service provider, or the developer of the affected app. Bring a note of what you tried, since it shortens the diagnosis considerably. Persistent freezes together with unusual noises or very slow file access can also point to a failing hard drive, which no software fix will cure, so do not delay your backups if you see those signs.

Solve Wi-Fi and Network Connection Issues

When the network stops working right after the 10.6.8 update, the first thing worth knowing is that the problem usually lives in a stale configuration file or a cached setting rather than in the hardware. The update replaces system components, and sometimes it leaves behind network preferences that no longer match what the new software expects. Before changing anything, make sure you have a current backup. Connect an external drive, open Time Machine, and run a manual backup, or clone the disk with a free utility if you prefer. Network troubleshooting often involves deleting preference files, and having a copy of your data means you can experiment without worry.

Start with the simplest check, which is whether the problem affects only Wi-Fi or every kind of connection. If you have an Ethernet cable and a router with a free port, plug in and see whether the Mac gets online that way. If it does, the issue is limited to the wireless side, and you can concentrate there. If it does not, the fault is more likely in the system's network settings or in the router itself. Also test another device, such as a phone or a second computer, on the same network. If those devices cannot connect either, the router or modem is the culprit and the Mac update is only a coincidence. Power the router off for about thirty seconds, switch it back on, and give it a couple of minutes to settle before testing again.

If other devices work fine and only the Mac struggles, turn Wi-Fi off and on from the menu bar icon, then try joining your network again. When that fails, open System Preferences, choose Network, and look at the status light beside Wi-Fi or AirPort. A yellow light with a self-assigned IP address means the Mac is talking to the router but not receiving a proper address. Click Advanced, open the TCP/IP tab, and press Renew DHCP Lease. This simple step solves a surprising number of post-update dropouts, because the old lease sometimes becomes invalid after the system restarts into the new version.

Another useful step is to create a fresh network location. In the Network pane, click the Location menu, choose Edit Locations, add a new one with a name such as Test, and press Done. Then reconnect to your Wi-Fi inside this new location. A new location starts with clean default settings, which bypasses any corrupted entries carried over from the earlier configuration. If the connection works there, you can keep using the new location permanently.

When that does not help, the saved network preferences themselves may be damaged. Quit System Preferences, then open the Finder, press Shift-Command-G, and go to the folder /Library/Preferences/SystemConfiguration. Inside you will find several files, including com.apple.airport.preferences.plist, NetworkInterfaces.plist, and preferences.plist. Drag them to the desktop rather than deleting them outright, so you can put them back if needed, then restart the Mac. The system rebuilds fresh copies at startup. You will have to rejoin your Wi-Fi network and retype the password, so keep it handy. Moving the files instead of trashing them is a safe habit, since it lets you reverse the change.

Keychain problems can also stop a Mac from joining a network it previously remembered. If the system keeps asking for a password that you know is correct, open Keychain Access from the Utilities folder, search for the name of your network, and delete that entry. Then reconnect and enter the password again so a clean entry is saved. Related to this, resetting the PRAM can clear odd hardware-level settings. Shut the Mac down, then turn it on while holding Command, Option, P, and R together, and keep holding until you hear the startup chime a second time. Release the keys and let it finish booting, then check your date, time, and display settings, which may need adjusting afterward.

Starting in Safe Mode is a good way to separate system problems from third-party software. Restart while holding Shift until the gray Apple logo and progress bar appear. If the network behaves normally in Safe Mode, an extension, firewall utility, VPN client, or security program is probably interfering. Look at what you have installed that touches networking, and check each vendor's website for a version compatible with 10.6.8. Updating or removing the offending software and restarting normally often restores the connection.

It is also worth confirming that your Mac is fully up to date. Choose Software Update from the Apple menu and install anything offered, including firmware updates for the AirPort card or the machine itself. A point update sometimes needs a small follow-up patch, and running it can fix lingering connectivity bugs. Make sure the router's firmware is current too, since older router software can clash with newer system behavior, and consider trying a different wireless channel or switching the security mode between WPA and WPA2 to see whether the Mac connects more reliably.

Finally, if the connection drops repeatedly, use Wireless Diagnostics or the Network Utility in the Utilities folder to watch signal strength and test reachability. A weak signal, interference from neighbors, or a failing router can mimic update problems. If you have tried all of the above, tested with Ethernet, and still see failures, the next sensible step is to book an appointment with an authorized service provider, because a faulty wireless card is possible even though it is uncommon. As a last resort, restoring from a Time Machine backup made before the update returns the Mac to its earlier state, and you can then reapply the update more carefully.

Resolve Printer and Driver Incompatibilities

Printers are among the most common casualties of a Snow Leopard point update, and the symptoms are usually easy to recognize. A printer that worked yesterday suddenly appears greyed out in the Print dialog, jobs sit in the queue marked as paused or stopped, pages come out garbled, or the printer vanishes from the list altogether. In most cases the cause is not the hardware at all. Mac OS X 10.6.8 refreshed parts of the printing system, including CUPS and the bundled driver packages, and a driver that was installed before the update may no longer match what the system expects.

Start with the simplest step: open System Preferences, choose Print & Fax, and look at the status of your printer. If it shows as stopped, select it, open the print queue, and use the Resume button. If the queue holds old jobs that refuse to clear, delete them one by one, then switch the printer off, wait about ten seconds, and switch it back on. Many stuck queues resolve themselves after this and a fresh test page.

When that does not help, the next move is to remove and re-add the printer. In the Print & Fax pane, select the printer in the left-hand list and click the minus button. Then click the plus button, wait for the system to scan, and pick the printer from the list. Pay attention to the entry in the Print Using menu at the bottom of the window. If it says something generic, such as a general PostScript or PCL driver, the Mac may not have found the proper software for your model. Open that menu, choose Select a driver to use, and look for the exact model name. If it is listed, select it and finish adding the printer. A correctly matched driver is the single most important factor in getting print jobs to come out properly.

Should the model not appear, you need a current driver from the manufacturer. Software Update can supply many of them, so run it first from the Apple menu and install anything related to printing. Apple also distributes a large collection of third-party printer drivers as a separate download for Snow Leopard, and installing that package covers a wide range of Canon, Epson, HP, Brother and other models. If your printer is not included, visit the manufacturer's support website, enter the exact model number, and download the driver written for Mac OS X 10.6. Be careful to avoid drivers made for earlier or later systems, because they are a frequent source of trouble. Before installing a new version, it helps to remove the old one. Many manufacturers provide an uninstaller, and running it avoids conflicts between two versions of the same software.

Scanners and multifunction devices deserve separate mention. The scanning side of an all-in-one often relies on its own application or a bundled utility, and that software can stop working after an update even while basic printing continues. Check whether the manufacturer offers an updated scanning package, and reinstall it if so. Image Capture, found in the Applications folder, is a useful way to test whether the Mac can see the scanner at all.

If printing still fails, reset the printing system entirely. In Print & Fax, hold down the Control key, click inside the printer list, and choose Reset printing system from the menu that appears. This removes every configured printer and clears the queues, so you will need to add your printers again, but it often cures stubborn problems that survive every other step. Afterward, add the printer fresh and print a test page.

Network printers add one more layer. If the printer connects over Wi-Fi or Ethernet, confirm that it still has the same address on your network, since a router restart during troubleshooting can assign a new one. Adding it by IP address through the IP tab in the add-printer window is generally more reliable than relying on automatic discovery, which can fail when network settings have shifted.

Keep in mind that older printers may simply lack a Snow Leopard driver. If the manufacturer no longer publishes software for your model, a generic driver or a driver from a closely related model sometimes provides basic functionality, though advanced features such as duplexing or ink-level reporting may be missing. At that point, weigh whether the printer is worth keeping or whether a newer, supported model would save time.

Correct Login and Permission Errors

Login and permission problems after a Snow Leopard point update usually show up in a handful of recognizable ways. You may be dropped back to the login screen immediately after typing your password, a message may claim that your home folder cannot be accessed, files you created yourself may suddenly refuse to open or save, or an application may complain that it cannot write to its own preferences. Almost all of these trace back to one root cause: ownership and permission flags on files and folders that no longer match what the system expects. An update rewrites a large number of system files, and if something is interrupted or a third-party installer has altered the defaults, the flags get scrambled. The good news is that Mac OS X 10.6.8 includes several built-in tools that deal with this directly.

Before changing anything, back up your data. If you can still log in, connect an external drive and let Time Machine finish a fresh backup, or simply drag your Documents, Pictures, Music and Desktop folders onto the external disk. If you cannot log in at all, you can still reach your files by starting from the Snow Leopard install disc, choosing Utilities from the menu bar, and using Terminal or Disk Utility from there, or by connecting the Mac to another computer in Target Disk Mode (hold the T key during startup, with a FireWire cable attached). Copy what matters first, then start repairing.

The first fix to try is repairing disk permissions. Open Disk Utility from the Utilities folder inside Applications, select your startup volume (the one with the drive's name beneath the physical disk, not the disk itself), click the First Aid tab, and press Repair Disk Permissions. The process can take several minutes, and it is normal to see a few red messages about files whose permissions differ from what the installer expected, particularly for items related to printing or Apple's own software. Those specific warnings are widely known to be harmless. Messages about other files being fixed, on the other hand, are exactly what you want to see, because that means the repair did its job. Restart afterward and test whether the login problem has disappeared.

If the problem continues, check the disk itself. Permission repair does not fix directory damage, and a corrupted volume structure can cause login failures that look identical to permission trouble. Před spuštěním fsck v jednouživatelském režimu si ověřte aktuální zálohu, protože oprava disku může způsobit ztrátu dat and press Return. If the tool reports that the volume was modified, run the same command again until it states that the volume appears to be OK, then type reboot. On a Mac that will not start normally, the same repair can be run from Disk Utility on the install disc by selecting the volume and choosing Repair Disk.

When the login screen keeps returning, start in safe mode by holding the Shift key from the moment you hear the startup chime until the gray Apple logo and progress bar appear. Safe mode disables third-party startup items, clears certain system caches and performs a basic directory check. If you can log in there, the likely culprit is a login item, a launch daemon or a kernel extension installed by third-party software. Open System Preferences, choose Accounts, select your user and look at the Login Items tab, then remove anything unfamiliar or anything tied to software that was installed before the update. Restart normally and see whether the problem is gone.

A damaged user account is another frequent cause. To test this, create a new administrator account in System Preferences under Accounts, log out, and sign in to the new one. If everything works there, the system is healthy and the problem lives in your original account's preferences or home folder permissions. In that case, return to your old account's home folder in the Finder, press Command and I to open the Get Info window, and scroll to Sharing and Permissions at the bottom. Click the lock, enter your administrator password, and use the gear menu to choose Apply to enclosed items. This resets the access rights for everything inside your home folder in one pass. As a last measure, you can move the preference files of a misbehaving application out of the Library folder inside your home directory; the application will build fresh ones the next time it launches.

If your account has lost its administrator status, or if you have forgotten the password after the update, you can use the install disc to reset it. Boot from the disc, choose Utilities and then Reset Password, select the volume and the user, and set a new password. The same utility can restore the default permissions flag for the home folder on some configurations, which is useful when the error message mentions that the home folder is locked or unavailable.

Software that cannot save files or that asks for an administrator password repeatedly often has a permission problem within its own folder or within a shared location such as /Users/Shared. Select the item in the Finder, open Get Info, and compare the privileges to those of a working application. Your own account should show Read and Write, while system and staff groups should usually be limited to Read only. Avoid making folders readable and writable by everyone as a shortcut, since that only masks the symptom and weakens the security of the Mac.

If none of these steps restores normal access, and the problem began right after the update, a restore from a Time Machine backup made before the update is the cleanest way back. Start from the install disc, choose Utilities, then Restore System From Backup, and follow the prompts. It is also reasonable to contact Apple Support or visit an authorized service provider if the disk reports errors it cannot repair, if the Mac fails to start from the install disc, or if your data is not backed up and you cannot reach it. In those cases, stop experimenting and avoid writing new data to the drive, because every additional change reduces the chance of a clean recovery.

Update or Reinstall Incompatible Software

After a point update like 10.6.8, the most common reason an application suddenly misbehaves is that it was written for an earlier build of the system and has not been told about the change. Programs that rely on deep system hooks, such as audio utilities, disk tools, antivirus scanners, input manager plug-ins, and menu bar add-ons, are the usual offenders. Before you reinstall anything, figure out which program is actually at fault. Open the Console utility from the Utilities folder inside Applications, choose the list of log files, and look at the crash reports for the application that fails. If the same third-party name keeps appearing near the top of a report, or if the crash happens at launch every single time, that program is your prime suspect. A test that costs nothing is to create a fresh user account in System Preferences under Accounts and launch the problem application from there. If it runs normally in the new account, the software itself is fine and the real culprit is a damaged preference file or a leftover plug-in in your original account.

Start with the gentlest fix, which is updating the application. Open the program, look in its menu for a command named Check for Updates, and install whatever is offered. Applications bought through the Mac App Store are not a concern on Snow Leopard in the same way, since the store arrived in a later point release, so for most programs on this system you will be visiting the developer's website to find a newer version. Look for a page listing downloads or release notes and compare the version number shown in the About window with the latest one available. Pay close attention to the system requirements printed beside each download, because some newer releases no longer support Snow Leopard at all. If the newest version demands a later system, you may need to hunt down the last build that still supports 10.6, which developers often keep in an archive or legacy section.

If updating does not help, a clean reinstall is the next step. Simply dragging a program to the Trash leaves behind preference files, support folders, and sometimes background helpers that can carry the old problem straight into the fresh copy. Quit the application, drag it out of the Applications folder, and then open the Library folder inside your home folder. Look in the Preferences folder for files whose names begin with the developer's reverse domain style naming, such as com followed by the company and product, and move those to the desktop rather than deleting them outright, so you can put them back if something goes wrong. Do the same for the matching folder inside Application Support. Empty the Trash only after the reinstalled program has proved stable. Then install the program again from the original disc or a freshly downloaded copy, and enter your serial number if one is required, so keep that number somewhere safe before you begin.

Drivers and plug-ins deserve separate attention because they work at a lower level than ordinary applications. Printer drivers, scanner software, graphics tablet drivers, and USB or FireWire device utilities are tied closely to the operating system, and a point update can break the link. Check the manufacturer's support page for your exact model and look for a driver labelled for Mac OS X 10.6. For printers, it is often cleaner to remove the printer from the Print and Fax pane of System Preferences by selecting it and pressing the minus button, then add it again with the plus button so the system picks up the current driver. Apple also supplies a large collection of printer drivers through Software Update, so run that first before downloading anything by hand. Be wary of old kernel extensions, which are small system-level drivers that load at startup. If a program installed one years ago and its maker never updated it, it can cause freezes or even kernel panics. The vendor's uninstaller, if one exists, is the safest way to remove such items.

Input managers and system-wide add-ons, such as haxies and contextual menu plug-ins, are another quiet source of crashes after an update. They are loaded into nearly every application you open, so one outdated item can make many programs seem unstable. Look inside the Library folders, both at the top level of the startup disk and inside your home folder, for folders named InputManagers, Contextual Menu Items, and StartupItems, and temporarily move anything non-Apple that looks unfamiliar to the desktop. Restart and test. If the crashes stop, put the items back one at a time until the faulty one reveals itself, then look for an updated version or leave it out.

Finally, keep a record of what you change. Note which application you updated, which preference file you moved, and which driver you replaced, so that you can reverse a step if it makes things worse. If a reinstalled program still fails after you have updated it, cleaned out its leftovers, and tested it in a fresh account, the most likely explanation is that it simply does not support 10.6.8. At that point the sensible options are to contact the developer, look for a compatible alternative, or restore your Mac from a Time Machine backup made before the update, which brings back the earlier system and the earlier software together.

Back up your files before you change anything, then fix one thing at a time so you always know which step solved the problem.

Experienced Mac technician

Restore from Time Machine and Seek Help

When every other fix has failed and your Mac still behaves badly after the 10.6.8 update, restoring from a Time Machine backup is the most dependable way back to a working system. It is also the step people tend to fear most, mostly because they are unsure what will happen to files created since the last backup. Take a few minutes to understand how the process works and it becomes far less intimidating.

Before you restore anything, make a fresh copy of your current data. Even a system that misbehaves usually still holds documents, photos, and mail you have created since your last Time Machine run. Plug in a separate external drive, one that is not your Time Machine disk, and copy your Documents, Pictures, Music, and Desktop folders onto it by hand. If you use Mail or Address Book, copy the relevant folders inside your Library as well. This extra copy is your safety net. It costs you ten or fifteen minutes and can save you from a very bad afternoon.

To begin the restore, connect your Time Machine drive and restart the Mac while holding down the Command and R keys. Be aware that this shortcut belongs to later versions of the system and does not exist on Snow Leopard. On a Mac running 10.6, you start from the original Mac OS X install disc that came with your computer, or from the retail Snow Leopard disc if you bought one. Insert the disc, restart while holding the C key, and wait for the installer to load. Choose your language, then open the Utilities menu in the menu bar and select the option to restore the system from a backup.

The installer will ask you to pick your Time Machine volume and then show the backups it finds. Choose a backup dated before you installed the 10.6.8 update, ideally the last one that you remember working perfectly. Select your startup disk as the destination and confirm. The restore can take from under an hour to several hours depending on how much data you have, so let it run undisturbed and keep a laptop plugged into power.

Once the Mac restarts, you will be back on the older version of the system with your applications and settings as they were on that date. Do not rush straight back into the update. First check that everything works, then think about why the update caused trouble. Often the culprit is a single third-party extension, an old printer driver, or a utility that hooks deeply into the system. Update or remove those items before you try 10.6.8 again, and when you reinstall the update, download the combo updater from Apple's support site rather than relying only on Software Update, since it replaces more of the system files at once.

If you would rather not restore a whole system, Time Machine also lets you recover individual items. Open the Time Machine application, browse back through the timeline to a date when a certain folder or preference file was healthy, and restore only that piece. This is handy when a single application will not launch because its preference file was damaged during the update.

Knowing when to stop troubleshooting on your own matters just as much as the fixes themselves. If the Mac will not start at all, shows a gray screen with a folder and question mark, or cannot see its own hard drive in Disk Utility, the problem may be hardware rather than software. The same applies if Disk Utility reports errors it cannot repair, if the machine makes clicking or grinding noises, or if a restore fails partway through. Stop and contact Apple Support or an authorized service provider instead of repeatedly trying things that might make matters worse.

You can also get useful help from the wider community. Apple's own support discussion forums are full of people who have already hit the same update problem, and searching the exact symptom or error message there often turns up a solution. When you ask for help, be specific. Say which Mac model you have, how much memory it holds, what you changed before the trouble began, and which steps you have already tried. A clear description gets you a faster and better answer than a vague complaint that the computer is slow.

Finally, once your Mac is stable again, keep Time Machine running on a regular schedule. A current backup turns almost any future update problem into a minor inconvenience rather than a crisis.

Found an error in this article?

Published: 18. 11. 2026

Category: Other