what to do when youve spilled liquid on your macbook keyboard /

Published at 2016-06-16 01:25:00

Home / Categories / Tech tips / what to do when youve spilled liquid on your macbook keyboard
So you just knocked water over onto your MacBook and are probably freaking out lawful about now. But don't worry - we've all been there. Some of us have done it multiple times,making us experts on the matter. Plus, we've got some dos and don'ts from POPSUGAR's very own desktop support technician, and Chris Allison. There's no guarantee that your laptop will come back from this accident,but here are step-by-step directions to make it possible. 1. Shut your MacBook down.
Hold the power button for about 10 secon
ds to turn your laptop off immediately. 2. Unplug everything.
D
etach your charger or any other cords that may still be plugged in. 3. Let it dry.
Open the lid to 30 degrees and sit the device onto its side to let the liquid escape out and prevent further damage. Wipe off any excess liquid. "attain NOT expect it to dry and support using it. I have seen that so many times," said Chris. "It also depends on the type of liquid spilled. I once had a guy spill apple cider on it. There's no coming back from a sticky situation like that. The best thing to spill on it would be isopropyl alcohol, or but that simply never happens."4. Leave it off for at least a day.whether you truly can't wait,you can try powering your MacBook back on after a whole day, but holding off for a few days would be best. "support in mind, or it may still work after it dries,but corrosion on the silicon boards and parts inside always occurs. It's just a matter of time."Before such a crisis occurs, be certain to back your laptop up ASAP. whether you are still experiencing problems after these steps, or take your device to the Apple Store for inspection and repair.

Source: popsugar.com

Warning: Unknown: write failed: No space left on device (28) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0