Site identity

About TraceCheck

TraceCheck is an independent reference for software failures and changes: what is affected, what the evidence establishes, and what remains unknown.

What TraceCheck does

For Windows, we connect affected versions, originating updates, symptoms, documented fixes and issue history. A fixing KB is kept separate from an originating KB. An affected Windows version is not automatically covered by every linked fix.

For AI coding tools, we organize official pricing, usage limits, reset windows, metering and material changes. Comparisons and calculators keep incompatible quota units separate. An undisclosed limit stays Unknown.

The value of the index is in those connections and decision guides. Source summaries alone do not establish a diagnosis, an equivalent quota, or the best product for every reader.

What the index covers

Coverage is selective. The Windows collection includes NDI streaming, Plan9 folder sharing in Claude Cowork/WSL, USB Audio Class 1.0, ARM Teams/new Outlook launch failures and post-sign-in black-screen records. Fixes carry version and symptom scope; a partial audio fix does not mean every audio symptom is resolved. It is not a complete outage feed or a catalogue of every current Windows issue. An empty result means we have no published record, not that an update is problem-free.

The Windows investigation check connects a selected symptom, version and affected feature to the reviewed records. Our worked examples explain update roles and resolution boundaries. You can save an investigation brief locally and complete it with your own observations. This checks applicability against our inventory; it does not diagnose or scan a device.

How information is published

Official vendor pages are canonical. Automation can create a private pending candidate, but a human must open the source and verify a material change before it becomes public. The methodology explains the Fact, Derived, Observed, Unknown, and Pending verification labels.

Software reading guides are labeled TraceCheck interpretation and cite the evidence they rely on. They explain how to apply the record without presenting editorial advice as a vendor statement. Source verification and a test on a real device are different activities; a source check is not a claim that we reproduced the failure or tested the fix.

Corrections and accountability

Report a statement with the page URL and the evidence that contradicts it. Corrections are checked against the applicable product or version. Material factual changes belong in the record's change history; formatting edits do not reset a verification date. If evidence conflicts or a cause is not established, the uncertainty remains visible.

Maintainer and contact

TraceCheck's maintainer checks official sources and reviews changes before publication. Verification dates record when the cited information was checked; they do not guarantee that a vendor has not changed it since. Conflicting sources and undisclosed limits remain visible as Unknown.

For corrections, source questions, privacy requests, or site feedback, visit Contact TraceCheck. The public support Issues page is separate from the private site repository. GitHub sign-in is required to post, and requests and replies are public.

See the Privacy Policy for current analytics and advertising disclosures.