Windows-server-2019 - windows-file-explorer issue

Finbou - Investment Advisory 0 Reputation points
2026-08-26T00:29:28.53+00:00

Windows Essentials 20019 dedicated server is having explorer.exe issues. Seems an unkillable kernel I/O deadlock while running 18 critical MT4/5 platforms stably. I can sometimes end explorer.exe via Task Manager, but sometimes right-clicking on folders or tasks doesn't work. The only fix I have is to end it and then run it again via Task Manager > File> Run new task > "explorer.exe"

I can't send an event log either because the Event Viewer doesn't work.

Windows for business | Windows Server | Performance | System performance
0 comments No comments

1 answer

Sort by: Most helpful
  1. Hoang Le 6,355 Reputation points Independent Advisor
    2026-08-26T02:39:56.32+00:00

    Dear Finbou - Investment Advisory,

    The behavior you describe points to a kernel‑level I/O deadlock in explorer.exe, which is aggravated by the heavy workload of running multiple MT4/MT5 instances. On Windows Server Essentials 2019, Explorer is not critical for server operation, but when it hangs it can block shell interactions and even prevent Event Viewer from launching. There is no supported way to adjust heap allocation or thread concurrency for explorer.exe itself, since those parameters are hardcoded in the Windows shell. The correct mitigation is to isolate the workload: either disable Explorer auto‑start and run the server headless, or move the trading platforms into dedicated Hyper‑V VMs so that the host shell is not burdened by user‑mode I/O.

    For diagnosis, you should capture a kernel dump when the deadlock occurs (procdump -ma explorer.exe) and analyze it with WinDbg to confirm which I/O threads are blocked. If the Event Viewer is unusable, check logs directly under %SystemRoot%\System32\winevt\Logs and parse them with PowerShell (Get-WinEvent). If corruption is suspected, run sfc /scannow and DISM /Online /Cleanup-Image /RestoreHealth to repair system components. Ultimately, the best practice is to avoid running critical workloads directly on the Essentials host shell and instead use VM isolation or Remote Desktop sessions, which prevents Explorer from becoming a single point of failure.

    If my answer is useful for you, please hit Accept the answer to support me.

    Thank you,

    HL.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments

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.