When a Windows program suddenly shows “Not Responding,” the first reaction is often to open Task Manager and click End task.
Sometimes that is the right move. But if you do it too quickly, you may lose unsaved work or miss the reason the program became unresponsive in the first place.
A frozen-looking program may actually be busy processing a large file, waiting for a network location, communicating with another device, using a lot of memory, or waiting for a hidden dialog box. Other cases are genuine application crashes or system resource problems.
The goal is to determine which situation you are dealing with before ending the task.
This guide walks through that process for Windows 11 and Windows 10. Some settings and menu names can differ slightly between versions and applications.
First, Determine What “Not Responding” Actually Means
Not every apparent freeze is the same.
Before changing anything, look at what is happening.
The program is busy but Windows still works
If you can move the mouse, open other applications, and use the Start menu, Windows itself may be fine.
The affected program could simply be processing something in the background.
For example, it may be:
- Opening a very large document
- Exporting or converting a file
- Loading a large project
- Waiting for a network location
- Accessing an external drive
- Synchronizing data
- Performing a calculation
- Installing an update inside the application
If the program normally takes time during this operation, give it a reasonable amount of time before forcing it closed.
The program is completely frozen
If the window does not respond to clicks or keyboard input for an extended period and its behavior does not change, the application may actually be stuck.
This is when Task Manager becomes useful.
The entire computer is becoming unresponsive
If the Start menu, File Explorer, Task Manager, and other applications are also freezing, do not treat this as an isolated application problem.
The cause could involve:
- Very high CPU usage
- Memory pressure
- Disk activity
- Driver problems
- Storage problems
- Windows components
- Hardware instability
- A background service or application
In that situation, investigate Windows itself rather than immediately reinstalling the affected program.
Step 1: Check Whether a Hidden Window Is Waiting for You
One surprisingly common reason an application appears frozen is that it is waiting for a dialog box.
The dialog might be:
- A permission request
- A file overwrite question
- A sign-in window
- A warning message
- A confirmation prompt
- A request to select a folder
- A network authentication window
Press Alt + Tab to cycle through open windows.
Also check the taskbar for another window belonging to the same application.
If you find a dialog waiting for input, respond to it and see whether the main program becomes responsive again.
This is one of the safest checks because it does not terminate anything.
Step 2: Check Whether Windows Is Still Responsive
Before ending the program, try opening another application.
For example, press:
Ctrl + Shift + Esc
to open Task Manager.
If Task Manager opens normally, Windows is probably still responding even if the affected program is not.
You can also try:
- Opening File Explorer
- Opening Settings
- Switching to another application with Alt + Tab
- Opening the Start menu
If everything else works, concentrate your troubleshooting on the affected program.
If several Windows components are also frozen, the problem may be system-wide.
Step 3: Look at the Program in Task Manager
Open:
Ctrl + Shift + Esc → Processes
Find the affected application.
Do not immediately select End task.
Instead, look at its resource usage.
Pay particular attention to:
- CPU
- Memory
- Disk
- Network
High CPU usage
A program using significant CPU may still be actively working.
For example, video encoding, image processing, compression, compiling, or large calculations can temporarily make an application appear unresponsive.
If CPU usage remains high and the application normally performs demanding work, give it some time.
High memory usage
If the program is using a very large amount of memory, Windows may begin relying more heavily on virtual memory.
This can make the application and the rest of the system feel extremely slow.
Look at overall memory usage in Task Manager rather than judging the application alone.
If several programs are consuming large amounts of memory, close applications you no longer need after saving their work.
High disk usage
A program may appear frozen while Windows is performing heavy disk activity.
This can happen when working with:
- Large files
- Databases
- Virtual machines
- Video projects
- Photo libraries
- Cloud-synchronized folders
- Software installations
Check whether another process is responsible for the disk activity.
High network activity
Some programs wait for network resources before continuing.
This can happen with:
- Cloud applications
- Remote files
- Network drives
- Online databases
- Collaboration software
- Launchers and update systems
If the application is waiting for a network resource, ending it may not address the underlying problem.
Step 4: Check Whether the Problem Happens With One File or Everything
This is an important diagnostic test.
Suppose a word processor becomes unresponsive when opening one particular document.
Try opening a different document.
Or suppose an image editor freezes when loading one particular image.
Try a smaller image.
If the program works normally with other files, the problem may be related to the specific file rather than the application installation.
The same idea applies to:
- Projects
- Spreadsheets
- Databases
- Videos
- Images
- Browser profiles
- Game saves
- Plugins or add-ons
If only one file triggers the problem, do not immediately reinstall the entire application.
Step 5: Test Whether the Problem Is Reproducible
Ask yourself:
What was I doing immediately before the program stopped responding?
For example:
- Did I open a large file?
- Did I connect an external drive?
- Did I start printing?
- Did I switch networks?
- Did the program recently update?
- Did I install an extension?
- Did I change a setting?
- Did Windows recently update?
- Did I open a file from a network location?
Then try to reproduce the problem carefully.
If the program freezes every time you perform the same action, you have valuable diagnostic information.
A repeatable problem is usually easier to investigate than a random freeze.
Step 6: Check Available Storage
Very low free storage can cause broader Windows performance problems.
Open:
Settings → System → Storage
Check the available space on the drive where Windows and the affected application are installed.
If the drive is nearly full, free some space before continuing with more complicated troubleshooting.
Do not randomly delete Windows folders or application data just to create space.
Start with files you know you no longer need, such as unnecessary downloads or temporary files.
Step 7: Restart the Computer
If the problem happened once and there is no obvious cause, restart Windows.
A restart can clear temporary application states, release resources, and restart background services.
Use:
Start → Power → Restart
After Windows starts again, open the same program and test the same operation.
If the problem disappears and never returns, it may have been a temporary condition.
If it returns repeatedly, continue investigating rather than repeatedly restarting without identifying the cause.
Step 8: Check for Application Updates
If only one program keeps freezing, check whether the developer has released an update.
For a Microsoft Store application, open the Microsoft Store and check for available updates.
For a traditional desktop program, use the application’s own update mechanism or the software publisher’s official website.
Microsoft also recommends checking application compatibility and available updates when older applications behave incorrectly on newer Windows versions.
Avoid downloading unofficial “updated DLL” files or modified installers from random websites.
Step 9: Check Windows Update and Drivers
If several applications are freezing, or the problem started after a Windows or driver change, check Windows Update.
Go to:
Settings → Windows Update
Install available updates and restart when required.
If the affected program depends heavily on graphics, audio, networking, storage, or another hardware component, a driver problem can also be relevant.
However, do not download drivers from random driver websites.
Prefer Windows Update or the hardware manufacturer’s official support resources.
Step 10: Try the Program Without Extensions or Add-Ons
Some applications support extensions, plug-ins, add-ons, scripts, or third-party integrations.
These can sometimes cause problems after an application update.
If the application provides a safe mode, troubleshooting mode, or option to disable extensions, use that feature.
For example, if an application works normally without its extensions but freezes when they are enabled, you have narrowed the problem considerably.
You can then re-enable extensions individually rather than removing everything.
Step 11: Check Whether Security Software Is Interfering
Security software can sometimes affect how applications access files, folders, networks, or other protected resources.
If the freezing began immediately after installing or changing security software, investigate that connection.
Do not permanently disable antivirus or Windows security protections just to see whether the problem goes away.
Instead, check the security product’s notifications, quarantine history, or application-control settings.
If a legitimate program is being blocked, follow the security vendor’s documented procedure for handling the detection.
Step 12: Use Windows’ Repair Option When Available
For some applications, Windows provides a Repair option that can fix problems without requiring a full reinstall.
In Windows 11, try:
Start → Settings → Apps → Installed apps → select the application → Advanced options → Repair
Microsoft notes that not every application provides these options. If Repair is available, it can be tried before more disruptive recovery steps.
If Repair does not help, some applications also provide Reset.
Be careful with Reset.
Depending on the application, resetting can remove locally stored settings or application data.
Before using it, check whether the application stores important information locally.
Step 13: Check Reliability Monitor for a Pattern
If the program repeatedly freezes or crashes, Windows can provide useful diagnostic information.
Press:
Windows + R
Enter:
perfmon /rel
Press Enter.
This opens Reliability Monitor.
Look around the date and time when the problem occurred.
You may see application failures, Windows failures, updates, or other events.
The important question is not simply whether an error exists.
Look for a pattern.
For example:
The same application fails repeatedly shortly after the same update.
That is more useful than finding one unrelated warning from several days earlier.
Step 14: Check Event Viewer When the Problem Keeps Returning
For deeper troubleshooting, open:
Windows + R → eventvwr.msc
Then check:
Windows Logs → Application
Look for errors recorded around the time the program stopped responding.
Do not assume every warning or error is responsible for the freeze.
Focus on entries that:
- Occurred at the same time
- Name the affected application
- Reappear whenever the problem occurs
- Identify a faulting module or application component
Microsoft documentation uses the Application log to investigate application failures and unresponsive processes in Windows.
If you need help from the software developer, recording the exact time of the failure and relevant error information can make the report much more useful.
Step 15: Test With Another Windows User Account
If the application works correctly under another Windows user account, the problem may be specific to your normal user profile.
This can happen when an application’s user-specific settings, cache, configuration files, or permissions become damaged.
Do not immediately delete your original profile.
First use the second account as a diagnostic test.
If the application works there, investigate the application’s profile data before making destructive changes.
Step 16: Consider a Clean Boot for Persistent Conflicts
If the program works normally after a clean boot but freezes during a normal Windows startup, a background application or service may be interfering with it.
Microsoft’s clean-boot procedure starts Windows with essential drivers and startup programs so you can isolate third-party conflicts.
A clean boot is more advanced than simply restarting Windows.
If you use it, carefully record what you disable so you can restore normal startup afterward.
Microsoft also recommends returning Windows to normal startup once troubleshooting is finished.
Do not randomly disable Microsoft services.
Step 17: Check Whether the Problem Is Actually System-Wide
If several unrelated programs suddenly become unresponsive, investigate Windows itself.
Look for symptoms such as:
- File Explorer freezing
- Settings taking a long time to open
- Task Manager becoming unresponsive
- Extremely high disk usage
- Very high memory usage
- Frequent application crashes
- Windows restarting unexpectedly
- Blue-screen errors
- Problems appearing after a hardware or driver change
At this point, the affected program may only be the most visible symptom.
Windows includes built-in recovery and troubleshooting options that should generally be approached from less disruptive to more disruptive actions.
Step 18: Consider Windows System File Problems Only When the Symptoms Support It
If Windows itself is behaving incorrectly, built-in repair tools may be appropriate.
Microsoft provides DISM and System File Checker (SFC) for repairing missing or corrupted Windows system files.
Open Terminal or Command Prompt as administrator and follow Microsoft’s current instructions for the appropriate repair sequence.
Do not run system-repair commands simply because one application froze once.
If one program freezes while everything else works normally, the application itself is a more relevant place to investigate first.
When Should You Actually Click “End Task”?
Sometimes waiting is no longer useful.
Consider ending the task when:
- The application has remained completely unresponsive for a long time.
- Its resource usage is stuck rather than showing meaningful activity.
- Other applications continue working normally.
- You have checked for hidden dialogs.
- You have no important unsaved work that you still need to recover.
- You need to regain control of the application or desktop.
Open:
Ctrl + Shift + Esc → Processes → select the application → End task
Windows will terminate the application.
The main risk is losing unsaved work.
Some programs automatically recover recent work when reopened, but you should never assume recovery is guaranteed.
What to Do After Ending the Task
Do not immediately reopen the program and continue exactly where you left off without checking what happened.
Instead, ask:
Did the problem happen once, or is it repeatable?
If it happened once:
- Restart the application.
- Reopen the affected file if possible.
- Repeat the operation carefully.
- Watch Task Manager if the program becomes slow again.
If it happens repeatedly:
- Record what action triggers the freeze.
- Check Reliability Monitor.
- Check Event Viewer if necessary.
- Check application and Windows updates.
- Test without extensions or add-ons.
- Try Repair if available.
- Test another file.
- Test another Windows account if appropriate.
- Use a clean boot if a background conflict is suspected.
This turns a random freeze into a reproducible troubleshooting problem.
What You Should Not Do
Several common troubleshooting habits can make the situation worse.
Don’t repeatedly force-close the program
If the program is processing a large operation, repeatedly ending it does not solve the underlying issue.
Don’t immediately reinstall Windows
One frozen application does not normally justify a Windows reset or reinstall.
Start with less disruptive troubleshooting.
Don’t delete application folders randomly
An application’s folders may contain settings, licenses, databases, saved projects, or other important information.
Find out what a folder contains before deleting it.
Don’t download random DLL files
A missing-DLL message should be investigated through the application’s official installer, repair process, or publisher documentation.
Downloading replacement DLLs from unknown websites creates additional security and compatibility risks.
Don’t permanently disable security software
If security software appears to be involved, investigate its logs and settings instead.
Don’t change the Windows Registry without a specific reason
Registry edits copied from random troubleshooting websites can create additional problems.
A Simple Way to Find the Cause
You can narrow down most application freezes by changing one variable at a time.
| What you test | What the result can tell you |
|---|---|
| Another file | Problem may be file-specific |
| Another application | Problem may be application-specific |
| Another Windows account | User-profile issue becomes more likely |
| No extensions | Add-on conflict becomes more likely |
| Another network | Network dependency may be involved |
| After Windows restart | Temporary state becomes less likely |
| After application update | Version-related problem becomes more likely |
| Clean boot | Third-party background conflict becomes more likely |
| Reliability Monitor | Repeated crash pattern may become visible |
The purpose is not to try every possible Windows fix.
It is to find the smallest change that separates one possible cause from another.
A Practical Troubleshooting Order
If you want a simple sequence to follow, use this order:
1. Check for a hidden dialog.
2. Wait briefly if the program is performing a known heavy operation.
3. Check whether Windows itself is responsive.
4. Open Task Manager and inspect CPU, memory, disk, and network activity.
5. Test another file or operation.
6. Restart the program or Windows if necessary.
7. Check application and Windows updates.
8. Disable or test extensions and integrations.
9. Use Repair if Windows provides it.
10. Check Reliability Monitor for repeated failures.
11. Check Event Viewer for matching application errors.
12. Test another Windows user account if the problem appears profile-specific.
13. Use a clean boot if a third-party conflict is suspected.
14. Investigate Windows system problems only when other evidence points in that direction.
15. Reinstall the application only after simpler explanations have been ruled out.
This approach reduces unnecessary resets, reinstalls, and configuration changes.
How to Know You Have Actually Fixed It
A successful fix should do more than make the program open once.
Repeat the action that originally caused the problem.
For example, if the application froze while:
- Opening a specific file
- Exporting a project
- Printing
- Connecting to a server
- Using a particular extension
- Performing a large calculation
perform that same operation again.
Then check whether:
- The program remains responsive
- CPU and memory usage behave normally
- The operation completes
- The problem does not return after restarting Windows
- Other applications continue working normally
If the same action repeatedly causes another freeze, the problem is not fully resolved.
When to Contact the Software Developer
Contact the application’s developer when:
- Only that application is affected.
- The problem is reproducible.
- Windows itself appears stable.
- The application is updated.
- Repair does not help.
- The problem continues after testing without extensions.
- Other files or programs work normally.
When contacting support, provide useful details such as:
- Windows version
- Application name and version
- Exact action that triggers the freeze
- Whether the issue happens with every file
- Whether another Windows account has the same problem
- Whether the problem started after an update
- Relevant error messages
- Approximate time of the failure
- Reliability Monitor or Event Viewer information when appropriate
A precise reproduction path is usually much more useful than simply saying that the program “keeps freezing.”
Frequently Asked Questions
Should I always end a program when Windows says “Not Responding”?
No. A program can temporarily stop responding while performing a demanding operation. First check whether Windows is responsive, whether the program is using CPU or disk resources, and whether a hidden dialog is waiting for input.
Will End task damage my computer?
Ending a normal application usually terminates that application rather than damaging Windows itself. The bigger concern is losing unsaved work or interrupting an operation that was writing important data.
Why does only one Windows program keep freezing?
Possible causes include application bugs, corrupted settings, problematic files, extensions, compatibility issues, insufficient resources, or conflicts with other software. Testing another file and another user account can help narrow the possibilities.
What if every program starts freezing?
Treat that as a broader Windows performance or stability problem. Check system resource usage, storage, drivers, Windows updates, and recent changes rather than focusing only on one application.
Is Repair better than reinstalling an application?
When available, Repair is a less disruptive option worth trying before a complete reinstall. Microsoft provides Repair options for some Windows applications, although not every program supports them.
Can low disk space cause applications to freeze?
Very low available storage can contribute to Windows and application performance problems. Check the available space before assuming the application itself is damaged.
Should I use a registry cleaner to fix freezing programs?
No. A registry cleaner is not a reliable first-line solution for an application that stops responding. Diagnose the specific program or system condition instead.
When should I consider reinstalling the program?
Reinstalling makes more sense when the problem consistently affects that application, simpler repair and troubleshooting steps have failed, and there is evidence that the installation or its components may be damaged.
Final Takeaway
When a Windows program suddenly stops responding, End task should be a decision, not the first diagnostic step.
First determine whether the program is actually frozen, temporarily busy, waiting for another window, or affected by a broader Windows problem.
Check Task Manager, test another file, look for recent changes, update the application, and use Windows’ Repair option when available. If the problem keeps returning, Reliability Monitor, Event Viewer, another Windows account, and a clean boot can help narrow down the cause.
Only after those checks should you move toward more disruptive actions such as resetting or reinstalling the application.
That approach gives you a better chance of fixing the underlying problem while reducing the risk of losing useful data or changing Windows settings unnecessarily.
Official Microsoft Resources
- Microsoft Support: Repair apps and programs in Windows
- Microsoft Support: How to perform a clean boot in Windows
- Microsoft Support: Recovery options in Windows
- Microsoft Support: Make older apps or programs compatible with Windows
- Microsoft Support: Use DISM and System File Checker to repair Windows system files