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.