Protect what remains responsive
Save work in other open applications. If only one program is affected, avoid restarting the entire computer immediately. Check whether a hidden dialogue is waiting behind the main window, perhaps asking for a filename or a response to an error. Switching between the application's windows can reveal it.
If the document is stored on a disconnected shared drive or removable disk, restore that connection when safe. Do not unplug a drive that may be writing. Record the last action before the freeze, such as opening a particular file or invoking a plug-in. That detail will matter if the problem returns.
End the application only when necessary
Use the operating system's supported task-ending or force-quit control if the program cannot recover normally. Unsaved changes may be lost. End the affected application, not a collection of unfamiliar system processes. Reopen it and inspect any offered recovery document before choosing which version to keep.
Save a recovered file under a separate name initially. Compare it with the last saved version, especially after a large edit. An automatic recovery file may be recent without containing every action you remember. Confirm the important sections before overwriting either copy.
Find out whether the file or the program triggers it
Test the application with a small new document. If that works, try a copy of the problematic file so the original remains untouched. If all files trigger the failure, review official updates and the application's support guidance. Recently added extensions or templates can be relevant, but disable them through documented controls rather than deleting program folders.
When requesting help, include the program version, file type, last action and whether a fresh document works. Do not send a confidential file merely to demonstrate the fault; use a harmless reproduction or the support provider's approved secure process.
