High Sierra killed my mac!

[Sparky1]

I just upgraded my 2012 MacBook Pro to high sierra, after the update it seemed fine then when I tried a restart, it would not load past the apple logo screen, after spending a few hours talking to apple help and a day trying to fix the issue, I wasn't getting anywhere. I went into an Apple store and the Genius Bar, I was told as it's a software problem it should be fine, three hours later I'm walking out of there with no laptop as it needs a new logic board at a cost of £558.00!

Luckily before my MacBook Pro was erased in the Apple Store I managed to back up some of my work through safe mode.

I don't understand that what should of been quite a straightforward procedure can turn into such a nightmare, I appreciate there are warnings in the T&C's about backing data up before an update but to completely break a machine that had no issues and was running smoothly!

Apple obviously washed there hands and said it's out of warranty.

Has anyone else had similar issues?

Best!

 

[HDFan]

I tried a restart, it would not load past the apple logo screen,

but to completely break a machine that had no issues and was running smoothly!

2 contradictory statements.

 

[maflynn]

Apple obviously washed there hands and said it's out of warranty.

So you want Apple to fix a 6 year old laptop for free.

The OS didn't break the laptop, if it did, then we'd be hearing a lot of others dealing with the issue. It could be just a coincidence that your Mac failed at the time you were updating.

The long and short of it, the laptop is 6 years old and doesn't owe you anything. Btw,I also have a 2012 machine and I would never install HS on it. Given the age, and relatively slow CPU, I'm using an older OS. The machine is stable, fast enough and problem free. Why risk introducing problems on such an old machine. ¯\_(ツ)_/¯

Personally, I'd not pay for a new logic board and just a new Mac at this point

I appreciate there are warnings in the T&C's about backing data

You should be backing up all the time

 

[casperes1996]

The OS didn't break the laptop, if it did, then we'd be hearing a lot of others dealing with the issue. It could be just a coincidence that your Mac failed at the time you were updating.

Yeah - It's very likely that the hardware was near a breaking point, and the heat associated with running the update scripts pushed it past it.

 

[maflynn]

Yeah - It's very likely that the hardware was near a breaking point, and the heat associated with running the update scripts pushed it past it.

That was my thinking, the heat generated from the install/usage was the final straw.

 

[Sparky1]

2 contradictory statements.

Not really as either way it's pretty useless now
[doublepost=1535196956][/doublepost]

Yeah - It's very likely that the hardware was near a breaking point, and the heat associated with running the update scripts pushed it past it.

Thanks for the info, I have read other users with similar issues on these forums
[doublepost=1535197094][/doublepost]

Yeah - It's very likely that the hardware was near a breaking point, and the heat associated with running the update scripts pushed it past it.

I just feel there should be more of a warning when updating the system on a mac, if there is I apologise as haven't seen it.
[doublepost=1535197752][/doublepost]

So you want Apple to fix a 6 year old laptop for free.

The OS didn't break the laptop, if it did, then we'd be hearing a lot of others dealing with the issue. It could be just a coincidence that your Mac failed at the time you were updating.

The long and short of it, the laptop is 6 years old and doesn't owe you anything. Btw,I also have a 2012 machine and I would never install HS on it. Given the age, and relatively slow CPU, I'm using an older OS. The machine is stable, fast enough and problem free. Why risk introducing problems on such an old machine. ¯\_(ツ)_/¯

Personally, I'd not pay for a new logic board and just a new Mac at this point


You should be backing up all the time

I'm not expecting anything for free, and the laptop in question is not used often, but if issues arise because of a software update without suitable warnings then I would expect the company to take some kind of responsibility. If there are suitable warnings and I haven't read them then I apologise.

 

[maflynn]

but if issues arise because of a software update without suitable warnings

I don't see how your computer finally dying, requires apple to take some sort of responsibility. I don't think the update's code, function or process did it, but rather it was just the program that was running that pushed the computer over the edge. It could have been photoshop, safari, iTunes, etc. After 6 years, the laptop failed.

