How do I close a frozen Windows app without restarting everything?

First, save any work you can in other apps that are still usable. Avoid restarting Windows as your first move when the problem appears limited to one app.

For Microsoft Edge specifically, Microsoft Support says to open Task Manager, find Edge under Apps in Processes, choose End task, confirm it closed, and then reopen it normally. Ending the task closes the app, and the guidance does not promise that unsaved work will be recovered. [S1]

That is a documented Edge example, not a guarantee that every Windows app has identical controls or will recover the same way. If the frozen program is not Edge, note its name and what you see; do not assume the Edge steps are verified for it.

Yes. Before ending the frozen app, switch to other apps that still respond and save their open work. This protects work outside the frozen app from being lost if you later need to close or restart something.

For the frozen app itself, only save if its own controls respond. If they do not, do not assume that ending the task will preserve its unsaved changes: Microsoft’s Edge instructions describe closing and reopening Edge, but do not promise recovery of unsaved work. [S1]

A practical order is: save responsive work, note the frozen app’s name and what you were doing, then use the documented close steps if it is Edge. If it is another app, avoid selecting a process unless you can identify the intended app.

The cited Microsoft instructions verify the Task Manager steps for Edge only; they do not establish the exact steps or outcome for every other app. Treat them as an example, not a universal guarantee. If you use a close option for another clearly identified app, first save other work; unsaved work in the frozen app may be at risk.

If the freeze repeats, write down the app name, approximate time, what you were doing, what stopped responding, and what you tried. These notes help make a report clearer, but they do not by themselves identify the cause. Microsoft’s broader Windows freeze guidance recommends reviewing the System and Application event logs; it says an Application Error entry may be a sign of a crash or relevant system-process issue. That guidance is for broader troubleshooting, not a simple checklist that diagnoses every app crash. [S2]

Use this copyable note. Keep it factual and mark anything you do not know rather than guessing:

App: [name] Date and approximate time: [date/time] What I was doing just before it froze: [steps or task] What stopped responding: [visible behavior] Other apps still usable? [yes/no/unsure] Work saved in other apps first? [yes/no/not applicable] Action taken: [waited, closed app, other] Did the same freeze happen again? [yes/no; when] Relevant event-log entry, if reviewed: [System or Application; entry name; time; unsure]

For a repeated incident, event-log review is one way to preserve potentially useful troubleshooting details, not proof of a particular cause. Microsoft identifies an Application Error entry as a possible clue, not a definitive diagnosis. [S2]