Why the desktop comes back by itself
Finder is not optional. macOS keeps it running, so when it quits the system starts it again within seconds. The blink you see is the restart, and it means the crash already happened.
Finder also depends on other programs — add-ons from other apps, and every disk it lists. A crash is often not Finder's own fault, which is why the cause is usually found by asking what Finder was waiting on at the time.
An add-on from another app
Crashes started after installing or updating cloud storage, an antivirus tool, or a file utility. They happen in ordinary folders with nothing unusual in them.
Apps that show sync badges on your files, or add menu items when you right-click, do it with an extension. Each extension runs as its own separate program, so one crashing does not drag Finder down with it. What does is Finder waiting on an extension that has stopped answering.
Fixin System Settings, open General, then Login Items & Extensions, and look at the Finder extensions listed there. Turn off the most recently installed one and use the Mac normally for a while before turning it back on.
Turning extensions off one at a time is slower than turning off all of them, and it is the only version that tells you which one was responsible.
A disk or share that stopped answering
Crashes coincide with connecting an external drive, waking the Mac, or opening the sidebar while a network share is listed but offline.
Finder waits for a volume to answer. A failing external disk, or a network share that has gone away without being ejected, can leave it waiting long enough that macOS ends it.
Fixeject anything you do not need, and remove offline network shares from the sidebar rather than leaving them listed. If the crash follows one specific drive, that drive is the subject, not Finder.
One folder that always does it
Finder is stable until you open one particular folder, and then it fails every time.
Each folder stores its own layout — icon size, sort order, window position — in a small hidden file inside it. If that file is damaged, opening the folder reads it and fails.
Nothing in the folder is lost. Only the remembered layout is.
Fixopen the folder's enclosing folder, delete the hidden .DS_Store inside the problem folder, and reopen it. Finder writes a fresh one and the folder returns to default view settings.
What Noah can determine on this Mac
NoahNoah can read the crash reports macOS already wrote, check which volumes are mounted, and see whether the same failure repeats or happened once.
That difference matters: a single crash after a system update is usually not worth acting on, and a repeating one names its own cause in the report.
The short version
- The desktop reappearing is macOS restarting Finder, not a second crash.
- Crashes after installing a sync or utility app: check Finder extensions first.
- Crashes around a drive or network share: the volume is the subject.
- Crashes in one folder only: its saved view settings, and nothing in the folder is at risk.
- One crash after an update is not a pattern. Repeated crashes leave a report that names the cause.