CUI CUI CUI error 10.7.3 all apps crashes

So I've been on the phone with tech support. I'm the only one who called in and didn't fix it myself. So they were pretty happy about that. They had me send in a bunch of logs so they can find out what's causing the issue. The reason it wasn't caught in the dev releases is because it was all done by manual installations. There is some folders that that the software update does not rewrite and therefore the manual update rewrites some of these folders thus fixing anything that had been corrupted.

So currently I put an sd card 16gb into the computer. Booted into recovery mode(option+r as soon as the computer turns on) then open disk utility. Select sd card. Partition it as Mac (journaled) after thats done close out of disk utility then select install lion. Install it onto the sd card. Takes awhile. Then load into lion on the sd card. Open safari and download combo (I downloaded it onto a flash drive on another computer, not a Mac) then run the combo update but select original hard drive to install it on.

I'm just now running the combo update and will update this after its done with the results.

Also tech support said the new software update version as of today shouldn't cause this issue.

Tom Dignam wrote:

A four hour reinstall from a Time Machine back up is rediculous. A clone of your system would have had you up and running in 5 minutes. Take the time to clone your working system to an external drive. You can still use Time Machine for emergency back up of your cloned HD. Use the clone to reformat and do a clean install and update/upgrade of system.

You'll be back up but it will still take hours to restore something to your old boot drive, whether it's a new install or a clone of your bootable clone.

It's great to have a bootable backup, but unless you want to keep booting from it, you've work to do.

Had "the problem" on my early 2011 MBP. I didn't want to restore from TM since I had finished more than a few important projects at work that hadn't been backed up yet. What worked for me was rebooting into the recovery partition and reinstalling Lion. That put me back to 10.7.2, whereas I was able to once again open Safari without crashing and download the Combo updater and it installed fine. I even feel a little better thinking I now have a "cleaner" install of lion...

I've applied this update to about 25 iMac's and 4 MacBook Pro 15" over the past day, no issues like this so far.

But I have repaired the permissions on every machine before I did the update, same as I always do before applying ANY system update.

Maybe Apple should repair the system permissions BEFORE the installer does it's update.

Be interesting to see what the difference is between the combo update and the main update, it's quite possible that the combo update does nothing different, just the fact that doing a Time Machine restore fixes the permissions in the process.

But I have repaired the permissions on every machine before I did the update, same as I always do before applying ANY system update.

Maybe Apple should repair the system permissions BEFORE the installer does it's update.

I've only done four Macs, but I've never Repaired Permissions. For any update or upgrade. ever.

I've got another 25 iMac's to do tonight.

I've been supporting the Macs at the school for the past 3 years, we used to see random results in performing major system updates, sometimes all would be 100% OK, other times we would get random freezes.

This could have been down to the third party drivers for the M-Audio components, but since I've been following the routine as outlined below, In the past 2 years I've never had an issue:

1. Reboot the machine

2. Repair Disk Permissions.

3. Install the update through Software Update.

4. Test

The only thing that I've added in the past 2 years is step 2.

It only takes a few minutes to do and can be done while downloading the installer, but it does seem to stop any grief from happening.

I've probably cursed the project, lets hope all goes well tonight.

"............

You'll be back up but it will still take hours to restore something to your old boot drive, whether it's a new install or a clone of your bootable clone.

It's great to have a bootable backup, but unless you want to keep booting from it, you've work to do........"

Therein to dispell the myth of no work to do. While the Mac is by far the easiest of systems to administer there is still the chore of general houskeeping. For the "great majority" Apple Udates generally are seamless and function as intended. We can debate Time Machine vs Clone. My argument is intended to minimize downtime for the systems which require more than incremental Software Updates.

And users should be educated that System Updates are not ot be taken lightly even though Apple has successfully made it appear so. Many users will not back up or rely on simple Data Back Up ( Time Machine ) instead of insuring they have a complete bootable copy if their existing System. These precautions are not effortless and still not perfect. So far, it is the best possible insurance to avoid panic and lost productivity. A reasoned thought approach, taken in time will "almost" always assure a successfull outcome.

My rules which are commonly known: Always use combo updater; fix permissions and verify disk before, clone system (I use carbon copy cloner and time machine), wait a few days after update comes out to see how the "testers" have faired. Recommendations are often to also disconnect peripherals (e.g. hard drives) and boot in safe mode, but I don't. I've yet to apply 10.7.3 though, kind of wish it included ibooks 2 for mac or at least the nuts and bolts to run it if and hopefully when it comes out..

......Every thing hosed on my MB Pro. I am at work and cant restore. This freakin *****............... I knew when Jobs passed, somebody would freak Apple up........

What did "you do" to your set up? Maybe we can help.

I agree, this is the worst freaking thing ever, I am stuck all day with no dang laptop, because of a sorry coded update. Apple this is horrible. Guess I will be going back to Windows soon, cause apple is gonna go in the toilet again.

At least I can run Windows on the Apple hardware....Some consolation to the price I paid for this hardware.

Just installed the update when I got to work and got the notification. Totally hosed all the Apps, just like everyone else is saying. And my TimeMachine is 20miles away at home. Well this WAS gonna be a good Friday.....

At least I can run Windows on the Apple hardware....Some consolation to the price I paid for this hardware.

That's why you paid a premium. Apple let's you run Windows so you will be happy. So what's the problem again?

I've yet to see a "hosed" machine with this upgrade, am tempted not to do the permissions repair on some of the builds I'm doing tonight, see what exactly happens, and if one goes pop.

"Guess I will be going back to Windows soon, cause apple is gonna go in the toilet again."

That's not going to help!! The grass is nowhere greener on the other side of the fence, infact it's more of a yellow colour.

I've got the exchange server to do upgrades to this weekend, unlike the apple Mac OS X server where we feel confident to "just upgrade it", we have to plan and double plan with the windows box, as on several occasions it's failed when doing the upgrade. thankfully it's VMWare related and we are able to roll back to the snapshot, otherwise bang goes my weekend.

We've had windows 7 machines where updates have been authorised by WSUS to upgrade, only to come in on a Monday morning and find things haven't gone to plan.....

Doing the upgrade as I've said before has ALWAYS worked, and we've not had a machine that's been killed in action.

As a result, it's now the policy to apply patches to the mac's when they are released, give or take a day, but the windows patches are held off till half-term, or until they have been thoroughly tested, and then we are always a month or two behind.

This latest upgrade may have cause some a headache, and I would love to get my hands on a broken mac just to see what's happened.

Has anybody actually tried booting into the recovery console, running disk utility and then repairing permissions?

Well Tom, besides my MBPro being useless untill sometime tomorrow, and one out of 1000 using an Apple in a windows enviroment. Hmm. I have talked up Apple so much, and done some much to promote it, it is so dissapointing to have a hosed MacBook right now, I can't explain it. An I am just stuck without my favorite piece of hardware in world and can't do anything about it.... If I need to do my job today, Im going to have to RDP to a server from someones desktop to do it....

..........Well Tom, besides my MBPro being useless untill sometime tomorrow, and one out of 1000 using an Apple in a windows enviroment. Hmm. I have talked up Apple so much, and done some much to promote it, it is so dissapointing to have a hosed MacBook right now, I can't explain it. An I am just stuck without my favorite piece of hardware in world and can't do anything about it.... If I need to do my job today, Im going to have to RDP to a server from someones desktop to do it....

What did "you do" to hose the MBP? Don't you carry a bootable back up to work?