Skip to the content
The Update Bureau
About The Update Bureau AI-Written · Source-Checked

How we work

Who publishes this site, where the facts come from, how the AI texts are written and checked, and how you can verify every explanation.

Contact & report a mistake Privacy

Microsoft publishes release notes for every update of Windows 11, Windows 10 (including the long-term servicing editions), Windows Server, .NET Framework, SQL Server, SharePoint Server, Office Online Server and Exchange Server, but they are written for IT administrators and spread over many pages. The Update Bureau puts them in one place and explains them in plain words.

The mascot, an umarell: an elderly man in a flat cap, hands behind his back, reading a billboard with a check mark

Who writes the text

Every update page combines three things: an editor who runs the site, exact technical data from Microsoft, and AI explanations checked against the sources:

1 · The Editor Direction, guides & corrections

The editor runs the site alone. The editor chooses the sources, maintains the matching rules for each Windows and Server branch, writes the practical guides and recurring KB pages, reviews by hand the drafts that fail a check, and verifies every correction readers send in. Most update pages go live without a person reading them first: the checks below are what protects them. By hand so far: 24 guides and 6 recurring KB pages.

2 · Exact Data Numbers never come from AI

Numbers that the data already has (how many vulnerabilities an update fixes, how many are critical or exploited, build numbers, dates, changed files per component) are shown from the data, not from the AI text, so the page never depends on the model for them.

3 · Cited AI Drafts Plain words with exact quotes

An AI model writes each update explanation from those sources, and only from them. It is asked to cite the exact sentence behind each statement so every claim can be checked against Microsoft's text.

Where the facts come from

Only official Microsoft sources: the Windows Update service itself, the Microsoft Update Catalog, the support page of each update, Windows release health, the Security Update Guide, the official CSV file manifests of each package, and the Windows Insider release notes.

  • Windows Update & Update Catalog Packages, superseding chains, prerequisites and standalone installers.
  • Microsoft Support KB Pages The official changelog of fixes, improvements and deployment notes.
  • Release Health & Server History Confirmed known issues, workarounds, resolutions and Server builds.
  • MSRC Security Update Guide Fixed vulnerabilities (CVEs), severity ratings and exploited zero-days.
  • Official CSV File Manifests Changed system files, versions and components inside each package.
  • Windows Insider Release Notes Experimental, Beta and Release Preview build notes and rollouts.

Every page links the sources it uses, and every card links the Microsoft page of its update. We quote short passages and link the rest: the full notes stay on Microsoft's pages.

What we cover

Windows 11 and Windows 10 (version 22H2 and the long-term servicing editions), Windows Server, .NET Framework, SQL Server, SharePoint Server, Office Online Server, Exchange Server and the Windows Insider builds. The history starts in January 2024; older updates are not on the site.

Not covered: the Windows versions Microsoft no longer services and this site does not follow (Windows 11 22H2 and 21H2, Windows 10 1507), and modern .NET (8, 9 and 10), which is separate from .NET Framework. For Insider builds before April 2026 Microsoft published no release notes on its documentation site, so those pages rest on the Windows Insider blog post of the build.

How it is checked

Automated rules check every explanation before it goes live; a draft that fails one is held until the editor looks at it:

  • 01 Every quote must appear, word for word, in the source it cites.
  • 02 Every KB number, build, date and vulnerability ID must exist in the sources.
  • 03 Every change listed by Microsoft must be covered, and the text must stay easy to read.
  • 04 A headline must name what changes, not repeat the product or say something that fits any update.
  • 05 A second AI reads the text against the sources for accuracy and clarity; the drafts it rejects go to the editor.
A text that fails any check is not published until it is fixed. Published texts are compared again with the data when it changes (for example when Microsoft links the vulnerabilities of an update after release), and written again when they no longer agree with it.

How to use and verify the texts

  • 01 Read the short text and the key facts to decide quickly; open the sections below for the details.
  • 02 For anything that matters (a production server, a security decision), open the Microsoft source linked at the end of the page and in the card: it is the reference, this site is a reading aid.
  • 03 Each statement has a footnote with the sentence it comes from.
  • 04 If you find a mistake, tell us the KB number and what is wrong; the editor reads every report, corrects the page, and its history shows the change.

When things change

Microsoft often adds known issues or corrections after release. Pages are checked again automatically and the page history lists what changed.

Who publishes this site

The Update Bureau is an independent publication run by a single editor. It is not affiliated with, sponsored by or endorsed by Microsoft; Windows, SQL Server, SharePoint and Exchange are Microsoft trademarks. The site is supported by clearly labelled advertising, which never influences our explanations or what we cover. To ask a question or report a mistake, see Contact.

An independent publication that explains Microsoft updates from Microsoft's own documents, written with AI and checked by rules and a second AI.