This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(16, 5%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EFL%3C/text%3E%3C/svg%3E)
Whenever I load animations on the Store of my Windows 10 ESU PC, DWM crashes and restarts. I am currently on the Insider Release Preview channel, and I can't leave it since I need to wait until the "next major release of Windows 10", which is obviously not going to happen. I have reproduced the issue on a VM, so it's not my PC's fault. Is there any way I can ask Microsoft to report the bug? Mod moved from Windows Insider
This might be the exact same crash I diagnosed and reported in detail here: https://learn.microsoft.com/en-ie/answers/questions/5942677/dwm-exe-fail-fast-purecall-in-dwmcore-cexpressionm . Same trigger (Store animations), same dwm.exe fail-fast/restart pattern. Mine is a purecall inside dwmcore!CExpressionManager::UpdateExpressions — if you still have a crash dump from your VM repro, it'd be worth checking if the Failure.Hash matches {e31753ac-c98a-8055-3663-47e707543d20}. If it does, that's two independent reproductions of the same bug, which might carry more weight if either of us reports it further.
One thing worth clarifying: Windows 10 has no active development anymore, so there's no newer build to wait for regardless of Insider channel — if you're on 22H2 build 19045 with the latest July 2026 LCU, that's the same branch everyone on ESU is on. Could you confirm your exact dwm.exe version and build number (winver and Get-Item C:\Windows\System32\dwm.exe) ? That would help determine if this is really the same underlying issue.
Of course! My winver is 19045.7548 (latest ESU patch Tuesday) and
this is my DWM version. If you want, I can show you some logs I got from Event Viewer.
Yes, please share them. What would help most:
The Faulting application name/module/exception code block for the dwm.exe crash (the standard WER entry, Event ID 1000, source "Application Error"). I'm mainly looking for the exception code (mine is 0xc0000409) Even just the Event Viewer entry is useful on its own,
I confirmed my dwm.exe version , and Windows 10 build match yours exactly .
Once again, Microsoft has shown a complete lack of respect for a user's work — they deleted, without reason, my thread where I analyzed and explained the actual cause of this problem.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(60.8, 22%, 15%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EJ%3C/text%3E%3C/svg%3E)
@MSH™ ®
I undeleted your thread (https://learn.microsoft.com/en-us/answers/questions/5942677/dwm-exe-fail-fast-purecall-in-dwmcore-cexpressionm) which got wrongly deleted by the system.
Ok here is my crash log of DWM:
Faulting application name: dwm.exe, version: 10.0.19041.7417, time stamp: 0xe923a573
Faulting module name: ucrtbase.dll, version: 10.0.19041.7548, time stamp: 0x2bd748bf
Exception code: 0xc0000409
Fault offset: 0x000000000007286e
Faulting process id: 0x14a0
Faulting application start time: 0x01dd2260d16d2745
Faulting application path: C:\WINDOWS\System32\dwm.exe
Faulting module path: C:\WINDOWS\System32\ucrtbase.dll
Report Id: cf1f7fbc-bf21-4ba0-b9bb-b90ade347e9e
Faulting package full name:
Faulting package-relative application ID:
Wow I got the SAME exception code as yours
Thank you for your log .
That's it — same file offset too (0x7286e), not just the same exception code. That's about as close to a 100% match as you can get from a WER event log alone.
This confirms it , same bug, two completely independent machines, so honestly, at this point I don't think there's much doubt left. The problems is that as you know Windows 10 is in ESU , I haven't hope that Microsoft will fix this bug .
One more thing, in case it helps build up telemetry on this: could you check whether Windows Error Reporting is actually enabled and set to auto-send on your end? Most people never touch this, so you're probably fine, but worth a 10-second check in powershell >
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\Windows Error Reporting' -Name Disabled -ErrorAction SilentlyContinue
Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\Windows Error Reporting\Consent' -Name DefaultConsent -ErrorAction SilentlyContinue
check the value for first command Disabled : 0 , and for the second command DefaultConsent : 3
After a few weeks of random Store updates, it still crashes on both the PC and the VM; I have no hope for Microsoft at this point
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(198.4, 2%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EPO%3C/text%3E%3C/svg%3E)
I can't leave it since I need to wait until the "next major release of Windows 10", which is obviously not going to happen.
You can get your device out of Insider program by deleting WindowsSelfHost -key from registry.
Open reg edit and go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsSelfHost
On left menu right click WindowsSelfHost and select Delete. Restart.
For bug report use Feedback Hub (push Win key + F)
