Windows 11 Not Responding: Diagnose Freezes and Restore Stability

Windows 11 can stop responding when an application becomes stuck, a system process consumes excessive resources, a driver fails or hardware cannot complete an operation.

The correct repair depends on the scope of the freeze.

If only one program is affected, restarting that application may be enough; if the taskbar, Start menu and other programs also stop responding, investigate Windows, drivers and hardware.

A frozen application and a frozen operating system are different failures.

An application may display a Not Responding label because its main thread is not processing messages, while Windows continues to run in the background.

A full system freeze can prevent keyboard shortcuts, Task Manager and other processes from working.

Distinguishing these conditions prevents unnecessary resets and helps preserve evidence about the cause.

Start by recording when the problem occurs, which applications are open, and whether the mouse pointer still moves.

Note whether the freeze happens after sign-in, during file transfers, while browsing, after waking from sleep or under heavy workload.

That timing often points towards the relevant component, such as startup software, storage, graphics, memory or a recent Windows update.

Recover the desktop

When File Explorer stops responding, the desktop and taskbar may also become unusable because Windows uses the Explorer process to manage those parts of the interface.

If Task Manager still opens, press Ctrl + Shift + Esc, locate Windows Explorer under Processes, right click it and select Restart.

The taskbar and desktop may disappear briefly while the process reloads, then return without a full computer restart.

This is a useful first response when folders or the Windows shell freeze but other applications remain active.

If Windows Explorer is missing from the process list, use Task Manager's Run new task option and enter explorer.exe.

This starts a new shell process and may restore the desktop after a crash.

Restarting Explorer does not repair a damaged folder, unavailable network location or faulty context menu extension, so observe what happens when you repeat the action that caused the freeze.

If only one folder triggers the problem, investigate its contents and storage location before changing system settings.

A folder that hangs while displaying thumbnails or previews may be waiting for Windows to read a damaged media file, an unavailable drive or a third party preview handler.

Close the Preview pane and test the same folder with thumbnails disabled or with a different folder view.

If the problem occurs only when right clicking files, a shell extension installed by an archive utility, cloud storage client or security application may be responsible.

TechBasics101 and Help Desk Geek both identify these Explorer specific triggers as useful distinctions during diagnosis.

Measure resource pressure

Task Manager provides the quickest view of whether a process is consuming the resources Windows needs to remain responsive.

Press Ctrl + Shift + Esc and select Processes, then review CPU, Memory, Disk and Network usage while the system is slow.

Sort by each column to identify applications or background processes that remain near the top.

Microsoft recommends monitoring these resource categories and closing applications that are not needed when investigating poor performance.

High CPU usage can make the desktop lag while a process performs intensive work, such as video encoding, software compilation, antivirus scanning or a large update.

Memory pressure can cause Windows to move data between RAM and the paging file, which may make switching between applications slow.

Disk activity that remains high while the computer responds slowly can indicate a busy update, indexing operation, synchronization process or storage bottleneck.

Record the process name and the resource that remains saturated instead of ending unfamiliar system tasks at random.

The Performance tab gives a broader view of CPU, memory, disk, Ethernet and GPU activity.

Check whether memory use approaches the installed capacity, whether the system disk remains busy and whether the GPU is under sustained load.

A browser with many tabs, a large spreadsheet, virtual machines and video editing software can collectively exceed available memory.

Closing a workload may restore responsiveness, but repeated freezes under ordinary use justify checking startup programs, memory capacity and the health of the system drive.

Do not terminate a process simply because its name is unfamiliar or its resource use is high.

Web Hosting

Hostinger VPS

4.3

4.3

Hostinger VPS delivers KVM virtualization, NVMe storage and full root access at prices that undercut most competing cloud providers.

• Strong price to specification ratio overall
• NVMe storage included on every tier

• Renewal rates climb steeply after promo
• Self managed means security is your job

Read review Get Started Affiliate Link

Windows Update, Microsoft Defender, Search Indexer and cloud synchronization services can temporarily consume substantial resources during legitimate work.

Check the process location and publisher, inspect its activity, and give a legitimate operation time to finish if the disk or CPU activity is progressing.

If the same process repeatedly becomes unresponsive, update or repair the application that owns it.

Check storage health

A storage device can make the entire computer appear frozen when Windows waits for data that takes too long to read or write.

This can affect File Explorer, application launches, sign in, updates and even the Start menu because those operations depend on the system drive.

A nearly full drive can also restrict temporary storage and paging operations.

Open Settings, select System and Storage, and review the space used by installed applications, temporary files and other categories.

