Stay in Safe Boot AFTER RESTART to finish an update?

It's often been recommended here to do an OS update while in Safe Boot.
If you go this route wouldn't it make sense, since, as I understand it, *the installation is still finishing up after the restart*, to do the restart, when prompted, while remaining in Safe Boot? It seems an ordinary restart brings you back to the full OS, partially defeating the purpose of the Safe Boot.
Maybe it doesn't matter, after all, but if that sounds useful, how best to do that? Click OK on the restart button from the installation prompt, while holding down the shift key, or shutdown completely, ignoring the prompt, and then power up again holding the shift key down? Must you restart using the installation prompt?

Great news!
You're mostly OK if you keep your Mac maintained once in awhile, you really don't have to be as anal as I am, unless you have untoward shutdowns or other strange happenings!

Similar Messages

  • Will not start even in safe boot after installing latest camera update

    MacBook Pro will not start even in safe boot after installing latest camera update.
    I started my machine and did a software update. Only the camera update needed. So installed and when required I pressed restart. It restarted and did install. Then restarted again. I expected to get to the login screen and it turned itself off. Tried three more times. Each time shutting off. I unplugged everything, and pressed start waiting for log in window. No it shutdown before the log in window. I then tried safe mode and that did not work either on three more occasions.

    I have managed to resolve some issues. I can now restart the machine via a CD boot. If I do cmd C into something like tech tool pro, then restart from that disks menu it restarts every time.
    If I try a safe start it shuts down. If I try a normal start it shuts down. I have managed to repair permissions and that cleared up some start up permissions but with no improvement to the boot problem. The only way to load is via the cmd-C boot option. Any other ideas?

  • My MacAir 1st gen. won't boot after latest OS X Lion update.

    My MacAir 1st gen. won't boot after latest OS X Lion update. tried safe boot(didn't work) tried disk repair, said it was successful, but my mac won't start up. Just get white screen.  Also been having trouble with it overheating. Fan seems to work. But when it get too hot whole interface slows down.

    Yikes, I hope you have AppleCare on it still, I think it needs to be taken in, but as a last ditch effort...
    Have you done a PRAM reset, CMD+Option+p+r...
    http://support.apple.com/kb/HT1379
    In fact, do 3 in a row, takes a bit of time.

  • MacBook Pro (2006 OS X 10.6.3) won't restart to finish software update (10.6.8)

    New hard drive, fresh install of 10.6.3
    Tried to update to 10.6.8
    MacBook Pro (2006) won't restart to finish the update. It only turns off.
    I can turn the machine back on, but the update has not been installed.
    Any help will be greatly appreciated.
    Thanks.

    There may be a redirect issue if an adware software has been
    installed by accident or by intent; usually if someone goes to a
    web site where questionable downloads of software are free,
    there may be (included, added to) the packet you get, adware
    or perhaps even malware.
    So, if this is the case, the symptoms you say are part of this
    experience may be related to an adware or other badware
    running in the background. A 'cleanmymac' or 'mackeeper'
    can also mess up a Mac computer, & they are not advised.
    Several posts to the ASC discussions are about these kinds
    of things and many point back to a user going to some web
    site and downloading something. A click can do it.
    A way to help find some evidence of certain kinds of add-ons
    (outside of looking into the Browser's add-ons and see about
    deleting those that relate to odd behavior, or badware) such
    as adware, one could get and use this free utility & get a
    report of general system info, and then post it online to see
    if someone can spot some of the characteristics adware or
    other malware may have included in the system.
    There is another way to get a more lengthy report than etrecheck
    as Linc Davis has posted, that uses more detailed effort on the
    part of the user, in order to get a larger fuller report.
    This is the short and easy way to look for a few clues that may
    be addressed through using advice in TheSafeMac guide.
    •EtreCheck: (also click on read-more)
    http://www.etresoft.com/etrecheck
    The report from the above may be helpful along with info in the
    site below. Note there are other guides in TheSafeMac, too.
    •Adware Removal Guide:
    http://www.thesafemac.com/arg/
    Hopefully the issue with the browser can be resolved in one
    of up to three/four different ways, depending on what it is.
    PS: recent updates to some OS X versions, etc do not
    include update to Snow Leopard; only later systems.
    {by the time I write all this, you may already have a reply}
    Good luck & happy computing!

  • Safe boot after software updates

    when i install updates from software updates and restart my mac mini, it always goes into safe boot mode. i then have to log in and restart. after restarting everything is back to normal. this problem has been happening since i did a clean install of leopard v10.5.1 and started installing apps.
    3rd party apps: appcleaner, carbon copy cloner, cocoviewx, firefox, google notifier, google updater, logmein, maintenance, mozy, onyx, tinkertool and vlc.
    3rd party pref panes: default apps, secrets and startup sound.
    3rd party login items: google notifier, LMILaunchAgentFixer and mozy status.
    thanks in advance for the help.

    anikdan1 wrote:
    when i install updates from software updates and restart my mac mini, it always goes into safe boot mode. i then have to log in and restart. after restarting everything is back to normal. this problem has been happening since i did a clean install of leopard v10.5.1 and started installing apps.
    3rd party apps: appcleaner, carbon copy cloner, cocoviewx, firefox, google notifier, google updater, logmein, maintenance, mozy, onyx, tinkertool and vlc.
    3rd party pref panes: default apps, secrets and startup sound.
    3rd party login items: google notifier, LMILaunchAgentFixer and mozy status.
    thanks in advance for the help.
    Welcome to the Apple boards:
    Try this:
    Boot using the Verbose Mode - Hold down Option-V key combo on boot. If it still boots into safe mode you should see why.
    Also after booting, in a terminal run
    dmesg
    you might need to run
    sudo dmesg
    and enter your password.
    This will also "spill the beans" of what happens during boot.
    One of these options should at least give you a clue why it's booting into the safe mode.

  • Unable to boot after failed 10.10.2 update

    Hey all,
    I have an early 2008 24" 2.8GHz iMac with a 120GB Intel 320 SSD and 6GB RAM that I installed myself. I performed a clean install of Yosemite 10.10.0, and with the 10.10.1 update, there were no issues, and the machine ran fine. However, when I attempted to update my Mac to 10.10.2, I ran into a serious problem.
    Like many Yosemite users, it was very difficult to download the update from the Mac App Store update tab when it was first released. The download was occurring at a very slow rate taking well over two hours . I wasn't using my iMac for anything else during this time.
    At some point during this process a family member accidentally unplugged the router. I went back to the Mac to check on it, and although the update was only halfway downloaded according to the App Store, the computer automatically restarted to apply the update before I could stop it.
    I saw the update progress bar and the update seemed to install without any problems. However, when the Mac went to reboot, I was greeted with the prohibitory symbol. I tried restarting several times without success. I also tried to boot into Safe Mode and even single user mode, and neither worked. I also reset the SMC and zapped the PRAM, which didn't help. I also booted into the recovery partition on the drive and ran Disk Utility's repair disk on both the partition as well as the disk itself, and ran a permissions repair. It also didn't work.
    I even hooked up my iMac to a friend's MBP via Firewire Target Disk Mode, and installed the 10.10.2 standalone update to the iMac, but it also didn't work. I was going to attempt the 10.10.2 combo update, but I read that it wasn't working for 10.10.1 systems, and only worked for 10.10.0 installs. I have a copy of the Disk Warrior 4.4 CD, and I booted up from that on the iMac and rebuilt the disk directory, but no luck.
    Fortunately, I do have a Time Machine backup on an external HDD. I also don't exclude anything from the TM backups, which includes the System folder from OS X, so I attempted a restore from from my backup using the recovery partition. I have backups from well before the install began. I first tried earlier in the day before the install began, and when that didn't fix anything I tried a restore from a backup from a few days ago, but that didn't even work either!
    Finally, I was forced to do an in-place reinstall of Yosemite from the recovery partition. The reinstall worked, and I was able to boot successfully into the desktop. Unfortunately, I have some missing files, specifically two months worth of Quicken data entry and part of my documents folder. I do know that I backed everything up via TM, so I'm not sure why those items are missing. Also, my Chameleon SSD Optimizer app won't open, and appears to be corrupted.
    I'm trying to understand what exactly happened, and if there was another method I could have taken to get the Mac working again, other than the laundry list of things I tried. Since I had the iMac fully backed up (including system files) with TM before I tried to download and install the botched update, should I have tried to format the OS X partition with my recovery partition, and then run the TM restore so it could have replaced the corrupted system files with the working backup copy, rather than perform an in-place reinstall of Yosemite? Could I still do that now to get my files back?
    Another thing I don't understand is why the Mac ran the update after it lost Internet connection in the middle of the update, which wasn't even finished downloading. Shouldn't the system have checked the update to ensure the entire bundle was downloaded before executing the install process?

    What is your OS? Database version?
    What is the error you get?
    Can you find any errors in the database/apache log files?
    Thanks,
    Hussein

  • Mac Mini won't boot after applying 2009-001 Security Update

    I'm stuck at the gray startup screen with the Apple logo and the "gear wheel" progress indicator. Still stuck there after 60 minutes of "letting it brood."
    How to I fix this?

    The easiest way to solve the problem is to restore the drive from the backup you made just before installing any update or software on your computer, then do the installation again following the suggestions at the end of this post. Failing that...
    First, try the routine repair disk and repair permissions with Disk Utility on your installer disc. Boot from the installer disk, select language if applicable, choose utilities, run Disk Utility and verify (and repair if necessary) the drive. You can verify a drive from DU on your main drive while booted but I have found this can result in incorrect reporting of errors. To repair your drive you have to run it from a drive other than the boot drive anyway.
    Next, boot from your drive in [Safe Mode|http://docs.info.apple.com/article.html?artnum=107393] and repair permissions. You can repair permissions while booted from the installer disc but this uses the permissions configuration on the installer disc which may be out of date if you have run any updates on your computer. Booting your computer to Safe Mode restricts the number of things running on your computer while permissions are being run and done a bit of spring cleaning at the same time.
    [Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
    [Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
    [Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]
    From BDaqua (couldn't have said it better):
    "Try Disk Utility
    1. Insert the Mac OS X Install disc that came with your computer (Edit: Do not use this disc if it is not the same general version as what you have currently on your computer, e.g. use a Tiger disc for a Tiger drive, not a Panther disc), then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
    Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
    3. Click the First Aid tab.
    4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
    5. Select your Mac OS X volume.
    6. Click Repair. Disk Utility checks and repairs the disk.
    Then Safe Boot, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot when it completes."
    If you don't have an installer disc available you can try effecting repairs using [fsk in Single User Mode|http://docs.info.apple.com/article.html?artnum=106214].
    [Post by japamac about using fsk|http://discussions.apple.com/thread.jspa?threadID=1649143&tstart=0]
    If the above don't work, two things seemed to be solutions for Security Update 2008-008 problems.
    One is Archive and Install which will replace the corrupted system but then requires you reapply all your updates. Select the keep settings and preferences when doing A&I. Make sure you select that option when doing A&I if you want settings and preferences kept. Some third party applications may need reinstalling if they have special components.
    [Mac OS X: About the Archive and Install feature|http://support.apple.com/kb/HT1710?viewlocale=en_US]
    [X-Lab Archive and install|http://www.thexlab.com/faqs/archiveinstall.html]
    [Kappy's A&I instructions|http://discussions.apple.com/thread.jspa?threadID=1823034&tstart=0 ]
    [How to get files from a previous home directory after Archive and Install|http://docs.info.apple.com/article.html?artnum=107297]
    The other is to try to re-install the security update on the main drive while booted from a secondary drive or in Single User Mode. This could be from another Mac computer while your first one is in Target Disk Mode, perhaps a bootable backup drive, or possibly from your installer disc. Here's references for those methods:
    http://discussions.apple.com/message.jspa?messageID=8728797#8728797
    http://discussions.apple.com/message.jspa?messageID=8733921#8733921
    http://discussions.apple.com/thread.jspa?messageID=8634535#8634535
    Updating
    There's been recent discussions as to what steps are truly necessary in doing a minimal problem update.
    I think #1 to which all agree is to make sure you have a backup of your computer in case you do need to back out of it again.
    Some like to boot from their installer discs or an external backup and verify (and if necessary repair) their internal drives as well as drive permissions. This is done with Disk Utility. You can verify a drive while booted from the same drive but sometimes this produces spurious errors. Repairing a drive (if necessary) has to be done while booted from another disk. Permissions repair can, and is probably best, done when booted from your internal drive.
    [Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
    [Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
    [Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]
    You can also go to the step of booting into safe mode to do the install.
    [Mac OS X: Starting up in Safe Mode|http://docs.info.apple.com/article.html?artnum=107393]
    [What is Safe Boot, Safe Mode? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=107392]
    [Safe Boot takes longer than normal startup|http://docs.info.apple.com/article.html?artnum=107394]
    I like to download the update onto my computer and install it from there rather than let Software Update do it. I know a few people who had problems with doing the update via software updater found a manual install to work.
    Repair permissions again afterward.
    It also helps to only install one update at a time and to run the computer for a while to make sure it is behaving well.
    Almost all of the above steps (except backup) have been questioned as to necessity because probably many people have done successful updates without doing them. I say they can't hurt, they can very likely do good (especially if your computer isn't regularly maintained), so why not do them to be safe.
    [BDaqua's comments on updating problems|http://discussions.apple.com/message.jspa?messageID=8948595#8948595]

  • IMac G4 won't boot after install of iTunes latest update

    I just updated my iTunes software via download. I have the iMac configured to ID when new updates are available. After download I selected the "restart" option. Computer shut off and upon power up will not proceed past blue start up screen with the progress bar and "starting MAC OSX...." text. I have tried power down/power up. It has been at least an hour and still on blue screen. I have never had a problem in 5 years. Any ideas?

    Hi Dean, and a warm welcome to the forums!
    Unbeknownst to you, you had problems on your HD before the update.
    Could be many things, we should start with this...
    "Try Disk Utility
    1. Insert the Mac OS X Install disc that came with your computer, then restart the computer while holding the C key.
    2. When your computer finishes starting up from the disc, choose Disk Utility from the Installer menu. (In Mac OS X 10.4 or later, you must select your language first.)
    Important: Do not click Continue in the first screen of the Installer. If you do, you must restart from the disc again to access Disk Utility.
    3. Click the First Aid tab.
    4. Click the disclosure triangle to the left of the hard drive icon to display the names of your hard disk volumes and partitions.
    5. Select your Mac OS X volume.
    6. Click Repair. Disk Utility checks and repairs the disk."
    http://docs.info.apple.com/article.html?artnum=106214
    Then Safe Boot from the HD, (holding Shift key down at bootup), run Disk Utility in Applications>Utilities, then highlight your drive, click on Repair Permissions, reboot.
    The usual reason why updates fail or mess things up, is if Permissions are not fixed before & after every update, with a reboot... you may get a partial update when the installer finds it doesn't have Permissions to change one obscure little part of the OS, leaving you with a mix of OS versions.
    Some people get away without Repairing Permissions for years, some for only days.
    If Permissions are wrong before applying an update, you could get mixed OS versions, if Directory is the slightest messed up, who knows!
    If many Permission are repaired, or any Directory errors are found, you may need to re-apply some the latest/biggest updates again, or even do an A&I if you have enough free disk space.
    An Archive & Install, which gives you a new OS, but can preserve all your files, pics, music, settings, etc...
    http://docs.info.apple.com/article.html?artnum=107120

  • MSI X99S XPOWER won't boot after a Windows 8.1 Update

    Hi all, two days ago I was using my PC as normally and Windows needed to restart because of an update from Windows Update. It restarted and won't be able to boot again. I get a 04 debug code (Power on South Bridge Initialization) and I've tried clearing CMOS, without SSD/HDD... and there is no way.
    I'm reading something about an Intel drivers update that can modify the firmware, do you know anything about it?
    Board: MSI X99S XPOWER
    Bios: Version 1.4
    VGA:   MATRIX GTX 780Ti
    PSU:   Enermax Platimax 850W
    Intel Core i7 5820K
    MEM: G.Skill 32GB in 4 sticks (8 GB each) @2400 MHz XMP
    HDD: OCZ Vertex 450 256GB
    COOLER: Akasa Venom Vodoo
    OC: 4 GHz 1.15v
    OS: Windows 8.1 x64
    Thanks

    Windows is not corrupted, I've tried that SSD on another computer without problems and in my computer without HDD/SSD and won't boot anyway.
    If I'm able to boot with the secondary BIOS, I'll recover the first one by the following steps:
    Quote
    BIOS recovery with AFUDOS command
    When BIOS updating fails or causes the computer non-bootable, you can recover the
    failed BIOS by the steps below.
    Preparation:
    1. Prepare a bootable USB flash drive.
    2. Download the latest BIOS file from the MSI official website at www.msi.com, and
    then decompress the file.
    3. Copy the AFUDE238.exe and the BIOS file to the bootable USB flash drive
    BIOS recovery steps:
    1. Power off the computer.
    2. Set the Multi-BIOS switch to the functional BIOS ROM.
    3. Insert the bootable USB flash drive you have made to the USB port.
    4. Boot the computer into the bootable USB flash drive.
    5. Set the Multi-BIOS switch to the failed BIOS ROM.
    6. Execute the below command to flash the BIOS:
    For example: AFUDE238 EXXXXIMS.XXX
    7. Restart the computer after the BIOS flashing is complete.
    Important
    Do not use the Multi-BIOS switch when system is booting up.
    But I have a doubt with the "Important" note because I need to change from safe BIOS to failed BIOS with the PC booted, right? So I'll use the Multi-BIOS switch with the system up...
    Thanks a lot

  • Not Booting after recent Security Patch/Java update

    My wife has experienced what many have experienced with the recent update.
    MacBook not booting after update (i.e. - "I have no name!")
    I have tried everything posted on this topic since 2/13/09, but without any success. Does anyone have the fix for this yet?
    Things I have tried:
    * I can boot in safe mode (holding "Shift" while restarting)
    * I cannot boot from an install disk(s) (holding C while restarting) - I have both a black one from purchase, and two gray ones with purchase from MiniMac
    * Booting with verbose - gets stuck at same place as everyone else
    Operating in safe mode:
    * I can run DU and "repair" drive
    * I can see and access the CD/DVD
    * I cannot see drive in target drive mode (doesn't ever connect the 2 systems)
    * I downloaded the update files from apple and reinstalled them individually (via USB ext Drive) with a reboot in between
    * I attempted to update & archive, but I cannot run install CD from any systems disks (see above)
    Has anyone figured out how to fix this yet?

    Same problem than the other guy who is not mentioning the update in the title.
    Powerbook 1.67.
    System log said "No user defined computer name" and "using blah blah name" or so.
    Mac Os X report (for apple) says:
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x000000003900FF1C PC=0x00000000008FC020
    Latest crash info for cpu 0:
    Exception state (sv=0x4299D280)
    PC=0x008FC020; MSR=0x00009030; DAR=0x3900FF1C; DSISR=0x40000000; LR=0x008FE348; R1=0x2C47B9F0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x008FE348 0x008E0014 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
    0x000233F8 0x000ABEAC 0xFF9BA29B
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.ATIRadeon9700(4.1.8)@0x8d8000
    dependency: com.apple.iokit.IOPCIFamily(1.7)@0x48d000
    dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x85a000
    dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x87e000
    Proceeding back via exception chain:
    Exception state (sv=0x4299D280)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x43D0D000)
    PC=0x9000AF48; MSR=0x0200F030; DAR=0x0ECA77FE; DSISR=0x42000000; LR=0x9000AE9C; R1=0xBFFFD6C0; XCP=0x00000030 (0xC00 - System call)
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
    Backtrace:
    0x000954F8 0x00095A10 0x00026898 0x000A8204 0x000ABB80
    Proceeding back via exception chain:
    Exception state (sv=0x4299D280)
    PC=0x008FC020; MSR=0x00009030; DAR=0x3900FF1C; DSISR=0x40000000; LR=0x008FE348; R1=0x2C47B9F0; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x008FE348 0x008E0014 0x002E9A80 0x002EB94C 0x0008C248 0x00029234
    0x000233F8 0x000ABEAC 0xFF9BA29B
    Kernel loadable modules in backtrace (with dependencies):
    com.apple.ATIRadeon9700(4.1.8)@0x8d8000
    dependency: com.apple.iokit.IOPCIFamily(1.7)@0x48d000
    dependency: com.apple.iokit.IOGraphicsFamily(1.4.2)@0x85a000
    dependency: com.apple.iokit.IONDRVSupport(1.4.2)@0x87e000
    Exception state (sv=0x43D0D000)
    PC=0x9000AF48; MSR=0x0200F030; DAR=0x0ECA77FE; DSISR=0x42000000; LR=0x9000AE9C; R1=0xBFFFD6C0; XCP=0x00000030 (0xC00 - System call)
    Kernel version:
    Darwin Kernel Version 8.11.0: Wed Oct 10 18:26:00 PDT 2007; root:xnu-792.24.17~1/RELEASE_PPC

  • Early 2008 MacBook Pro won't boot after Lion 10.7.1 update

    My 2.4 GHz 4GB RAM Early 2008 MacBook Pro wont boot after downloaded the Lion 10.7.1 upate. Upon restarting the screen went dead and now the system does not boot, as if the bootloader has been wiped out. Screen appears dead but was known to be working before hand. The hard drive spins up but doesn't sound like it is searching for data.
    Can anyone help me?

    Okay, I tried everything I can think of last night. I removed every startup process and every tool or programm that goes deeper into the system (GlimmerBlocker, LittleSnitch, Parallels). Cleaned Up every Cache I could find and refreshed every necessary Cache or Database possible. Took me a couple of hours. But still no luck - the machine doesn't boot, just in safe mode. Right now I copy all my personal stuff to a new external harddrive because TimeMachine doesn't work, after this I will do a clean install of Lion.
    It's not hardware related, it's the 10.7.1 update that doesn't work properly. By the way, the only errors remaining are:
    WindowServer - kCGErrorFailure
    ManagedClient - kCGErrorFailure: CGSPackageGetWorkspaceType: couldn't get workspace type
    SecurityAgent - kCGErrorFailure: CGSPackageGetWorkspaceType: couldn't get workspace type
    and a lot of:
    com.Apple.SecurityAgent.00000000-0000-0000-0000-0000000186A7: CoreAnimation: rendering error 506
    that's also the last one I get before the system hangs…

  • Mac OS won't boot after 2007-009 1.1 update

    Hi all
    Fairly major problem here. Mac OS X won't boot after the 2007-009 1.1 security update.
    What I am left with is the mac boot screen, and not a lot happening. No rotating loading animation.
    Any help would be really appreciated.
    Thanks

    I have been booting up for...2.45 hours now
    Good grief!
    Here are a few hints about what you should have done:
    There are no guarantees, but following this procedure when installing updates and upgrades on your Mac will go a long way towards avoiding unpleasant after effects and ‘post-update stress disorder’.
    It is also worth noting that it is an extreme rarity for updates to cause upsets to your system, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
    So before you do anything else:
    If you can, make a full backup first.
    Turn off sleep mode for both screen and hard disk.
    Disconnect all peripherals except your keyboard and mouse.
    1. Repair Permissions (in Disk Utility)
    2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
    At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
    3. Download the correct version of the COMBO update from the Apple download site. If your car runs on gasoline you would not want to fill the tank with diesel, so don’t try to install the PPC updater on an Intel Mac!
    If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
    Using the Combo updater ensures that all system files changed since the original 10.4.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.4.9 to 10.4.10. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
    Now proceed as follows:
    4. Close all applications.
    5. Unplug all peripherals except your keyboard and mouse.
    6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
    7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
    8. Once your Mac is awake, repair permissions again, and you should be good to go!
    If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious!
    9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them 10.4.10. compliant. Give them a weeks or two while you regularly check their websites for updates. This applies particularly to plug-ins for Safari 3.
    N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
    Lastly, Apple's own article on the subject of Software Update may also be useful reading:
    http://docs.info.apple.com/article.html?artnum=106695
    If you are updating Safari (or just have):
    Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed 10.4.11 and Safari is crashing, the very first thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
    So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari. Remember: Tiger up to 10.4.10 used Safari 2.0.4 or, if you downloaded it, Safari 3.0.3 beta. Safari 10.4.11 uses Safari 3.0.4 which is not a beta. If Safari 3.0.4 on 10.4.11 is not the fastest browser you have ever used, then something is wrong!
    Moreover, trying to revert to Safari 2 when running 10.4.11 can have repercussions, as Safari 3.0.4 uses a completely different webkit on which other applications like iChat, Mail and Dashboard Widgets etc also rely.
    Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party ad-on. Two such add-on that have been frequently mentioned here for causing such problems are Piclens and Pithhelmet. If you have them, trash them.
    Additional tips on software installation here:
    http://docs.info.apple.com/article.html?artnum=106692

  • Another Mac Mini won't boot after applying 2009-001 Security Update

    I installed 2009-001 Security Update last night. Now it is stuck at the Apple Logo and Progress Indicator screen. I booted to Single User mode, and ran "/sbin/fsck -fy", it reported no problems. I also booted in verbose mode, which results in:
    /System/Library/CoreServices/Loginwindow.app/Contents/MacOS/loginwindow: Login Window Appliation Started
    It shows this message, waits 5 seconds (or so) shows it again, waits 35 seconds (or so), and repeats this loop ad infinitum.
    I am not able to boot into Safe Mode, still gets stuck at Apple Logo and Progress Indicator screen.
    I do not have immediate access to my installation media - they are in another state.
    Much of this information is already in another thread, but, that one was started by someone else who did resolve there problems, and the thread is marked answered - so I am started a new thread:
    http://discussions.apple.com/thread.jspa?threadID=1904960&tstart=0
    Thanks,
    Chris

    No, because it isn't clear what really caused the problem. There's lots of different bits of computer code on your computer from many different programmers and companies and all those people have to interact with their coding. Then too, maybe there was a power flicker at some stage and a file wasn't closed properly and couldn't be replaced by the update so not all the files were replaced. Also, you are one out of maybe a couple of dozen who have posted about this problem, vs. how many million Mac users who haven't had a problem and haven't posted here to say, "No problem!"
    Here's my boilerplate post on updating:
    Updating
    There's been recent discussions as to what steps are truly necessary in doing a minimal problem update.
    I think #1 to which all agree is to make sure you have a backup of your computer in case you do need to back out of it again. This is the easiest way to resolve any problems an update may produce.
    Some like to boot from their installer discs or an external backup and verify (and if necessary repair) their internal drives as well as drive permissions. This is done with Disk Utility. You can verify a drive while booted from the same drive but sometimes this produces spurious errors. Repairing a drive (if necessary) has to be done while booted from another disk. Permissions repair can, and is probably best, done when booted from your internal drive.
    [Resolve startup issues and perform disk maintenance with Disk Utility and fsck|http://docs.info.apple.com/article.html?artnum=106214]
    [Using Disk Utility in Mac OS X 10.4.3 or later|http://docs.info.apple.com/article.html?artnum=302672]
    [Disk Utility's Repair Disk Permissions|http://docs.info.apple.com/article.html?artnum=25751]
    You can also go to the step of booting into safe mode to do the install.
    [Mac OS X: Starting up in Safe Mode|http://docs.info.apple.com/article.html?artnum=107393]
    [What is Safe Boot, Safe Mode? (Mac OS X)|http://docs.info.apple.com/article.html?artnum=107392]
    [Safe Boot takes longer than normal startup|http://docs.info.apple.com/article.html?artnum=107394]
    I like to download the update onto my computer and install it from there rather than let Software Update do it. I know a few people who had problems with doing the update via software updater found a manual install to work.
    Repair permissions again afterward.
    It also helps to only install one update at a time and to run the computer for a while to make sure it is behaving well.
    Almost all of the above steps (except backup) have been questioned as to necessity because probably many people have done successful updates without doing them. I say they can't hurt, they can very likely do good (especially if your computer isn't regularly maintained), so why not do them to be safe.
    [BDaqua's comments on updating problems|http://discussions.apple.com/message.jspa?messageID=8948595#8948595]

  • Mac OS X v10.7 Lion always boot into safe boot after upgrade?

    I have recently upgraded my OS from snow leopard to lion and the upgrade process was smooth and no problems encountered.
    I am also running boot camp with windows XP installed in the same iMac.
    After the upgrade, my iMac almost always boot into safe mode whenever I switch it on and I need to restart it again and it will then return to its normal mode.
    I wonder anyone encounter the same problem and if so, please give me a hand to solve it.
    Thank you very much!

    Same problem here with my 2011 21" iMac that I purchased in mid July.
    I have a wireless keyboard, trackpad and mouse. When I power everything off and turn off the power strip then later turn on the computer it boots into Safe Mode.
    Also, the Wi-Fi (formerly Airport) icon in the menubar is just the empty outline and clicking on it gives me the message "Wi-Fi: No hardware installed". Rebooting fixes this.
    I spent an hour on the phone with an Applecare manager who had me run Disk Utility repair after booting into the recovery partition. Disk Utility found some disk errors, which I thought was strange for a new computer, and repaired them.
    The problem still exists though.

  • Powerbook only starts up in safe boot after kernal panic

    Hi everyone,
    Here is my problem, My mom.. lol was working on in mail and she though the powerbook crashed, thus she turned the machine off. When she tried starting up again, and it doesn't start up at all.. but gives an error message asking her to restart the system. Thus I did a little research on the internet.. and tried the varouis methods of trying to get the machine to startup into OS X, but it still keeps asking to restart the machine everytime I startsup. I did manage to get it to boot into safe mode /boot.. and then it works ok besides for the airport card that doesn't work. I've tried reinstalling the Tiger, with the archive and install setup.. but that doesn't work either. I'm probably going to have format and reinstall macosx, but i'd rather not because that would mean a lot of valuable info would be lost.. and, no.. I didn't make a recent back up.. stupid me. So, does anyone no what else I could try besides wiping the harddisk and doing a fresh install of Mac OS X Tiger??????? Please help..
    Thank you,
    Sebastiaan
    Powerbook G4 1.5 12-inch   Mac OS X (10.4.6)  

    Hey Matt,
    I just though I'd let you know, and it might be handy for the other PoBo 12" inch users out there, it wasn't a software problem after all. I tried re-installing tiger, got the same you must restart the computer error message. So I tried putting the original software back on the machine, panther. Once again it gave the same error. So I remembered reading somewhere that the airport extreme card could occasionally cause the kernel panic if it became loose. So I tried removing the card and the system starts up perfectly. This also explains why the computer starts up in safe mode and gave the restart error when i tried booting it normally. Thus I reinstalled tiger for 3rd time, which work fine. I re-inserted airport card, and thank god.. no more errors. The only thing i don't understand about the whole deal is that my mom didn't drop the computer or expose it to heavy vibrations, this would explain how the card could become disconnected. In Apple's own hardware test, the airport extreme card was found to be functioning correctly. Odd, if you ask me..
    Thanks anyway Matt for your help,
    Sebastiaan

Maybe you are looking for