In this article
Separate the launch from the restored windows
An application starting after sign-in and an application restoring old documents are two different events. Before changing settings, identify which event you want to stop.
| What you observe | First control to check | What the observation does not prove |
|---|---|---|
| Previously open apps return after sign-in | Reopen windows when logging back in | That each app has a login-item entry |
| Old windows return after you manually open an app | The macOS window-restoration preference and the app's own settings | That the app launched automatically |
| One app starts at every sign-in | Open at Login and that app's startup settings | That removing one entry covers every helper |
| A process appears in Activity Monitor without a window | The process's identity and purpose | That a visible app window was restored |
Apple's reopening guide, published December 8, 2025, covers session restoration separately from per-app window restoration. An empty login-item list is therefore not a complete explanation of what will appear after sign-in.
This article focuses on the restored-session case. Our Open at Login versus background activity guide covers the two System Settings sections and their different purposes.
Use the normal confirmation dialog
When you are ready to restart or log out, save your work and use the ordinary Apple-menu command. In the confirmation dialog, clear Reopen windows when logging back in before proceeding.
Apple states that a forced restart, or using Option to bypass the dialog, reuses the most recent setting. That makes an emergency reboot a poor controlled test of a change you intended to make but never confirmed in the dialog.
Keep the scope of this option in mind. You are choosing whether to restore that login session. You are not removing applications, erasing their saved documents, or configuring every application's independent startup behavior.
If the symptom follows only an unexpected shutdown, write that down separately. Combining “after a planned logout” with “after the Mac froze” can hide the circumstance that matters most. A support report should identify which path produced the unwanted result.
Closing a window can leave the app open
Before your next test, distinguish closing from quitting. Apple's Quit apps guide explains that the red close button closes an app's window, while App Name → Quit or Command-Q quits the app. A dot beneath the Dock icon indicates that an app is still open.
That is why “I closed everything” can be an ambiguous troubleshooting note. Record whether you closed the last visible window or actually quit the application. Do not rely on an empty desktop as your only evidence.
For the separate problem of old windows returning when an app is opened, Apple places Close windows when quitting an application in System Settings → Desktop & Dock on macOS Ventura and later. This is a window-restoration preference, not a replacement for the restart-dialog choice. App-specific settings may also matter.
Run a one-app check you can interpret
The following is an original diagnostic worksheet based on the distinctions above. It is a protocol for your next suitable sign-in, not a claim that we restarted a test Mac or verified every app's behavior. Do not interrupt active work merely to complete it.
Choose one affected application. A report such as “everything comes back” is harder to investigate than one named app with a repeatable trigger.
- Record the baseline. Note the app name, version, macOS version, whether the app is running, and whether it appears in Open at Login. Note any app setting that explicitly mentions startup or reopening windows.
- Name the expected result. For example: “After signing in, this app should not open until I choose it.” This avoids confusing a hidden process with an unwanted window.
- Change one control. At a planned normal logout or restart, clear the session-restoration checkbox. Leave unrelated helpers and preferences alone for this trial.
- Observe before interacting. After sign-in, note whether the application opens before you click its Dock icon, open one of its documents, or start another app that could call it.
- Test manual reopening separately. If the app stayed closed, open it deliberately and note whether old documents return. That is a second event with a different setting to investigate.
- Keep the result bounded. Record what happened once. Repeat only if the result is inconsistent or another controlled change needs verification.
The value of this worksheet is the order of observations. If you open a document immediately after login, you can accidentally supply the launch trigger you were trying to investigate.
Interpret the result before disabling anything else
| Result of the check | Useful next step |
|---|---|
| App stays closed until manually opened | The unwanted automatic launch did not recur in this trial |
| App stays closed, then restores windows on manual opening | Review window restoration and the app's own document or tab settings |
| App opens before any interaction despite the normal-session check | Review a separate startup trigger; retain the exact sequence for support |
| Only an unfamiliar process is visible | Identify its owning app before treating it as the same symptom |
| Mac had to be forcibly restarted | Record the trial as inconclusive for the intended normal-session comparison |
Apple's login-item guide explains how to remove a known item from Open at Login. Apply that to the item you actually intend to change. If the app is absent, check its own documentation rather than clearing unrelated background permissions.
A persistent helper needs identification, not a guess from its name. Our unknown background-item guide explains how to connect an entry to an application. A LaunchAgent file on disk also does not, by itself, establish that a service is running or what caused a window to open.
Match the control to the event: session restoration for the previous login session, window settings for content restored inside an opened app, and startup settings for a separate automatic launch. Keep those observations separate and your next change becomes much easier to evaluate.
