Fences 7.0.0.9 intermittently crashes Explorer at startup with Segment Heap enabled
Windows Version Number: Windows 26H2 x64(26300.10075)
App Version: 7.0.0.9
I reproduced an Explorer crash with Fences 7.0.0.9 on Windows 26H2 x64, OS build 26300.10075. Explorer crashed twice during the first test with Segment Heap enabled. The same startup test completed without a crash after I switched only explorer.exe to NT Heap.
Steps to reproduce
- On a system with Fences 7.0.0.9 installed and system-wide Segment Heap enabled, make sure
explorer.exehas noFrontEndHeapDebugOptionsoverride underHKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options\explorer.exe. - Restart Windows Explorer from Task Manager. I verified that the replacement Explorer process was using Segment Heap.
- Run
Fences.exe /startupand let the desktop initialize. Explorer may terminate and restart automatically.
Expected and actual results
| Explorer heap | Result |
|---|---|
| Segment Heap | Explorer crashed twice during the first 21-second test. Windows Error Reporting recorded ntdll.dll, exception 0xC0000409, and fast-fail subcode 0x23. |
| NT Heap | I set FrontEndHeapDebugOptions to DWORD 0x4 for explorer.exe only, restarted Explorer, and verified it was using NT Heap. Fences.exe /startup exited with code 0, the Fences desktop modules loaded, and no new crashes occurred during the 15-second follow-up. The global Segment Heap setting stayed enabled. |
WinDbg findings
Both dumps show DesktopDock64.dll version 7.0.0.9 loaded in Explorer. The call stack passes through Fences’ Detour64.dll into ntdll!RtlAllocateHeap. The original exception is 0xC0000005 at ntdll!RtlpHpSegMgrCommit+0x14F. In both dumps, movaps attempts to write to a stack address that is 8 bytes off the required 16-byte alignment. The heap exception handler then terminates Explorer with 0xC0000409, subcode 0x23 (FAST_FAIL_UNEXPECTED_HEAP_EXCEPTION).
Could you check where the x64 stack alignment is lost in the call path that reaches RtlAllocateHeap through Detour64.dll?
Crash dumps
Both Explorer minidumps were captured on November 22, 2026 (UTC+8).
I cannot post the dump links here beacuse it rejects me to create a new post.
| File | Crash time | Size |
|---|---|---|
explorer.exe.26256.dmp |
04:25:33.294 |
48,894,584 bytes |
explorer.exe.54884.dmp |
04:25:43.060 |
50,750,555 bytes |