Microsoft provides a critical storage warning feature for supported drives.

In Settings, open System, Storage, Advanced storage settings and Disks & volumes, then select the affected drive and inspect its Properties.

Windows can report low spare capacity, degraded reliability or a drive that has become read only.

Microsoft advises users to back up data and seek support when a critical warning appears, because a drive reporting reliability problems may be at risk of failure.

If a drive disappears intermittently, produces unusual mechanical sounds or causes repeated pauses during file access, prioritize a backup before running intensive repair utilities.

A failing HDD or SSD can deteriorate while diagnostic scans are running.

Copy irreplaceable documents to another physical drive or a reliable network location, then use the manufacturer's diagnostic utility to assess the device.

Do not treat a successful Windows file check as proof that the physical drive is healthy.

External and network storage can create a more localized freeze.

A mapped drive that is offline, a NAS that is unreachable, a USB enclosure with a failing disk or a cloud synchronization folder waiting for a connection can delay File Explorer.

Disconnect the affected device or temporarily remove the unavailable network location, then repeat the same folder operation.

If the freeze disappears, troubleshoot the connection, cable, enclosure, VPN or storage service rather than reinstalling Windows.

Isolate background software

A clean boot starts Windows with essential drivers and services while disabling third party startup programs and services for diagnostic purposes.

It helps identify software conflicts that may not appear when you inspect Task Manager during a normal session.

Microsoft distinguishes a clean boot from Safe Mode because it gives administrators more control over which services and startup applications remain active.

Use it when the computer freezes repeatedly and basic resource checks have not identified the cause.

To perform the test, search for System Configuration or run msconfig, then open the Services tab.

Select Hide all Microsoft services before choosing Disable all, so essential Windows services remain protected.

Open the Startup tab, select Open Task Manager and disable the enabled startup applications while recording which entries you changed.

Restart the computer and use it under the same conditions that normally trigger the freeze.

If the problem disappears during a clean boot, a disabled service or startup application is a likely contributor.

Re-enable entries in controlled groups and restart between tests until the freeze returns.

Microsoft recommends testing groups of services and startup items systematically, which reduces the number of restarts needed to isolate the conflict.

Once identified, update or uninstall the responsible application, or leave its unnecessary startup component disabled.

Restore normal startup after the test.

Open System Configuration, select Normal startup on the General tab, then restore the services and startup applications you disabled.

A clean boot is a temporary diagnostic state, not a permanent performance setting.

Leaving security software, backup clients or business applications disabled can expose the computer or interrupt important tasks.

Repair Windows components

Corrupted Windows system files can cause features to malfunction, applications to hang and the operating system to become unresponsive.

Microsoft provides DISM and System File Checker to repair the Windows component store and protected system files.

Run these tools when the freeze affects Windows features broadly or persists after software isolation, rather than using them as the first response to one isolated application failure.

Open Command Prompt as administrator and run DISM with the online image and RestoreHealth options.

Wait until the operation reports completion, then run System File Checker with the Scannow option.

DISM can repair the component store that provides files for Windows repairs, while SFC checks protected system files and replaces damaged copies where possible.

Microsoft specifies this order in its current instructions for Windows 11 and Windows 10.

The result matters.

If SFC reports that it found and repaired corrupted files, restart Windows and test the operations that previously caused the freeze.

If it reports that no integrity violations were found, system file corruption becomes a less likely explanation, but drivers and hardware remain possible causes.

If SFC cannot repair some files, preserve the scan details and investigate the component store, Windows Update and storage health before attempting a reset.

A freeze that occurs during an update or immediately after a Windows feature update needs a version specific check.

Open Settings, select Windows Update and review Update history to identify the installed cumulative update and its date.

Then consult Microsoft's Windows release health page for the installed Windows 11 version and check for known issues that match the symptoms.

The release health information is particularly useful because an issue can affect a specific update, device configuration or enterprise environment rather than every Windows 11 computer.

For example, Microsoft documented a desktop loading problem after certain August 2026 updates, primarily on Azure Virtual Desktop hosts using FSLogix.

The symptoms included a black screen after sign in and Windows Explorer crashes, and Microsoft marked the issue resolved by updates released from October 13, 2026.

That case does not establish a general Windows 11 freezing defect, but it demonstrates why update history and release health should be checked before changing unrelated drivers or hardware.

Examine system logs

Event Viewer can help establish what Windows recorded immediately before or after a freeze.

Search for Event Viewer, open Windows Logs and inspect both System and Application logs around the time the computer stopped responding.

Look for repeated application errors, service failures, disk warnings, driver errors and unexpected shutdown records.

