Format:Windows Error Reporting report (Report.wer)
| On this wiki | Facts · Code · Notes · Topics |
|---|
The Report.wer text file that Windows Error Reporting writes beside a crash dump: UTF-16 text of Key=Value lines with indexed Sig[n], DynamicSig[n], UI[n], LoadedModule[n] and State[n] entries, timestamps as FILETIME.
When a program crashes or hangs, Windows Error Reporting stores a report folder (default archive folder C:\ProgramData\Microsoft\Windows\WER\ReportArchive, as used by the parser read for this page; queued reports live in a sibling queue folder, Unverified) with a Report.wer file and often a Format:Minidump. The text is also a record of what ran and from where.
Source read: pukhanov/wer_parser parse_wer.py (Apache-2.0) at the commit linked below; it parses Report.wer with its own logic, there is no open specification in the sources used.
Text layout (as the parser assumes it)
- The file is read as UTF-16 text (
open(..., encoding="utf-16")), oneName=Valueper line, split at the first=. - Indexed entries are written
Name[N]=valuefor lists such asLoadedModule[0], orName[N].Key=/Name[N].Value=pairs. The parser uses.Nameor.Keyfor the key and the next line as its value for sections such asSig[N],DynamicSig[N],UI[N]andState[N](Unverified: the section names Sig, DynamicSig, UI and State come from memory of typical reports; only the generic handling is in the parser code). - Plain dotted keys such as
Response.typebecomeResponse->type. EventTimeandUploadTimeare 64-bit FILETIME values (100 ns ticks since 1601-01-01 UTC) as decimal text.
Fields the parser reports
AppPath, EventTime, AppName, NsAppName, OriginalFilename, EventType, FriendlyEventName, ReportType, and TargetAppId. When TargetAppId starts with W: and its second !-separated part begins with 0000, the rest is the SHA-1 of the executable, the same hash form as in the Amcache, according to a comment in the parser: only the first 31,457,280 bytes (30 MiB) of the file are hashed.
Why it matters
A report gives the crashing program's path, its name and version, the loaded module list and when the event happened, which helps dating an execution or matching a binary to a hash.
Code & repositories
- https://github.com/pukhanov/wer_parser @
2779234400f5b5dddd7bc70fda01ee252b2facb9· license: Apache-2.0 (declared by the contributor for the files used; GitHub reports Apache-2.0 (read from LICENSE; GitHub's API was busy) for the repository)
Small Python parser for Report.wer files (parse_wer.py).
Tested on: source read, not run · checked 2026-10-19
See also
Format:Minidump, Format:Windows Prefetch, Format:Windows XML Event Log (EVTX).