In Mac OS X Lion, when I do Apple > Shut Down, there is a checkbox that says "Reopen windows when logging back in".

Even though I constantly UNCHECK the box, it seems OS X doesn't care - and still opens some Finder windows and sometimes Chrome...

How can I turn this feature off?

  • 2
    In System Preferences > Users & Groups > Login Items, is Chrome set to open at login? In Snow Leopard, I know Finder windows were restored at launch, but Chrome windows are a mystery. Commented Aug 7, 2011 at 15:03
  • You were right about Chrome, it was in the login items, I don't know how it got there...
    – nute
    Commented Aug 10, 2011 at 7:16
  • I added that as an answer so you can mark your question as successfully answered. Commented Aug 10, 2011 at 14:12
  • Perhaps is our old friend GoogleSoftwareUpdate ? I bet Chromium does not do that .... :\
    – chiggsy
    Commented Aug 12, 2011 at 3:15
  • Unchecking "Reopen windows when logging back in" really just disables reopening applications. When applications are reopened either manually or as login items, their state is still restored. (Even if Resume was disabled in the General preferences and application state wouldn't normally be restored.)
    – Lri
    Commented May 10, 2012 at 18:25

5 Answers 5


Be sure that Google Chrome isn't included in System Preferences > Users & Groups > Login Items.

Also, Finder windows restore by default regardless, as they did in Snow Leopard.


For the record, we’re talking about this:


The problem is that OS X doesn’t remember if you uncheck the checkbox on the last shutdown — it will always keep the checkbox checked by default on subsequent shutdowns.

I found two different solutions for this problem, that seem to do the trick, although they aren’t ideal.

Open Terminal.app and enter the following commands:

defaults write com.apple.loginwindow TALLogoutSavesState -bool false
defaults write com.apple.loginwindow LoginwindowLaunchesRelaunchApps -bool false

This effectively disables the “reopen windows when logging back in” option, although the checkbox will still appear to be checked. You can just ignore it.

I’m afraid there’s no better solution, at least not at the moment.

Update: OS X 10.7.4 fixed this — it now remembers your selection:

  • 1
    It seems Mountain Lion fixed the issue
    – nute
    Commented Mar 22, 2012 at 10:57
  • @nute So does Mountain Lion remember your selection, or does it respect and remember the TALLogoutSavesState setting? It’s a neat improvement either way! Commented Mar 22, 2012 at 11:01
  • 2
    It remembers my checkbox selection.
    – nute
    Commented Mar 25, 2012 at 11:13
  • This hack resulted in some graphical glitches on my MBP 8-2 every time I logged in! This other solution on the other hand was fine.
    – gentmatt
    Commented May 15, 2012 at 11:00

This bug has been fixed with the Lion update 10.7.4:

The OS X Lion v10.7.4 Update includes fixes that:

Resolve an issue in which the "Reopen windows when logging back in" setting is always enabled.

enter image description here

(click here for more information)


Do you ever want applications to restore to their closed state, or just at startup? If you want something resembling pre-Lion behavior (i.e. not picking up where you left off), try this.

Back up your system before trying this, in case it messes anything up, but I'd recommend this procedure: In the Finder, press Command-shift-G for "Go to the folder:" then type "~/Library/Saved Application State/" (without the quotes). Delete all the folders in Saved Application State, then press Command-I to Get File Info. In the Get File Info window, check the "locked" box. This should keep applications from restoring their state.


The only thing that actually ever worked for me (MacOS 13.4 or similar) is to find the file:


Your file will have a different UUID for every user.

Empty this file: echo "" > ~/Library/Preferences/ByHost/com.apple.loginwindow.<UUID>.plist

And then make it unwritable: sudo chown root ~/Library/Preferences/ByHost/com.apple.loginwindow.<UUID>.plist

This ensures a predictable login time and makes a reboot do what it was designed to do: clear the current state of the computer. I know this thread is old but I am sure that someone else will benefit from this knowledge. I wish I could have found out the easy way.

  • 2
    This is what solved it for me, and just to be certain it hopefully sticks, I used sudo chmod 000 and sudo chown nobody:nogroup on this. It's been bugging me for ages that nothing else stuck.
    – Josh
    Commented Jun 28, 2023 at 5:48
  • I tried this and it helped but somehow Tuple still launched at startup, despite not being in this file, in the login items in my user account settings, and not having its own launch at startup setting checked. Is it just me or has this always been one of the most hard to control things in macOS?
    – Andy
    Commented Oct 20, 2023 at 20:31
  • Double check using something like launchcontrol (free version should work), or check launchctl list, that sounds like it starts at login instead of relaunching.
    – Josh
    Commented Oct 27, 2023 at 15:27

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .