2) Windows Version: Windows 11 Pro 25H2 (Build 26200.8655)
3) Screen Scaling Percentage: 100% (1920x1080, XYplorer maximized)
WHAT HAPPENS
Copying files in XYplorer with Ctrl+C intermittently makes Windows Explorer (explorer.exe) crash and restart (taskbar/desktop reload). XYplorer itself is completely unaffected and the copy/paste always completes correctly. Plain Ctrl+C / Ctrl+V only - no drag & drop involved.
FREQUENCY / HISTORY
9 explorer.exe crashes logged in the last 30 days (Application log, Event ID 1000), two of them today:
2026-06-08 18:35, 06-11 18:01, 06-11 19:36, 06-23 18:40, 06-24 11:41, 06-30 15:55, 07-06 15:08, 07-07 11:34, 07-07 15:47.
The crashes span two Windows servicing levels (shell binaries 10.0.26100.8457 and .8655), so this is not tied to one specific Windows cumulative update.
CRASH ANALYSIS
I analyzed the 4 available WER minidumps of explorer.exe (LocalDumps) and resolved the stacks against Microsoft's public symbol server. All four dumps show the identical failure; the remaining logged events fault at the same two sites.
Signature: access violation 0xC0000005 (read) in memcpy, called from windows.storage.dll while cloning an ITEMIDLIST that Explorer obtained from the clipboard data object's "Shell IDList Array" (CFSTR_SHELLIDLIST / HIDA). The PIDL size computed by walking the cb chain is far larger than the actual buffer (claimed 39-147 KB vs ~9-64 KB actually mapped), i.e. the ID list appears to lack a proper terminator / has a corrupt cb chain, and the copy runs off the end of the allocation into an unmapped page.
Two crashing entry paths, both fired by Explorer probing the clipboard right after it changes (Win11 command bar updating Paste availability - explains why no user drag is needed):
Code: Select all
Variant A (4 of 4 dumps):
ucrtbase!memcpy_repmovs <- AV: source buffer overread
windows.storage!ILCloneParent
windows.storage!SHBindToFolderIDListParent
shell32!DataObj_GetIDList
shell32!CFSDropTarget::_CanSourceTransferHIDA
shell32!CFSDropTarget::_CanMoveCopyHIDA
shell32!CFSDropTarget::DragEnter <- programmatic paste-effect probe (no real drag)
(COM cross-apartment dispatch: actxprxy/combase/rpcrt4;
Windows.UI.FileExplorer command bar further down the stack)
Variant B (2 logged events):
ucrtbase!memcpy_repmovs
windows.storage!CShellItem::SetIDList
windows.storage!SHCreateItemFromIDList
windows.storage!SHGetItemFromDataObject
(Windows.UI.FileExplorer!CommandBarViewAdapter on the stack)
memcpy total size rbp=0x1E128 (123,176 bytes), source rdx=0x5A239190, faulted at rsi=0x5A242000 (exact page boundary) after copying 0x8E70 (36,464) bytes, remaining rcx=0x152B8. So the walked PIDL claimed ~3.4x more data than the allocation actually held.
HOW I TRIGGER IT
- Select a few dozen up to ~100 files/folders in XYplorer, press Ctrl+C, while at least one File Explorer window is open. Explorer crashes within seconds (its clipboard probe), not every time.
- Paths frequently contain CJK (Chinese) characters.
- Copy source is always XYplorer; copying the same items with File Explorer as source has never crashed here.
NOTES
- Third-party shell extensions are installed (Baidu Netdisk, TortoiseSVN, Google Drive, PowerToys, 360zip), but none of them appear anywhere on the crashing call stack - the parsed data comes from the clipboard data object.
- Not yet tested with a clean default XYplorer configuration.
- The 4 .dmp files (~50 MB each) are available on request, as is a small validator script that checks the on-clipboard HIDA structure offline. Happy to test beta builds or capture more data.
XYplorer Beta Club