Pause before forcing it closed
If the application is exporting a large file, opening a complex project or performing another demanding task, allow reasonable time for that operation. Look for a progress indicator or a change in the output file rather than judging only the frozen window.
Check for a dialog hidden behind another window. A save prompt, permission request or missing-file message can make the main application appear unresponsive while it waits for an answer. Use normal window switching to inspect what is open.
Try switching to another application. If the rest of the computer responds normally, the problem is narrower than a complete system freeze. Save work in the applications that still function before taking further action.
Close the smallest thing necessary
Try the affected application's normal close command once. If it does not respond and you have decided the current operation is no longer progressing, Task Manager can end the application. Understand that unsaved work may be lost.
Do not end unfamiliar system processes just because they show activity. Identify the actual application and keep the action limited to it. A forced shutdown of the entire computer should not be the first response when one program is stuck.
After reopening, look for the application's recovery or autosave options. Save any recovered document under a new name until you have checked it. Do not overwrite a good earlier version immediately with a recovery file that may be incomplete.
Try to reproduce the cause safely
Work on a copy of the file and repeat the last few steps. If one document consistently triggers the problem while others do not, the file or a particular feature may be involved. If every document fails, the application installation or environment deserves closer attention.
Note recent changes such as an update, extension, plug-in or new peripheral. Temporarily disabling a known optional add-on through its supported controls can be a useful comparison. Make one change at a time and restore anything unrelated.
Check available storage and whether the system is under sustained memory or processor pressure. Microsoft's performance guidance describes several possible sources of slowdown, but none should be assumed to explain every freeze. Use the observation to choose the next check.
Escalate with a reproducible account
Install supported application updates when appropriate, after backing up important files. If the issue began immediately after an update, read the developer's known-issue notes and recovery guidance before attempting a rollback.
A useful support report includes the application version, operating system, file type, exact action and whether the problem happens in a new blank document. Include an error message if one appears. Share sample files only when permitted and after removing private information.
If the whole computer repeatedly freezes, restarts unexpectedly or reports storage errors, stop treating it as a single-app nuisance. Verify backups and seek device-level support. The aim is to preserve the work and identify the cause, not to become faster at forcing the same application closed every day.
