Use this guide when a desktop application does nothing when selected, opens and immediately closes, freezes, repeatedly shows "not responding," or crashes during one task. This article covers locally installed Windows and Mac applications. If only a website is affected, report it as a browser or service issue instead.
Stop if the application displays an unexpected request for a password, MFA code, recovery key, payment, security-software removal, or remote access. Close the prompt if safe and contact support. Also stop if the crash follows a suspicious attachment, unknown download, or unusual encryption or ransom message. Do not keep reopening a program that is actively changing or corrupting important files. If the computer becomes extremely hot, smells burnt, or shows battery swelling, shut it down safely and follow the hardware safety process.
Identify the scope. Confirm the application's exact name and whether other approved applications open normally. Note whether it fails at launch or only after a specific non-sensitive action. Do not test with confidential or irreplaceable files.
Wait, then close it once. Give the application up to a minute to respond. In Windows, use Task Manager only to end that specific unresponsive app. On a Mac, use Apple menu, Force Quit. Reopen it once after it fully closes. Repeated relaunching can create more temporary files or repeated failed transactions.
Restart the computer normally. Save work in other applications first. A normal restart clears a stuck process and pending application state. After restart, open only the affected application before reconnecting optional docks or accessories.
Check whether a service outage is involved. If the app requires a company or cloud service, check the vendor's official status page or your internal service notice. Avoid third-party outage pages that ask you to sign in.
Check approved updates. Use the application's built-in update command, Microsoft Store, Apple App Store, Windows Update, macOS Software Update, or your organization's software portal. Do not download an installer from an advertisement, file-sharing site, or search result that is not the verified vendor.
Try a safe, blank test. If the app opens, create a new empty document or use its default start screen. If that works but one file triggers the crash, stop testing that file and report the distinction. Do not upload the file to public repair sites or attach it to a ticket unless support provides an approved secure method.
Check simple resource conditions. Close unused applications and confirm the device has reasonable free storage using built-in Settings or System Settings. If the app uses an external device, disconnect that device, restart the app, and note the result.
Use only built-in repair options. In Windows, Settings, Apps, Installed apps may offer an app-specific Repair option that attempts to preserve data. Use Repair only if your organization permits it. Do not select Reset or uninstall unless support approves. On a Mac, follow the app developer's documented steps and contact support if restarting and updating do not help.
Do not erase or reinstall the operating system, edit the registry, delete system folders, run compatibility hacks, install unapproved cleaners, disable endpoint protection, or remove organization profiles. Do not reinstall or reset a business application without approval because local settings or unsynced work may be lost. Never provide passwords, MFA codes, recovery keys, customer data, or confidential files.
Escalate immediately for a suspicious security prompt, ransomware message, or possible data corruption. Contact support if a business-critical app cannot open, crashes after restart and approved updates, affects multiple users, fails only with a required file or device, or shows an error code. Preserve the error on screen if safe, but do not include sensitive document contents in a screenshot.
Provide the computer asset tag, operating system, application name and version if visible, exact error text, date and time, whether other apps work, whether a blank test works, and the last non-sensitive action before the crash. List the numbered checks attempted and any recent approved application change. Attach a screenshot only after checking that it contains no customer data, credentials, confidential filenames, or private messages.