What is loginwindow, and why is it running on my Mac?
Last reviewed: 19 November 2026. Path, account, launchd job and Force Quit window code checked on macOS 26.3.1.
loginwindow is the macOS process that shows the login screen and then manages your login session, including logging out, restarting, shutting down and the Force Quit Applications window. It is normal for it to run all the time and sit near 0% CPU. Do not force it to quit: that ends your session and closes your apps without saving.
loginwindow at a glance
| loginwindow | |
|---|---|
| Made by | Apple (part of macOS) |
| Type | System app (login session) |
| Location | /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow |
| Runs as | your user |
| Started by | launchd job com.apple.loginwindow |
| Bundle ID | com.apple.loginwindow |
| Can you quit it? | No. It manages your login session; forcing it to quit ends the session. |
What is loginwindow?
loginwindow shows the screen where you pick a user and enter a password. Once you log in, it stays running for your session and handles session events: logging out, restarting and shutting down (asking each app to quit and showing which ones refuse), and the Force Quit Applications window you open with Option-Command-Esc. The Force Quit panel's code is part of the loginwindow app.
launchd starts it from the com.apple.loginwindow job in /System/Library/LaunchDaemons, and during your session it runs as your user. It is one of the processes macOS needs to run, along with launchd and WindowServer.
Is loginwindow safe?
Yes. loginwindow is part of macOS, signed by Apple, and lives in /System/Library/CoreServices on the read-only system volume. It is expected to be running whenever someone is logged in.
Why does loginwindow use so much CPU?
- Logging out, restarting or shutting down. When you log out or shut down, loginwindow asks each app to quit and waits for them, which shows as activity until the session ends.
- The Force Quit window. Opening the Force Quit Applications window and force quitting an app is handled by loginwindow.
- Logging in. Right after login, loginwindow sets up the session and starts the apps that open at login.
- Locking and fast user switching. Locking the screen and switching between users bring the login screen back, which loginwindow draws.
How much CPU is normal for loginwindow?
At or near 0% CPU during normal use. Short activity at login, logout, lock and unlock, and when the Force Quit window is open, is expected.
Memory use is typically in the tens of megabytes.
What can you do if loginwindow is busy or the Mac will not log out?
- Find the app that blocks logout. If logout or shutdown stalls, loginwindow is waiting for an app to quit. Look for an app asking to save changes, save or cancel, then try again.
- Force quit the app, not loginwindow. Press Option-Command-Esc, select the app that is not responding, and click Force Quit. Leave loginwindow itself alone.
- Reduce apps reopened at login. If login is slow, remove items you do not need in System Settings > General > Login Items & Extensions, so fewer apps open as your session starts.
- Restart the Mac. If loginwindow stays busy during normal use, save your work and restart from the Apple menu. That starts a fresh session.
When should you worry about loginwindow?
Look closer if loginwindow stays above a few percent CPU for many minutes during normal use, outside login, logout or locking. A restart usually clears it.
There should be one loginwindow per logged-in user, running from /System/Library/CoreServices/loginwindow.app. A copy elsewhere would not be Apple's.
How do you check loginwindow in Activity Monitor and Terminal?
Open Activity Monitor (Applications > Utilities), and type loginwindow in the search field. The CPU tab shows its % CPU. Double-click the row for its parent process, memory details and open files.
In Terminal, the first command lists every loginwindow process with its PID, user, CPU and memory (RSS is resident memory in kilobytes).
ps -axo pid,user,%cpu,%mem,rss,command | grep -F 'loginwindow' | grep -v grep
How can Thrum help with loginwindow?
Thrum keeps a live CPU graph in the menu bar. One click shows the eight processes using the most CPU, so you can see when loginwindow is among them and how much it takes. An optional alert tells you when a process stays above a CPU level you choose (50 to 200% of one core) for 1 to 10 minutes. Thrum lists loginwindow but has no Quit button for it, because macOS needs it to run.
Thrum is $4.99 once with a 14-day free trial and no account. It requires macOS 26 Tahoe on Apple silicon or Intel.
Questions about loginwindow
Can I quit loginwindow?
No. It manages your login session, and forcing it to quit ends the session and closes your apps without saving.
Why is loginwindow running when I am already logged in?
It stays running for the whole session to handle logout, restart, shutdown, the lock screen and the Force Quit window.
Is the Force Quit window part of loginwindow?
Yes. The Force Quit Applications window you open with Option-Command-Esc is part of the loginwindow app.