WispBinderOur corrections
Every time one of our checks, pages, guides or tools gave a wrong or misleading result, or lost something an office typed in, it goes on this list: what happened, who could have been affected, and what we changed. We add entries; we never edit or remove old ones.
The list
A machine-readable copy is at corrections.json. When you open your binder on the results page, your browser compares your own records with this list and shows a notice if a correction applies to them. Nothing is sent to us.
Newest first. Dates are when we found the problem. Our source code repository is private, so the details below come from our own change records; we can show them on request.
C4 · found 5 Nov 2026 · results page
What was wrong: when the Windows check ran without administrator permission, four settings it cannot read in that mode (W02 Full-disk encryption, W05 Windows updates installed recently, W11 Windows records sign-in events, W12 Windows Security log enabled) were shown as "Needs written confirmation". That asked the office to confirm something in writing that the check had simply not read.
Who could be affected: anyone who opened a result file from a check without administrator permission before 5 Nov 2026.
What we changed (5 Nov 2026): these four now show "Not checked yet", with a "Run full check" step. The check script itself did not change; we measured the behaviour on a test computer on 4 Nov 2026 first.
C3 · found 3 Nov 2026 · binder
What was wrong: a date and place typed by hand for record E10 (staff training records) or E12 (vendor list) were overwritten as soon as the training table or vendor table got its first row.
Who could be affected: offices that typed E10 or E12 by hand and then added rows to those tables before 3 Nov 2026.
What we changed (3 Nov 2026): anything typed by hand is kept. An independent review found it; an automatic test now guards it.
C2 · found 2 Nov 2026 · double-click launcher v2
What was wrong: after clicking "Yes" in the Windows permission prompt, the administrator window closed at once and the check did not finish. No result file was made, so no wrong result was shown.
Who could be affected: anyone who used launcher v2 on 2 Nov 2026.
What we changed (2 Nov 2026): launcher v3 hands over its folder in a form Windows cannot break. Every launcher version and its fingerprint is listed in releases.json.
C1 · found 31 Oct 2026 · fix guides and check text
What was wrong: the BitLocker guide listed PowerShell commands that we had not tested. The W06 text (screen locks automatically when idle) did not say that the check also accepts a password-protected screen saver of 15 minutes or less, and that it does not read sleep settings.
Who could be affected: readers of the BitLocker guide and of W06 results before 31 Oct 2026.
What we changed (31 Oct 2026): the guide now shows the steps we tested on 31 Oct 2026; the W06 text says what the check accepts and what it does not read.
What counts as a correction
- A check, page or tool showed a result that was wrong or could mislead an office.
- Something an office typed in was lost or changed without being asked.
- A guide told an office to do something that was wrong or untested.
- A check or tool stopped working in a way an office could notice.
Spelling and layout changes are not listed. Not an audit, not a certification, not legal advice.