OS X :: IWork 09 Update Completely Crashes MacBook

Bought and downloaded iWork '09 March 8 from authorised Apple reseller in Hong Kong, used it for a week. loaded software onto white MacBook 13'' 2.16Gz. machine is now 7 months out of the standard 1-year warranty (meaning I've owned the machine for 1 year and 7 months). Apple Auto Update cued update for iWork '09 (Pages, Numbers) on March 13, which I authorised for it to download. Left and came back to computer, which does not turn on. Tried resetting PRAM, SRAM, doesn't work - completely crashed, light next to IR port does not turn on, battery does not charge, but power adapter lights up green when connected. Went to CASE, in Mongkok (Hong Kong), over the weekend.

3rd party service contractor of AppleCare HK, which takes care of hardware problems. The counter rep said it will cost me HK$600 (US$100) just to examine the problem because the machine is out of warranty. I kicked up a fuss. he finally gave it a cursory look, say something is wrong with logic board and says they will have to charge me HK$10,000 (US$1,200 = which equals new aluminum MacBook) to fix it. But they said i should wait to speak to a Customer Service rep on Monday to see what more could be done. So I went home, took out the hard drive and put it into an external hard drive (SATA) case. Over USB, backed up my critical user files onto another macbook. There were "stop signs" overlaid my file folder icons, I clicked on them, opened them up, transferred these files onto another external drive.

I returned original hard drive into unbootable macbook (apparently this should have fixed it), did not try to power up one last time (see below). Called up AppleCare Customer Service on Monday (see below); they were helpful. At CASE (AppleCare's 3rd party contractor), technician pushed power button and to my utter amazement, the computer turns on. screen shows the machine was just about to restart - it was stuck on Apple Update, which has just finished downloading for iWork 09. The technician says actually I am the second person to have this problem - the other person was installing updates for iLife '09. Technician also says this has never happened before iLife or iWork 09.