By default, File Explorer in Windows operating systems (OSes) shares same explorer.exe process for all Explorer windows. This means if you open Desktop, Taskbar and few File Explorer windows, they all will be sharing a common process, named explorer.exe. Hence, when you press End Task button for this same process in Task Manager, you’ll find that Desktop and Taskbar is also restarted along with File Explorer.
However, sometimes the third-party software you use on your Windows may change the above mentioned default behavior, and may allow the OS to launch folder windows as a separate process. If this happens, Desktop and Taskbar will get isolated explorer.exe process separated from File Explorer‘s explorer.exe process. The new instances of File Explorer launched will have other brand-new explorer.exe processes. Hence, now if you restart Explorer windows, Desktop and Taskbar won’t be reloaded and they keep running.
Recently, we came around an issue in Windows 10 which is supposed to occur if OS is launching folder windows as separate process. The error is:
Server execution failed.
This error, although may be suppressed by clicking OK button along with error message. But by this, you can’t confirm that error will not appear later. It can occur anytime on any Windows OS edition, which is launching separate instances of folder window. These simple fixes will help you to resolve it:
FIX : Server Execution Failed Error In Windows 10
FIX 1 – Using Registry Editor
1. Press + R and put regedit in Run dialog box to open Registry Editor (if you’re not familiar with Registry Editor, then click here). Click OK.
2. In the left pane of Registry Editor, navigate to following registry key:
3. In the right pane corresponding Advanced registry key, scroll down and look for SeparateProcess named registry DWORD (REG_DWORD). Since you’re facing this issue, the Data for it might be set to 1. Double click on the DWORD to modify its Value data:
4. In the Edit DWORD Value, put 0 as the Value data and click OK. Close Registry Editor. Reboot and problem will be resolved.
FIX 2 – Using Microsoft’s HotFix
Microsoft was already aware of this issue in previous editions of Windows. They have released a HotFix to address this problem. You can use below link to get the HotFix for your machine to automatically resolve this hiccup:
After running the HotFix, the issue will no longer occur.
Let us know if problem still persists!