Microsoft's advanced freeze troubleshooting guidance specifically recommends reviewing System and Application logs after a computer has recovered.

Reliability Monitor offers a more accessible timeline of application failures, Windows failures and installation events.

Web Hosting

Hostinger VPS

4.3

4.3

Hostinger VPS delivers KVM virtualization, NVMe storage and full root access at prices that undercut most competing cloud providers.

• Strong price to specification ratio overall
• NVMe storage included on every tier

• Renewal rates climb steeply after promo
• Self managed means security is your job

Read review Get Started Affiliate Link

Search Windows for View reliability history and inspect the days when the freezes occurred.

A repeated failure for the same application or module can help identify a software issue, while a sequence of failures that begins after a driver or update installation can establish a useful timeline.

Reliability Monitor is a starting point for correlation, not a tool that independently proves the root cause.

Kernel Power Event ID 41 is often misunderstood.

It records that Windows restarted without a clean shutdown, which can happen after a forced power off, power loss or a system crash.

The event alone does not prove that the power supply is defective.

Check whether the same event includes a bug check code or whether other errors appear at the same time, then correlate the record with the freeze and any hardware or software changes.

For a repeatable freeze, create a record with the exact time, workload, connected devices and whether keyboard shortcuts still worked.

This makes it easier to compare event logs across separate incidents.

In a managed environment, preserve the relevant logs before cleanup or reinstallation, because they may help an administrator identify a common driver, service or storage failure across several machines.

Test memory and drivers

Faulty RAM can cause intermittent freezes, application crashes and inconsistent system behavior.

Windows Memory Diagnostic provides a built in test that can detect certain memory errors.

Search for Windows Memory Diagnostic, select Restart now and check for problems, then allow the computer to restart and complete the test.

Save open work first because the test requires a restart and may take several minutes.

If the diagnostic reports memory errors, repeat the test if necessary and consult the computer manufacturer's hardware documentation.

Desktop computers with removable memory modules may allow individual module testing, which can help identify a defective stick or slot.

Shut down the computer and disconnect power before opening the case.

If the memory is soldered or the machine is under warranty, use the manufacturer's service process instead of attempting an unsupported repair.

Drivers deserve attention when freezes begin after a graphics, chipset, network or storage update.

Open Device Manager and inspect devices with warning symbols, then review the driver provider and version for the relevant component.

Obtain updates from Windows Update or the computer manufacturer's support page for the exact model.

If the problem began immediately after a driver update, use Roll Back Driver where available and test the computer before installing another package.

A driver can also be responsible when the system freezes only during a specific operation.

Graphics problems may appear during video playback or gaming, while storage controller problems may occur during large file transfers.

Network adapter faults can cause pauses during network access without affecting offline applications.

Match the driver investigation to the workload that triggers the freeze, and change one component at a time so the result remains useful.

Use Safe Mode

Safe Mode loads Windows with a limited set of drivers and services.

If the computer remains stable in Safe Mode but freezes during normal startup, a third party driver, service or startup application becomes a stronger suspect.

If the same hard freeze occurs in Safe Mode, investigate Windows components and hardware more closely.

This comparison does not prove the cause, but it helps separate problems that depend on normal startup software from those that persist with a reduced configuration.

To enter Safe Mode, hold Shift while selecting Restart from the Start menu.

Choose Troubleshoot, Advanced options, Startup Settings and Restart.

When the numbered startup menu appears, select Safe Mode or Safe Mode with Networking if you need internet access.

If Windows cannot reach the desktop, enter Windows Recovery Environment through repeated failed starts or use Windows installation media and select the repair option.

Use Safe Mode to remove a recently installed application, inspect Device Manager or copy important files before further repair.

Do not assume that a stable Safe Mode session proves every hardware component is healthy, because the system uses fewer drivers and features in this environment.

If the computer freezes only during normal startup, continue with a clean boot and controlled driver tests.

If it freezes in both modes, prioritize memory, storage, temperature and power diagnostics.

Know when to reset

Reset this PC is appropriate when Windows remains unstable after reasonable software and driver checks, but it should come after a backup and a review of hardware health.

Windows offers options that keep personal files or remove everything, although installed applications and settings may be removed.

The Keep my files option is not a substitute for a separate backup, and the reset process can fail if the system drive or Windows recovery components are damaged.

Before a reset, copy important files to an external drive or trusted network location and make sure you have access to application installers, license information and account credentials.

If the computer contains business data, confirm that the backup is readable and that the recovery plan complies with company policy.

A reset can remove software conflicts and damaged Windows configuration, but it cannot repair defective memory, a failing SSD or overheating hardware.

