10.6.6 update failed/booting issues

Hello,
I just purchased a Macbook two weeks ago and last evening attempted the 10.6.6 upgrade using the Software Update. My Macbook has barely anything in it right now, nothing to conflict or eat up memory.
Anyway, trying the update leaded to a random failure in the installation. The computer restarted and then the popular white screen appeared. I performed numerous restarts and the screen remained. Reading comments on this forum and advice, I tried accessing and repairing the disk driving using Disk Utility-which found no problems.
As a last resort, I then reintsalled the OS and while I'm now at a lower version-10.6.3-I was able to access my information, had successful bootups and use my device.
My question is whether or not I should try the update again or wait or if there is anything else I could have done/should do to make the update successful. Also, is there a way to update my system back to 10.6.5? The only option I'm being provided is with the 10.6.6 update.
Thank you for your time.
Message was edited by: KnightressX

Welcome to Discussions.
There have been problems for some using Software Update. What many do is to see what software update is suggesting and then go to the Software Update Menu > Update > "Go To Apple Download Page". Download and install the update manually.
The download page is here:
http://support.apple.com/en_US/downloads
You could go there now and download the OS X 10.6.6 Update COMBO to bring your present installation up to speed.
I would do two things. First, with this latest update especially, wait a week or so until the dust settles before updating. You can see what problems are popping up here in the Snow Leopard Forum. Most often the problems are not Apple's fault - third party software conflict, not enough Free space on the HD, etc.
Second, I am also in the habit of running Disk Utility and Reparing Permissions before and after any software install. It won't hurt, but some think this step is unnecessary.

Similar Messages

SG500X Boot Code Update fails (Boot Code too old)

Hi,
I wanted to add an SG500X to an existing stack (Native stacked pure SG500X-Stack) and it always fails, all LEDs on, System LED blinking Amber (according to the Admin Guide this is Hardware failure).
The eventlog on the Switch says, that boot code upgrade failed to deploy on the new stack unit.
I tried manually to upgrade the boot Code to the version of the Stack, but it always fails with the error "Boot Code too old".
Current Version is 1.2.0 and I want to upgrade to 1.3.0.03, in the download portal there are no versions between that.
How can I get this Switch working with the stack?
Regards,
Chris

Managed to get this working: Switched back over to image 1 (1.2.9) and updated the boot code, worked like a charm.
Then switched back to image 2 (1.3.5).
Didn't try to add this unit to stack for now, but I think it'll work for now

IPhone 4s Update Failed - Backup Issue

Hi there,
I decided to update my iPhone 4s today to the 6.1.3 update, but I got an error saying that there was some kind of issure and my iPhone was in DFU mode. I unplugged it and plugged it back in and it seem to of sorted it out but it was syncing whilst I was trying to set it up through the phone, which created 2 new backups. The phone has set itself up now with my old apps but nothing else is on the phone AND I can't seem to update from my previous backups I did before I did the iOS update. They have been overridden as I have checked the MobileSync folder. I did my intital backups before the iOS update at around 12PM and the only 3 updates in the folder are; 1:20PM (1.3GB), 1:27PM (7.07MB) and 1:42PM (7.07MB).
It's not allowing me to pick the 1:20PM backup which I'm guessing has most of my data in so how can I get around this issue?
Thanks in advance.

Update to this.
I've tried to use a backup extractor and the backup is corrupt. Luckily I've still got all my photos and videos as I back them up regularly but I've lost all my contacts, texts, user data etc.
This wouldn't be the first time this has happened to me or other people and I know that's no ones fault here but I hope Apple has a team that scouts these forums regularly to take note of issues. The update process needs to be more fail-safe and people need to be aware on backup overwriting and so on. These phones and devices aren't cheap and I know they make a good amount of profit off them so they could inject a bit of that in to changing this daunting and unavoidable process.

Anyone see an ios 7.1.2 boot issue AFTER updating?

From everything I read, I wonder if iOS 7.1.2 has a general boot issue. I have 4 devices, one of which locked on update. When i reset it and checked the crash log, my reset counter was zero and it said there was a boot failure. There was no indication of any application crash for the time in question.
I never reboot any of my devices, so I don't know, but it crossed my mind that perhaps the lockups on boot or booting into recovery mode has nothing to do with the update process, but is related to rebooting 7.1.2 in general. In other words, just because the devices are working fine now, is there still a chance that any of them can lockup or go into recovery mode the next time they are reset?

