You can make a difference in the Apple Support Community!
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.
It's done it ever since upgrading to High Sierra in January. After setting a reminder in iCal to open a Save As window in an app, I now cancel the shut down every time, unless i get busy elsewhere. Then it shuts down; no restart; no message; just an otherwise normal shutdown. Anyone know of a way to stop it from shutting down every night?
MacBook Pro
Have you done a PRAM reset, CMD+Option+p+r...
http://support.apple.com/kb/HT1379
In fact, do 3 in a row, takes a bit of time.
Intel-based Macs: Resetting the System Management Controller (SMC)...
Yup. It shut down on 3 different nights while in my admin account. So it's not account specific. But there's more. Believe it or not, it seems to be replicating. I discovered that once in a while it doesn't shut down. So one such time, I disabled the automatic system time and turned the clock back to 9:00 or earlier, maybe back to 8:55, to see if it would shut down.
After several times turning it back and saving it, it never shut down. But since then, I now get the shutdown notice at 9:05 AM (12 hours & 4 minutes after the PM one) asking me if I'm sure I want to shut it down, and that it will in 1 minute if I don't cancel it. So now I have to cancel that one every day too, as well as the one at night.
I'd like to wait on doing a PRAM reset till after your response to this post. Here are the lines from two PM shutdowns and an AM shutdown. Hopefully I included enough lines before the shutdowns started. Let me know if I didn't. Why the AM one shut down at 9:15, I don't know. But I always get the notice at 9:05 AM.
Maybe the Set a startup, wake, sleep, restart, or shutdown time on your Mac automatic shutdown is enables?
Thanks. But no. It's not. If it were, it would ask me to confirm the shutdown. But as I forgot to mention (sorry about that), it just shuts down without asking me first, unless I cancel it with an open Save As window. Any other idea(s)?
If you have a second account and logout and login as the second user, does it still shut down? In other words wonder if the shutdown is account specific? If it doesn't do, then perhaps you have some sort of utility in the first account that is doing on its own via a cronjob or some sort of automated launch daemon or ???
Also, look in the system.log file and see if there are some funny messages that happen right about that time that might give some hints? system.log is located in the /var/log folder or /private/var/log if you would rather. You can look at this file with TextEdit or any other editor you prefer.
Good luck...
Post the EtreCheck data, opening a new reply here and pressing the button that looks like a printed page to get a text input box big enough to paste the hardware and software configuration report here.
Well, very strange behavior it seems. The "loginwindow" process is declared dead and then system seems to be shut down. What is killing the loginwindow process is not apparent. right before this happens "loginwindow" starts killing processes, but why have no idea.
I would take a look at all the items in the various system level launchd queues since you say the shutdowns are occurring for multiple accounts, correct? Your statement about how it shut down on your "admin" account seems confusing, as by default first (and usually only) account is always an admin type account, so do you normally have a second non-admin account you usually use? And the shutdowns are occurring in both of these? Do a "man launchd" in a terminal window to see some places to start looking (see FILES at the end of man page).
It appears there is some sort of cascade of events that precede the actual shutdown, all of which seem odd to be happening in the middle of normal operations. I would guess that some automatic/launchd based script is killing something it shouldn't be and that results in a series of events which ends in killing loginwindow itself, which normally would just cause you to abruptly be logged out, not cause the shutdown, so that is also weird. Have you had any system crashes that might have corrupted something on the disk? What is the result of the Terminal command:
sum /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow
On my High Sierra system build 17G8030 (you get this build number from "About this Mac" and then click on the version string under "MacOS High Sierra) it is:
30741 1230 /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow
This is just a WAG, but if you have a different checksum, then don't know what other choice you would have other than a refresh of the system.
Also items that would seem to suggest more investigation are:
com.apple.xpc.launchd.user.domain.501.100115.Aqua
com.myJob.agent
and several others -- just look at your log and check things that give errors.
you seem to have a few of system level utilities/enhancements installed that might be old and no longer supported in High Sierra?
Good luck...
Safe Boot from the HD, (holding Shift key down at bootup), does the shutdown occur in Safe Mode?
Etrecheck report could help a lot.
High Sierra Shuts Down Every Night At 9:01