If the computer freezes even during Windows installation or recovery, stop repeating software resets and arrange hardware diagnostics.

A technician may need to test RAM, storage, motherboard, cooling and power delivery.

For advanced cases, Microsoft documents methods to collect memory dumps and performance data while a computer is frozen, although these procedures require administrator access and careful configuration.

Preserving diagnostic evidence is more useful than repeatedly forcing shutdowns without recording what happened.

Advanced troubleshooting for persistent freezes

When basic repairs fail, the next step is to identify the exact condition that triggers the freeze.

Windows 11 may appear unresponsive because of a faulty driver, a background process, a damaged user profile or a hardware problem.

A repeatable test is more useful than changing several settings at once.

Reproduce the problem

Start by recording what happens immediately before the computer stops responding.

This helps narrow the investigation and prevents unnecessary changes to Windows.

Use this procedure:

1. Restart the computer and sign in normally.
2. Wait until startup activity has settled.
3. Open only the application that usually causes the problem.
4. Repeat the action that previously triggered the freeze.
5. Record the time and note whether the mouse, keyboard and other applications still respond.
6. Repeat the test after a restart to check whether the behaviour is consistent.

Record these details for each incident:

• The application or task that was active.
• Whether the freeze occurred immediately after startup or during normal use.
• CPU, memory and disk usage before the system stopped responding.
• Any recent Windows updates, driver installations or application changes.
• Whether the computer recovered by itself or required a restart.

A consistent trigger often points towards a specific application, device or service.

Random freezes across unrelated activities require a broader investigation.

Test with a new user account

A damaged Windows user profile can cause problems with the Start menu, File Explorer, desktop settings and applications.

Testing with another account helps determine whether the issue affects one profile or the entire computer.

1. Open Settings.
2. Select Accounts.
3. Open Other users.
4. Choose Add account.
5. Create a separate local test account if appropriate.
6. Sign out of the current account and sign in with the new one.
7. Test the activities that previously caused Windows to freeze.

If the new account works normally, the original profile may contain damaged settings or application data.

If both accounts experience the same freezes, investigate system components, drivers and hardware instead.

Do not delete the original account during this test.

First back up its files and confirm that the new profile provides access to the applications and resources you need.

Prevent Windows 11 from freezing again

Once the computer becomes stable, review the changes that can reduce the likelihood of another incident.

Prevention is particularly useful on computers that run several applications, handle large files or remain switched on for extended periods.

Control startup applications

Applications that launch automatically can increase startup time and consume memory throughout the working session.

Web Hosting

Hostinger VPS

4.3

4.3

Hostinger VPS delivers KVM virtualization, NVMe storage and full root access at prices that undercut most competing cloud providers.

• Strong price to specification ratio overall
• NVMe storage included on every tier

• Renewal rates climb steeply after promo
• Self managed means security is your job

Read review Get Started Affiliate Link

To review them:

1. Press Ctrl + Shift + Esc.
2. Open Startup apps in Task Manager.
3. Review the applications listed.
4. Check the Startup impact column.
5. Disable applications that are not required at sign-in.

Keep security software, hardware utilities and applications that support essential business functions enabled.

Disabling a startup entry does not normally uninstall the application; it prevents automatic launch.

Keep drivers and Windows updated

Outdated or incompatible drivers can cause instability, particularly after a major Windows update.

Check Windows Update and the computer manufacturer's support page for drivers designed for the exact model.

Prioritise these components:

• Graphics drivers, especially on computers with dedicated GPUs.
• Chipset and motherboard drivers.
• Storage controller drivers.
• Network and Wi-Fi adapters.
• Audio and peripheral drivers.

Avoid installing several driver packages from unknown websites.

Use Windows Update or the manufacturer's official support resources, and create a restore point before making significant driver changes.

Maintain sufficient storage space

Windows needs available storage for temporary files, updates, virtual memory and application activity.

A nearly full system drive can contribute to poor performance and update failures.

Review storage periodically:

1. Open Settings.
2. Select System.
3. Choose Storage.
4. Review Temporary files and installed applications.
5. Remove files you no longer need.
6. Empty the Recycle Bin after checking its contents.

Do not manually delete unfamiliar folders from Windows or Program Files.

Removing system components can create additional problems.

Choosing the right recovery option

Not every freeze requires a Windows reset.

The appropriate repair depends on the evidence collected during diagnosis.

A Windows reset should remain a recovery option after less disruptive repairs have been exhausted.

Before choosing it, verify that important files are backed up and that you have access to the necessary application installers, licence information and account credentials.