Hello Faas, Jason,
The behavior you’re describing is tied to how Windows handles the pinned File Explorer shortcut on the taskbar. The Win+E shortcut calls explorer.exe directly with the default shell path, whereas the taskbar pin is a shortcut object stored under %AppData%\Microsoft\Internet Explorer\Quick Launch\User Pinned\TaskBar. If that shortcut becomes corrupted or points to an invalid CLSID or path, Explorer will attempt to resolve it, hang, and then restart itself. That explains why Win+E works fine but clicking the pinned icon causes the crash.
The fix is to completely remove the pinned shortcut and rebuild it from a clean state. Delete the File Explorer shortcut from the pinned taskbar list mentioned above, then clear the cache under %AppData%\Microsoft\Windows\Recent\AutomaticDestinations (this is where Explorer jump list data is stored). After that, reboot and pin File Explorer again from C:\Windows\explorer.exe directly rather than re‑pinning from the existing shortcut. This ensures the taskbar entry points to the correct binary without stale metadata.
If the issue persists even after recreating the shortcut, it can indicate corruption in the Explorer shell extensions or context handlers. In that case, you would need to disable non‑Microsoft shell extensions using Sysinternals Autoruns (Explorer tab) and test again. A faulty third‑party extension can cause Explorer to hang only when invoked through certain entry points like the pinned shortcut.
I hope you've found something useful here. If it helps you get more insight into the issue, it's appreciated to accept the answer. Should you have more questions, feel free to leave a message. Have a nice day!
Domic Vo.