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 Four doors, one per question a reader arrives carrying Covers Winset downloads · startup items · memory meters · registry scans We ran it No. We hold no copy and distribute none. Sourcing Microsoft documentation · archived vendor pages Ledger rows see each article Open questions 0 Published 2026-08-05   Last verified 2026-08-05

You landed here from an old link. Which page do you actually want?

Most people reading this arrived on a URL that was published somewhere else, years ago, pointing at software. They did not choose this site; a download catalogue chose it for them. So rather than a tour, here are four doors, each one labelled with the question a reader was carrying when they clicked, and each one opening on the single article that answers it.

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.

§1You clicked a link to download Windows Winset and got a website instead

The software is not here. We do not have it, we do not distribute it, and we have never run it — this domain was Tenglnet’s address until about 2016 and it is ours now, which is a change of tenancy rather than a continuation. Nobody should install a 2012 system-level utility of uncertain provenance on a machine they care about, and that sentence is the shortest useful thing on this page.

What replaced it is more useful than the download would have been. The archived product page advertised something in the order of forty tools on Vista and fifty on Windows 7, and every one of those tools was a claim about a specific part of Windows: a registry key, a service start value, a memory API, a prefetch parameter. The article takes that feature list as a table of contents and maps each advertised capability to the surface it must have been writing to, with what Windows does with that surface by default and where that is documented.

Go to: Windows Winset, read as an index of Windows mechanisms — SUPERSEDED, with every capability the product advertised mapped to the mechanism underneath it.

If your link was specifically the Windows 8 build, the companion piece is What Windows 8 changed that broke the tweak industry, which is about that release in particular: hybrid shutdown, the startup surface moving into Task Manager, driver signing, and the networking tweak that had already been automatic for two operating-system generations by the time it was still being sold.

§2Something starts with Windows and you cannot find where it is set

This is the one intervention that knowledgeable users consistently endorse, and it is also the one where the tools are least honest about their coverage. “Startup programs” is not one list. It is at least sixteen separate registration mechanisms — the Run and RunOnce keys under two hives, the Startup folder, services, drivers, scheduled tasks, trigger-start registrations, Winlogon entries, BootExecute, WMI event subscriptions, shell extensions, AppInit_DLLs, image file execution options, codecs, printer monitor DLLs, Winsock providers and LSA security providers.

A startup manager that shows you one list is showing you a subset, and the useful question to ask any such tool is which of the sixteen it does not cover. The article enumerates all of them from the primary source, says what each is for, where it lives and what breaks if you switch it off.

Go to: Sixteen places Windows can start a program — TRADE for removing a named entry from a surface you can look up, DEPENDS for whether a given manager covers the surface your problem is actually on, and UNVERIFIED for the coverage of any tool that has never published a list. The full enumeration, with the capability-boundary question every startup manager should be made to answer in public.

§3A meter says your memory is nearly full and something offered to free it

On a healthy machine, free memory is not supposed to be large. Empty RAM is RAM you paid for and are not using, and Windows works continuously to keep it occupied with pages it expects you to want. The number a memory cleaner moves is not a measure of how much memory you have available; it is a measure of how much the operating system has been persuaded to throw away.

The mechanism is documented and the article names it: an application can ask Windows to trim another process’s working set, at which point the meter drops and the pages are read back from disk the moment you switch windows. The meter improves. The machine does more work. The article states the loss as extra hard faults rather than as an adjective, credits the person who established the argument in 2004, and ends on the one counter that would actually tell you whether you are short of memory.

Go to: Free RAM is the wrong number — HARMFUL for memory cleaning on a timer, NO-OP for a free-memory percentage trigger. The first names the mechanism of the loss; the second names why the trigger fires on a figure that already counts the file cache as available, and so is not a shortage.

§4A scan reported thousands of registry errors and wants payment to fix them

Start with what the registry is: a handful of files in %SystemRoot%\System32\config plus a per-user NTUSER.DAT, holding a key-value store that Windows reads constantly and quickly. It is not a substance that accumulates, degrades or fills up, and there is no documented condition called a “registry error” that a scanner could be counting.

So the useful question is not whether the count is high. It is what the tool is counting, by what definition, and whether removing those entries has any measurable effect on anything. The article works through what the scanners typically enumerate, what Microsoft’s own support policy says about running one — and, because overreading a source in our own favour is not allowed here, what that policy pointedly does not say.

Go to: What a “registry error” actually is — SUPERSEDED for the size premise, UNVERIFIED for the cleaning claim and UNVERIFIED for the count, with the definition problem stated first. Note which code is absent: a scan that reports a count and no per-item key path has named no surface, so the claim can be neither confirmed nor refuted, and the row therefore reads UNVERIFIED rather than NO-OP.

§5Where to go once a door has been opened

Two places. The Mechanism Ledger is the artifact the rest of this site is built around: one maintained table in which every row is a claim joined to the operating-system surface it must be touching if the claim is true at all, with the documented default, the release at which it stopped being true, the counter that would move, a verdict, and what breaks if you apply it anyway. Rows we could not settle from a primary source are filed at /mechanisms/unverified/ with the single piece of evidence that would close each one, and every edit to a row is dated at /mechanisms/changes/.

And Measure it yourself, with what is already installed, which is a tool page with no downloads on it — nine instruments that ship with Windows or are published free by Microsoft, what each one measures, and the exact counter to watch for each claim this site examines. If a claim cannot be confirmed or refuted with something already on your machine, that is itself the finding.

The complete archive, as a list of settled claims with a verdict against each, is on the front page. Twelve pieces, no excerpts, no pagination.