Share via

Windows Explorer hangs and crashes

Vitalii Spasiuk 5 Reputation points
2026-03-17T16:48:28.9666667+00:00

Source

Windows Explorer

Summary

Stopped responding and was closed

Date

‎3/‎17/‎2026 6:39 PM

Status

Report sent

Description

A problem caused this program to stop interacting with Windows.

Faulting Application Path: C:\Windows\explorer.exe

Problem signature

Problem Event Name: AppHangXProcB1

Application Name: explorer.exe

Application Version: 10.0.26100.8036

Application Timestamp: 528e5b22

Hang Signature: d20b

Hang Type: 134217800

Waiting on Application Name: svchost.exe

Waiting on Application Version: 10.0.26100.7705

OS Version: 10.0.26200.2.0.0.256.4

Locale ID: 1033

Additional Hang Signature 1: d20b236d507687ec077eb194c48718fe

Additional Hang Signature 2: 68fb

Additional Hang Signature 3: 68fb92441b6fe31f5949f1b309148e86

Additional Hang Signature 4: 0007

Additional Hang Signature 5: 00075dd9b708f03029698daa026e43fb

Additional Hang Signature 6: 42ba

Additional Hang Signature 7: 42bac8564070fdc23c139ad23906e1c9

Extra information about the problem

Bucket ID: c34ae18c66600e5136a5400b2baa3dc4 (0)

Windows for business | Windows 365 Enterprise

2 answers

Sort by: Most helpful
  1. Chen Tran 10,310 Reputation points Independent Advisor
    2026-03-17T18:23:56.46+00:00

    Hello Vitalii,

    Thank you for posting question on Microsoft Windows Forum!

    Based on the provided error signature (AppHangXProcB1) which indicates that Windows Explorer (explorer.exe) stopped responding because it was waiting on another process, in this case svchost.exe. That might point to a system service or background process hanging and blocking Explorer.

    The suggestion here is to perform a clean slate for the Explorer process to see if it fixes the immediate hang by pressing Ctrl + Shift + Esc to open Task Manager. Find Windows Explorer in the list. Right-click it and select Restart.

    Another suggestion is to clear the File Explorer Cache. Sometimes a corrupted "Recent Files" link or a stuck thumbnail cache causes Explorer to hang while trying to load the "Home" or "Quick Access" view. Also, try to disable Quick Access. Since sometimes pinned items or recent files cause hangs. In Folder Options, set Explorer to open This PC instead of Quick Access.

    • User's image

    Since your error log mentions svchost.exe, there might be some underlying corruption. It is worth running System File Checker + DISM by opening an elevated Command Prompt and run this command DISM /Online /Cleanup-Image /RestoreHealth and then run the command sfc /scannow Then reboot when done. These fix corrupt system files that might cause explorer instability.

    Another point worth mentioning here is that you are running OS Version 10.0.26200. This is a Windows Insider Preview build (likely the Canary or Dev channel). Making sure you are on the latest build. Checking Windows Update to see if a newer build (like 26212 or higher) is available.

    Hope the above information is helpful! If it is. Free feel to hit "Accepted" for benefitting others in community having the same issue too.

    Was this answer helpful?

    1 person found this answer helpful.

  2. AI answer

    2026-03-17T16:48:41.6433333+00:00

    The hang report shows that explorer.exe (File Explorer / shell) is hanging while waiting on svchost.exe in a cross‑process hang (AppHangXProcB1). This means Explorer itself is not necessarily the root cause; it is blocked waiting for a service or component hosted in svchost.exe.

    On modern Windows, hang diagnostics include fields such as WaitingOnAppName and WaitingOnAppVersion specifically to identify this situation. In this case:

    • Waiting on Application Name: svchost.exe
    • Waiting on Application Version: 10.0.26100.7705

    This indicates a service or COM component inside that svchost.exe instance is not responding in time, causing Explorer to stop interacting with Windows and be terminated.

    Because the context only documents the hang-reporting fields and not specific remediation steps for this particular build or service, the only supported conclusion from the provided information is:

    • The problem is a cross‑process hang where Explorer is waiting on svchost.exe, not a simple crash in explorer.exe itself.
    • The diagnostic fields (such as WaitingOnAppName and related fields) are working as designed to report which other process is being waited on.

    Further isolation (which specific service inside svchost.exe, which shell extension, or which COM component is involved) is not covered in the provided context.


    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.