At this point, I suggest instead of getting worked up, or angry, move on, whether that's with an Apple Mac, or a windows machine ¯\_(ツ)_/¯

 

[Sparky1]

I don't see how your computer finally dying, requires apple to take some sort of responsibility. I don't think the update's code, function or process did it, but rather it was just the program that was running that pushed the computer over the edge. It could have been photoshop, safari, iTunes, etc. After 6 years, the laptop failed.

At this point, I suggest instead of getting worked up, or angry, move on, whether that's with an Apple Mac, or a windows machine ¯\_(ツ)_/¯

Hi Mike

I'm not getting worked up or angry I just want to understand why what should of been a straightforward update has ended up costing me £558.00.

I have now read similar issues on these forums with upgrading to high sierra

Thanks for your time

 

[chabig]

I just want to understand why what should of been a straightforward update has ended up costing me £558.00.

It’s really simple. Your MacBook Pro was on its last legs. It would have failed anyway. The fact that you updated the software is in coincidental. Your trying to make an association where none likely exists, which is something humans tend to do erroneously. It could have failed while running Word, or iTunes, or anything else and you’d want to blame that software.

Things tend to break when they’re being used, and if they break when idle we don’t notice until we use them. The fan belt on your car breaks, but you don’t notice until you start the car. Your air conditioner failed, but you don’t discover it until summer. Your logic board is about to fail but it doesn’t actually go until you’re doing a software update.

 

[Sparky1]

It’s really simple. Your MacBook Pro was on its last legs. It would have failed anyway. The fact that you updated the software is in coincidental. Your trying to make an association where none likely exists, which is something humans tend to do erroneously. It could have failed while running Word, or iTunes, or anything else and you’d want to blame that software.

Things tend to break when they’re being used, and if they break when idle we don’t notice until we use them. The fan belt on your car breaks, but you don’t notice until you start the car. Your air conditioner failed, but you don’t discover it until summer. Your logic board is about to fail but it doesn’t actually go until you’re doing a software update.

Thanks for the advice if it was on its last legs it looks like the update finally pushed it over the edge.

 

[maflynn]

I'm not getting worked up or angry I just want to understand why what should of been a straightforward update has ended up costing me £558.00.

I understand your frustration and perhaps I was too quick to judge, I see too often people who expect apple to foot the bill on their misdeeds. I'm not saying your actions were wrong, but overall we do see a lot of folks here get mad that apple won't fix a computer out of warranty. I totally understand how the computer dying and needing to spend a lot of money to fix it can be unnerving.

 

[Fishrrman]

I don't think there's anything wrong with your MBP that you can't fix yourself.

It -might be- a failing hard drive or quite possibly a bad ribbon cable (that connects the HDD to the motherboard).

An important question, please answer before we can go further:
Can you boot to internet recovery?
To try this, press the power on button and immediately hold down "command-option-R" and keep holding it down.
You should get "the internet symbol" and you may have to enter the password for your wifi.

Can you get this far?

 

[lederermc]

OS upgrades can uncover a hardware issue that was oblivious to the prior OS version. Many years ago I had a SIM that was bad but not detected until an OS upgrade that checked memory for integrity. High Sierra did not brake your hardware... it was probably always broken.

 

[simonsi]

That was my thinking, the heat generated from the install/usage was the final straw.

No conspiracy needed, just random timing, after all computers are generally doing <something> when they break, statistically some % will be updating when they break, doesn't mean any kind of heat stress conspiracy is needed.

 

[tibas92013]

I plan on installing in the very near future "OS High Sierra" on my Mac Mini(MM Late 2014),2.8GHz, 8GB Ram, 256SSD which is presently on "OS Sierra".

I do not plan any OS upgrade to "OS High Sierra" on my other MM(Late 2012),2.5GHz,16GB Ram, 500 GB HD which is also presently on "OS Sierra"

 

[imasterus]

Btw,I also have a 2012 machine and I would never install HS on it. Given the age, and relatively slow CPU, I'm using an older OS. The machine is stable, fast enough and problem free.

Which OS do you use?