Skip to content

About Thea

Thea covers each Windows update on the day it ships, and keeps a tested fix on file for the error codes and breakages that follow.

What Thea is

Thea is a Windows help site with two jobs. When Microsoft ships a Windows 11 update, we publish what changed, what it breaks and whether to install it. When an update fails or an error code appears, we publish a fix that works on the build people are running today, not one from three years ago.

Everything is filed under one of five categories:

  • Windows UpdatesWhat's new in each Windows 11 cumulative update and feature release: what changed, what to expect, and whether to install it.
  • Update ProblemsFixes for updates that won't install, get stuck, roll back, or break something after installing.
  • Error CodesStep-by-step fixes for Windows error codes, from Windows Update failures to activation and store errors.
  • Apps Not WorkingThird-party and Microsoft apps that stop opening, crash, or misbehave after a Windows update.
  • How-To GuidesShort guides to enable, disable, or configure new and changed Windows 11 features.

Who writes it

Thea is written by a small team, each covering the categories they know best. Every author page lists their published articles, and every article names the person responsible for it.

Maya Reyes

Maya writes Thea's update coverage. She tracks every Windows 11 cumulative and feature update on the day it ships, installs it on a test PC, and reports what changed and what to watch for. Placeholder bio — replace before launch.

Priya Natarajan

Priya writes the how-to guides for new and changed Windows 11 features: where a setting moved, how to turn it on or off, and what it does. Placeholder bio — replace before launch.

How articles are made

Every article starts from official Microsoft material: release notes, support articles and Windows Insider blog posts. We do not invent KB numbers, build numbers or error codes — if an identifier is not in the source, it is not in the article.

First drafts are AI-assisted: a model writes the draft from those sources, and an automated check then scores it for structure, thin content and identifiers that do not appear in the sources. Anything that fails waits in a review queue for a human editor.

A human editor reviews each article against its sources and tests the steps on a real PC — usually before it is published. Articles that pass the automated check can be published automatically so that same-day coverage is available quickly; the hands-on check then follows. Until it has happened, the article shows Verified: pending instead of a build number — treat it as a starting point and check back. Once checked, the article shows the build it was tested on and the date it was last verified.

When Microsoft ships a new build, affected articles are re-checked and the verified date is updated. The full process, including how corrections work, is in our editorial policy.

Independence

Thea is independent. It is not affiliated with, endorsed by or sponsored by Microsoft, and Windows is a trademark of Microsoft Corporation. We link to Microsoft’s own documentation because it is the primary source, not because of any relationship.

How the site makes money

Thea is funded by display advertising. The ad slots are managed by us, sit in fixed positions on article pages and are always labelled Advertisement. There are no affiliate links, no sponsored fixes and no paid “repair tool” recommendations — if an article recommends a tool, it is because that is the fix.

Spotted a mistake? The contact page explains how to report it and what to include.