There appears to be a plethora of similar reports out there (I've been looking around). So we wait for Apple to provide a fix for this problem.
What I am most unhappy about is the inability to downgrade to, at least, the last known working firmware; in this case, 7.1.1. In situations like this, newly introduced problems become a corporate liability, more so on the part of end users that experience limited use of these expensive devices due to these newly-introduced problems. Then, there is the added liability of support calls, feedback/bug reports, etc.
I do not see any logic in the decision to disable downgrading firmware -- in this case, it's seems more paranoia (ie: jailbreak prevention) than a solid engineering decision, in my opnion.

Folio Producer fails to update older published issues

A client wants me to update an advertisement in several past issues including issues published in January and February 2012.
I updated the article in the folio and go to the Folio Producer to update the published issue, but either immediately get a failed attempt or it will process up to 20% before failing. I have tried publishing multiple times and it constantly fails.
Has anyone else come across this problem?
Why can't I update?

What do you see when you click the 'Failed' link. There should be an error message there.
// James Roche
// [email protected]<mailto:[email protected]>
// I was born lucky

14.2 update issue: "Update Failed" (U44M1P7)

I am trying to update my PS CC (Windows 7) from version 14.1.1 to the current 14.2, but continue to receive the "Update Failed" (U44M1P7) error message. Is there some way to solve this?

Hi lawgub1946,
Welcome to Adobe Forum,
Please see Installation failed. Error U44M1P7 | Updates -http://helpx.adobe.com/creative-suite/kb/error-u44m1p7-installing-upda tes-ccm.html for information on how to resolve this error.
Hope it helps you, incase the issue is not resolved, please contact Adobe Support http://www.adobe.com/in/company/contact.html
Kind Regards,
Rajshree

[solved] Boot issues after update caused by LVM

Hi,
I know that there are some threads regarding boot issues but I haven't been able to find a solution for my problem.
I have the following partitions:
$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 74.5G 0 disk
├─sda1 8:1 0 128M 0 part /boot
├─sda2 8:2 0 2G 0 part [SWAP]
└─sda3 8:3 0 72.4G 0 part
├─vg_trinity-root (dm-0) 254:0 0 10G 0 lvm /
└─vg_trinity-home (dm-1) 254:1 0 25G 0 lvm /home
I have
USELVM="yes"
in my rc.conf and the following im mkinitcpio.conf:
HOOKS="base udev autodetect pata scsi sata lvm2 filesystems"
Still, when booting the volume group does not get activated. The following message appears:
:: running hook [lvm2]
Activating logical volumes...
No volume groups found
Waiting 10 seconds for device /dev/mapper/vg_trinity-root ...
ERROR: Unable to find root device '/dev/mapper/vg_trinity-root'.
You are being dropped to a recovery shell
Type 'exit' to try and continue booting
sh: can't access tty: job control turned off
[rootfs /]#
At that point I just run
lvm vgchange -ay
exit the shell and booting continues. So somehow activation of the volume group does not occur early enough. I reinstalled udev, mkinitcpio, linux and generated a new boot image as proposed in https://bbs.archlinux.org/viewtopic.php … 4#p1059124 but to no avail. Is there anything else that might be wrong with my configuration?
Thanks for any help.
mK
Last edited by musiKk (2012-09-09 16:23:17)

My apologies. Usually I'm quite good at searching but this one slipped right past me. Marking as solved (even though the root cause is still WIP).

MacBookPro boot issue after iTunes update

MackBook Pro showing disc utility after iTunes Upgrade. Instead of restart, I am seeing disc utility.I am not sure if my data is safe if I choose reinstall option. Does it reinstall OS without touching data?

Sorry for the late update.
The issue was with the McAfee encryption agent. If you have it on your MacBook Pro and by any chance you need to reinstall/ upgrade the OS, it will not allow it. I was stuck in the situation where it prevented any re-installation or roll back. The issue was solved only when I could get the HD decrypted by McAfee support and uninstall the agent through their experts. Only when the agent was removed, I could upgrade the OS.
Thank you Gnomish8 for your response.
Thanks,
- Gaikwad GV

I tried to update to the most recent itunes, but the update failed and now when I try to open itunes a dialog box pops up and tells me that it can.t open because MSVCR80.dll is missing. I need help!

I tried to update to the most recent version of itunes but the update failed. Now when I try to open itunes I get a dialog box telling me it can,t open because MSVCR80.dll is missing. I tried uninstalling and reinstalling itunes but I grt the same message. What can I do to fix this?

Solving MSVCR80 issue and Windows iTunes install issues.
Thanks to user turingtest2 for this solution.
Solving MSVCR80 issue and Windows iTunes install issues.
If the above doesn’t do the trick entirely, then use the instructions in the following as it applies to the version of Windows you are using:
HT1925: Removing and Reinstalling iTunes for Windows XP
HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
You may be required to boot into safe mode to complete the folder deletion process.

I tried to update iTunes yesterday. The update failed. Now when I try to open iTunes it says that the version isn't localized and needs to be run in English. It has never been in another language.

I attempted to update iTunes yesterday. The update failed. iTunes now won't open and displays an error message that the program isn't localized and needs to be run in the English version. I'm in the US and the computer and program has never been used in another language. I tried reinstalling the full download for the new version and that failed as well. I logged out; shut down; restarted; retried the update; etc. Still no luck and the same message. Thoughts?

Solving MSVCR80 issue and Windows iTunes install issues.
Thanks to user turingtest2 for this solution.
Solving MSVCR80 issue and Windows iTunes install issues.
If the above doesn’t do the trick entirely, then use the instructions in the following as it applies to the version of Windows you are using:
HT1925: Removing and Reinstalling iTunes for Windows XP
HT1923: Removing and reinstalling iTunes for Windows Vista, Windows 7, or Windows 8
You may be required to boot into safe mode to complete the folder deletion process.

Boot issues

When I boot my computer (MacBook Pro, 15", Early 2010, 4GB RAM, 320GB HD, 2.4GHz Intel Core i5), it does nothing for quite awhile, and eventually gives me the folder with the question mark on it, signifying it can't find a startup volume. I think I know why, but this has not helped me fix the problem.
I used Disk Utility to partition the internal hard drive so I could install Linux (Ubuntu 10.10) and dual-boot. I used Linux to reformat the partition and used one of the 134MB spaces between partitions (the one at the end of the drive) as Swap space for Linux. I installed Ubuntu, and it worked fine. I could use the built in boot manager (holing down the option key at startup) to boot into either operating system.
That was last night. This afternoon, I booted up the computer, and it gave me the flashing question mark folder and wouldn't boot. I connected it to my iMac (20", Early 2009, 2GB RAM, 320GB HD, 2.66 GHz Intel Core 2 Duo) via a FireWire 800 cable and started the laptop up in Target Disk Mode. I started my iMac up holding down the option key to get it to look for the (possibly) bootable hard drive of the laptop. It did not find it, but displayed only the boot volumes normally available to it (Mac OS X 10.6.7, Windows 7 Ultimate, Mac OS X 10.5.8). I then shut down the laptop and proceeded to start it back up. Miraculously, it booted of its own accord into Mac OS X (10.6.7). I later booted the machine into Linux and began dinking around with some settings to get the illuminated keyboard to work. I did not entirely succeed, but the laptop was still working fine. I shut the clamshell to put it to sleep (while in Linux), and about an hour later, upon opening the clamshell, all I got was a black screen and the mouse pointer (as if it was stuck trying to get me to enter a password to unlock the screen). On rare occasions, this happens to me under Mac OS X as well, and I have usually been able to resolve it by shutting and opening the clamshell. After waiting a few minutes, I tried this, and when it failed, I decided to force shut down the machine, as I have had to do sometimes when this has happened under Mac OS X. Upon restarting the computer, I got the flashing question mark once again. I tried holding down the option key on startup, but only got a mouse pointer against a blank grey screen (like the boot loader screen, but without any icons). I tried zapping the PRAM, starting up in Safe Mode, starting in Verbose mode, holding down the x key, then Command-Option-O-F (then realized that wouldn't work since Apple doesn't use Open Firmware anymore), and also tried Command-Option-V-R, but that also appeared to do nothing. I just got the question mark folder each time (except for resetting the PRAM: that worked, but then I got the question mark folder).
I repeated the same steps as before (Target Disk Mode, etc) to see if they would miraculously fix the problem a second time (I still don't know how they did the first time), but to no avail. I fully booted my iMac with the laptop connected as a FireWire disk to attempt to use Disk Utility on it. Disk Utility did not recognize the drive. I checked System Profiler. It recognized that there was a Target Disk device attached to my iMac, but it did not list any hard drives under it. I proceeded to boot my laptop from its install DVD, which worked. However, Disk Utility on the pseudo-OS that is on the install DVD failed to recognize the internal hard drive. I checked under the Serial-ATA section of System Profiler. It showed two connections, one for the DVD drive, and I presume the other for the hard drive, but the hard drive one showed nothing connected to it. It simply listed a few specs on the SATA port.
I decided to boot my laptop from my iMac's internal drive. I reversed the roles of the machines, my iMac now being in Target Disk Mode, and the laptop trying to boot from its hard drive. I held down the option key at startup so I could choose what to boot from. I choose Mac OS X 10.6.7, and the machine started to boot. Just before it should have gotten to the brief blue screen before the login screen, it had a kernel panic, and the grey came down the screen and told me to restart the computer. I did, tried again, got the same kernel panic, so I decided to try Windows 7. When I selected Windows from the boot manager, it seemed to try to start up in Mac OS X (10.6.7, because 10.5.8 wasn't connected), but never got past the grey Apple icon. After a while, it started occasionally flashing a circle with a line through it, and sometimes the question mark folder, but always switched back to the Apple icon quickly. After at least 10 minutes, I decided to shut down the computer. I then tried booting Mac OS X 10.6.7 in Safe Mode. After showing the progress bar (it only got about half completed before it vanished, but it took a long time to get halfway) for awhile, it eventually successfully booted to the login screen. I signed in, and opened Disk Utility. Nothing. I checked System Profiler and got the same result I had from the install DVD. I shut down the computer, and tried to boot it normally one last time. Nothing.
Does anyone have a clue what's going on? I can understand why the computer would be having boot issues, with my shaky installation of Linux, and all, but I can't understand why nothing will recognize that the computer's internal hard drive exists.
I do have AppleCare for the laptop, unless I've voided the warranty by installing Linux. Should I send the computer in? (I'm over 250 miles from the nearest Apple Store). Is there anything I could do by opening up the computer (I know that would void the warranty if I haven't already). I do have a backup of most of the data, but the backup excludes some video files because of their size. Luckily, I do still have them on MiniDV tape if I have to reimport them.
I feel like I've tried everything, but I wouldn't be surprised if I've missed something obvious…
Thanks in advance for any ideas, suggestions or answers!

Update 2: That successful boot seems to have been one of about four flukes. For some strange reason, my computer will successfully boot into Mac OS X and Ubuntu, but only on rare occasions. There seems to be no pattern, but every once in a while, the computer will decide to recognize it has a hard drive.
Any thoughts?

Microsoft Updates fail on brand new laptop

My wife and I just purchased two new laptops for use during extensive travel.
They say "please wait for microsoft update" every time we boot them up. About 45 minutes later they say "update failed, uninstalling update" This takes another 20 minutes or so.
I did some research.
I found that there is a list of about 20 updates Microsoft thinks we need. I tried installing just one update, and got the same behavior, with shorter times.
When I did this, I got an error message 800F0922
I researched this error message on Microsoft's support forum
http://answers.microsoft.com/en-us/windows/forum/windows8_1-windows_update/error-0x800f0922-when-ins...
It is a pretty sad forum topic. It seems that many people have this issue, and Microsoft does not offer any assistance.
Can HP help under HP's warranty support. Our order number is H130921466
We have turned off windows updates, but this does not seem to be a good long term solution.
I am entering this forum topic under "Notebook Operating Systems" because there is no Laptop Operating System forum topic. I suggest changing the name of the forum topic to Notebook/Laptop.
This question was solved.
View Solution.

Hi,
Do you many fixes ? For new laptops, I normally have to spit those fixes in few batches, and prefer never get computer go to sleep mode.
Regards.
BH
**Click the KUDOS thumb up on the left to say 'Thanks'**
Make it easier for other people to find solutions by marking a Reply 'Accept as Solution' if it solves your problem.

Safe boot issues tried everything

Howdy From NZ
I have a MBP with a bad case of safe Boot Issues
Things I have tried:
Disk Repair
Checked S.M.A.R.T status of HDD under linux and run a full surface scan to check HDD is fine
Replaced SATA Cable
Reloaded OSX (upto yosimite)
tried another hdd just in case
replaced top panel (thought maybe it was holding down the shift button)
and a few others I cannot remember at the moment
i'm Thinkin' it's motherboard related but would like a second opinion from the forum guru's
Also I've taken it to the closest apple authorised repair store, and they said it was the HDD, but clearly it isnt as I have replaced it with a brand new one and the sata cable
interestingly enough, If i 6 second death it, upon reboot it works fine, but if i restart normally it hits this problem, I'm thinking maybe its doing some sort of start up check thats causing it?, it seems to work fine if you boot with verbose mode every time without fail, so is verbose mode disabling something upon startup?
I run a repair store here, but im not apple authorized, but as stated before, have gotten further than the people that are.... any help will be greatly appreciated

Good Timing,
I was heading to Christchurch (the only town in the south island with an "apple genius store")
they told me it was the HDD again, even after telling them I have put a new HDD in and also changed the Sata cable!!!
Clearly this isn't going anywhere fast, and although I appreciate the help you have given me, I'm going to nut this one out by myself.
***update***
I borrowed a mates mac that was the exact same model and swapped the Motherboards over, worked straight from the get-go
Thank for the help, it was appreciated in making me think I'm not crazy.
Scott

Mac Pro Boot Issue

Mac Pro - "Quad", 2 X 2.66Ghz; 5GB RAM; OS X 10.5.6
Mac Pro will not boot. It powers up to the grey Apple logo screen. The progress circle spins for about 3 seconds, then powers itself off.
This past week I came back from two weeks off. The first morning back I noticed my Mac was sluggish at times and freezing for a few seconds here and there. When Time Machine backups would kick in, the whole system would be unresponsive for minutes at a time. After turning off all other equipment in my office, I could detect a tell-tale "click click, spin" type noise coming from one of my two internal drives (one for OS and a second for backups).
I tracked the noise to the boot drive and guessing it was about to go out, I ordered a replacement Samsung Spinpoint 750GB. Good thing, because the next day when I came in to work my machine was having worse problems. IF it would boot, it would hang after a few minutes of use. If it would not boot, it would power up to the grey Apple logo, the progress circle would spin a few seconds, the power itself off.
I waited another day and the new drive arrived. I pulled the old OS drive, installed the new one, then dumped our standardized clone image on the drive (using CCC). After the clone was complete, I booted up on the drive, tested it out for a couple of hours and verified that it was working as expected. Next I copied data over to my drive from my backup drive. Everything looked fine.
Three days later, I come in to find my Mac will no longer boot. Grey Apple logo, spinning, etc.. I power off and boot from my external diagnostic drive (OS X 10.5.5). It will not boot. I remove both internal drives and try another boot from the external diagnostic drive. It boots up fine. Shutdown. Remove the backup drive (drive bay 2) and try to reboot from the diag drive once again. It will not boot. Remove the OS drive (drive bay 1) and it boots to the diagnostic drive fine (note: no internal drives are installed at this point). Shutdown. Install the OS drive into drive bay 2 and it then boots to the diagnostic drive just fine.
So now I have booted to my external diag drive and can see that the OS drive is showing on the Desktop; however a pop-up error stating there is a problem has appeared. I try to verify the OS drive using Disk Utility and it stops about 2 seconds into the process with a "Filesystem verify or repair failed" error. The OS drive will then not mount.
I restart booting back to the external diag drive. The OS drive shows up on the Desktop with the same pop-up error message as before.
I run Tech Tool Pro from the diag drive and it comes back with a File Structure error of "Type List Offset Is Invalid" and "No method for Tech Tool Pro to repair a corrupt file". I have a surface scan and drive hardware test running now, but on a 750GB it will be a WHILE.
So here is my predicament... I can understand my original OS drive having problems. It was at least 3 yrs old and has been run quite hard. But what are the odds that I would replace it with a brand new drive running a verified to be good cloned disk image AND have almost the exact same boot issues on the new drive that I had on the old one?
I have taken my original OS drive and hooked it up to external cases and sata-to-usb adapters to make sure that it was actually dead and it is. It will not spin up properly and makes lots of clicking noises. However, having a similar boot issue with a brand new drive has me worried something may be wrong with the Mac Pro hardware also. The new OS drive ran fine for a few days and only had these problems today.
Any guesses?

Here is my own "cookie cutter" template to this type of problem.
Insure your UPS is working properly and that you have 1300VA to start with.
Run Apple Hardware Test of course.
CCC has been updated so make sure latest (it auto checks probably already).
Do you have Windows? run diagnostics from there, much better.
I settled on WD drives and use WD Diagnostic and has saved a drive.
Avoid Barracudas, seems even their 1TB is also suffering early failures (the 1.5TB was suffering from firmware problem).
Check for reviews and drive upgrade DB on AccelerateYourMac.
http://www.xlr8yourmac.com/
I know the F1 got a lot of early praise but they aren't compatible with Apple Pro RAID card and may have other issues.
If you want a fast low-cost drive, WD Cavair 640GB $69.
http://www.barefeats.com/harper14.html
Hitachi E7K1000: http://techreport.com/articles.x/16130/10
http://www.tomshardware.com/reviews/hdd-terabyte-1tb,2077-8.html
I have seen more than a couple of similar stories from people going away for 1-2 weeks and coming home to system that won't work properly. Hopefully people shutdown and unplug, or shutdown and have UPS, but it is strange to say the least.
Resetting SMC is a good idea but best done with 2008 model by leaving it unplugged for a full night 8-12 hrs. and not just 5 minutes. contrary to Apple tech article. For yours, there is a small physical button accessed by pulling drive tray #4 (easier to see if it is on its side and you have flashlight!)
http://support.apple.com/kb/HT1806
http://www.apple.com/support/macpro/

Failed to issue COM RESET successfully after 3 attempts. Failing...

Just in case anyone else has this problem, and wants to claw their eyes out.
I upgraded the Hard Disk in my MacBook Pro about four days ago (the new MBP, summer 2009 with SD card). I installed a Hitachi Travelstar 7K320. It worked awesome for about four days, until I went to run the EFI Firmware Update this morning.
My machine stopped booting. I held Command-V to get the verbose boot output, and eventually got the message: Failed to issue COM RESET successfully after 3 attempts. Failing... - which is where the boot halted.
I removed the Hitachi and restored the stock drive, and the laptop now booted fine. I think it's something Apple will have to look into.

I believe posting relevant facts is productive, & a very relevant fact here is that you are trying to use a drive with an interface (SATA-II) that Apple does not currently support in its laptops.
SATA-I controllers are supposed to be compatible with SATA-II drives, but many of them are not. The problem is how some controllers implement auto negotiation, which is supposed to tell the drive to fall back to SATA-1 speeds with the slower controllers. Some SATA-II drives have a jumper to force the slower speed if auto negotiation doesn't work; some do not.
How this compatibility problem came about, & why the jumper is required, is complicated but the short version is that at least four different specification bodies had some responsibility in producing SATA specifications, & not all controllers were designed to the same standards. This includes not just the controllers Apple has been using but those in many PC's as well.
So I agree that Apple dropped the ball, but not necessarily the way you might think: it should have made it very clear that the firmware update implemented an unsupported interface speed, that it might cause problems, & (most importantly) provided a reversion strategy to the former firmware if it did.
Hopefully, Apple will take another 'swing' at this & either provide that reversion strategy or a new update that at least allows the controller to work more reliably with the faster interface. But until then, unless your drive has the jumper, my previous suggestion is probably the best you can do.
BTW, none of the current mechanical drives available for laptops can saturate a SATA-1 bus except for brief bursts from the drive's buffer, so the real loss in performance of running a single SATA-II drive at SATA-1 speeds is almost negligible, something you might notice in a benchmark but not in real-world use.

10.6.6 update failed/booting issues

Similar Messages

Maybe you are looking for