Working Set tlwinset.com

How Windows actually works — the registry, prefetch, services, the memory manager — explained from documentation, so you can judge a speed-up claim yourself. We have not run the software we write about, and we say which parts we could not verify.

Subject Who publishes this site, and how it sources a claim Covers Publisher · provenance · method · contact We ran it No. We hold no copy and distribute none. Sourcing Microsoft documentation · archived vendor pages Ledger rows Open questions 0 Published 2026-08-05   Last verified 2026-08-05

Who publishes this site, and how does it source a claim?

Working Set is the reference a person reads before they read a review. It explains the parts of Windows that speed-up claims are claims about — the registry, the memory manager, the service control manager, prefetch, the component store — so that a reader can check a product’s promise against the documented behaviour of the surface it says it is changing.

Tenglnet published its Windows Winset utilities at tlwinset.com from roughly 2005 to 2016. The registration lapsed, the address passed through other owners, and it came to this publication in 2026. Working Set has no connection to Tenglnet, holds no copy of its software, distributes none, and has never run any of it.


§1Who publishes this

Working Set is written and published by Working Set. There is one editor, the editor is named, and every page on the site is published under that name. There is no pseudonymous byline, no rotating cast of stock authors, and no author box.

The address for corrections, sources and disputes is the contact form. It is written here as selectable text rather than as an image or a scrambled string, and it is repeated in the footer of every page. There is no contact form on this site. A form takes your message while keeping the recipient anonymous, and a publication that will not print the address messages go to has told you something about how it expects to answer them.


§2What this domain used to be

The provenance line above is not a formality and it is not buried. It appears in the footer of every page, and above the fold on every page that inherits an inbound link from the previous owner. A reader who arrived from a 2011 download catalogue in Czech, Slovak, Hungarian, Romanian, Finnish, German, Croatian, Russian or Spanish should be able to establish, in one glance, that the address is right and the publisher is not.

We never brand as Tenglnet or as Winset, never reuse their wordmark, template or colours, never reproduce their prose, and never imply continuity. The domain is our address, not our identity. Where an archived vendor page is quoted at all, the quotation is capped at 25 words, sits in a bordered claim card, and carries the archive URL and the capture date as required fields.


§3We have never run Windows Winset, and we do not have a copy

Stated plainly, because it governs every sentence on the site: we have never run Windows Winset. We do not possess a copy of it, of any Tenglnet product, or of any of the installers this domain once served. We will not obtain one, and we distribute none. No page here links to a binary, hosts a binary or mirrors a binary, and no file whose bytes are executable exists in any deploy of this site.

That is why the header block on every page carries the line WE RAN IT — No. before the first sentence of the page, rather than as a disclaimer at the bottom. It is the most important fact about the method, so it sits where it cannot be missed.

The consequence for the writing is that this site makes no first-person experience claim about any product, in any tense. We do not report what a tool felt like, how fast it was, or what it did to a machine we own, because we have not run one. What we can do instead is read the documentation for the surface a product says it writes to, state what Windows does with that surface by default, and let the reader draw the arithmetic.


§4How a claim gets sourced

Four rules do most of the work.

Primary documentation first. Behaviour of Windows is sourced to Microsoft’s own documentation, to a support article, or to Sysinternals, with the date the page was read. Secondary reporting is cited as secondary reporting and named as such. Where a widely repeated belief has no primary source behind it, the absence is reported as an absence rather than smoothed over.

Every assertion carries a provenance class in its construction. OBSERVED means we established it from a source we cite. CLAIMED means somebody else asserted it, and the sentence says who and when. UNDETERMINED means we looked, we failed, and the sentence says where we looked. There is no fourth class, and no unclassed assertion.

Vendor claims are framed as claims, in the past tense, with a capture date. “The 2012 capture of the product page advertises 50+ tools” is publishable here. “Windows Winset had 50+ tools” is not, because we have no way to check the second sentence and every way to check the first.

What we could not establish is stated inline, in the paragraph where a reader would otherwise assume we know, and never in a footnote. Every article closes with a Standing block whose Not established section is never empty. The Mechanism Ledger carries an UNVERIFIED tier, and every row in it is filed at /mechanisms/unverified/ with the single piece of evidence that would close it.

Drafting on this site is assisted by software, every factual claim is checked against a primary source by a named human before it is published, and no article makes a personal-use claim about any product. The full statement is on the colophon.


§5What this site takes money for

Nothing, at launch. Zero affiliate links, zero display advertising, zero sponsored content and zero paid placements in the Ledger. The reasoning is set out with the actual commission rates, which are not what the usual argument assumes, on /disclosures/. If that ever changes, the disclosure sits in the same visual block as the link and above it, in body-copy size, on every page carrying one.


§6How to correct us

Write to the contact form with the page, the sentence and the source. Corrections are published with the same prominence as the original claim, as dated update blocks with the original text struck through rather than deleted, and whoever got there first is named in the body of the page. The standing policy and the full corrections list are at /corrections/.

Three things we cannot help with, said here to save a message: we cannot supply Windows Winset or any other Tenglnet software, we cannot diagnose an individual machine, and we do not accept vendor-supplied review copies — accepting one would mean acquiring the experience claim this site is built to avoid.