<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">

  <title>Working Set</title>
  <subtitle>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.</subtitle>
  <id>https://tlwinset.com/</id>
  <updated>2026-08-06T00:00:00Z</updated>

  <link rel="self" type="application/atom+xml" href="https://tlwinset.com/feed.xml"/>
  <link rel="alternate" type="text/html" href="https://tlwinset.com/"/>

  <author>
    <name>Working Set</name>
    <email>editor@tlwinset.com</email>
    <uri>https://tlwinset.com/about/</uri>
  </author>
  <rights>Working Set, tlwinset.com. Corrections: editor@tlwinset.com</rights>
  <icon>https://tlwinset.com/favicon.svg</icon>

  <entry>
    <title>Windows Winset, read as an index of Windows mechanisms</title>
    <id>tag:tlwinset.com,2026:/winset/xiazai.htm</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/winset/xiazai.htm"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="claims"/>
    <category term="registry"/>
    <category term="memory"/>
    <summary type="text">The archived product page for this domain's own former software advertised roughly forty tools on Vista and fifty on Windows 7 and 8. Every one of them was a claim about a specific part of Windows. This article maps each advertised capability to the surface it must have been writing to — the registry key, the API, the service start value, the prefetch parameter — with what Windows does by default and where that is documented. It includes the "immunize disk partition" entry that nobody explains, the licensing claim we state the documented limit for and decline to describe any method of exceeding, and the address inconsistencies across the 2008, 2012 and Windows 8 captures, reported as inconsistencies and not as an allegation. The software is not available here and we have never run it.</summary>
  </entry>

  <entry>
    <title>What Windows 8 changed that broke the tweak industry</title>
    <id>tag:tlwinset.com,2026:/wineb/xiazai.htm</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/wineb/xiazai.htm"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="boot"/>
    <category term="services"/>
    <category term="memory"/>
    <summary type="text">A Vista-era tweak suite could not be recompiled for Windows 8, because Windows 8 moved or removed most of the surfaces it wrote to. Each one, and what replaced it: hybrid shutdown, and why every boot-time measurement published after 2012 measures a different operation than the ones before it; the startup surface moving out of msconfig and into Task Manager with a per-item impact rating computed by the operating system; driver signing and what it did to the class of utility that installed a kernel-mode helper; page combining and the memory-compression arithmetic; and the networking tweak that had already been automatic since Vista's receive-window auto-tuning, five years before this build was still selling it.</summary>
  </entry>

  <entry>
    <title>This URL used to be an installer</title>
    <id>tag:tlwinset.com,2026:/bulk-mailer/</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/bulk-mailer/"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="claims"/>
    <summary type="text">One address on this domain served a Windows installer until roughly 2016: a bulk email sender bundled with a spider that harvested addresses from search engines by keyword. It does not now, we do not have it, and this domain distributes no executables permanently. What the article covers instead is the engineering — multi-account SMTP rotation and one-by-one delivery, both aimed at defeating a receiver's ability to see what was happening, which is why both stopped working — the statute that names address harvesting as an aggravated violation and the careful distinction that an aggravated violation is an enhancer rather than a standalone offence, and the authentication requirements that ended the technique. Also why running any fifteen-year-old installer of unknown provenance is an unbounded risk with a bounded reward of zero.</summary>
  </entry>

  <entry>
    <title>Windows 10 or Linux, from both sides of the sentence</title>
    <id>tag:tlwinset.com,2026:/why-is-windows-10-better-than-linux</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/why-is-windows-10-better-than-linux"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="claims"/>
    <category term="memory"/>
    <summary type="text">The slug of this page argues one side and the anchor text that brings most of its readers argues the other, so the contradiction is the subject. Both sentences are checked against mechanisms rather than against preference: what each system actually does with memory, with background services, with updates and with old hardware, stated in units where units exist and marked as judgement where they do not. Includes the Windows 10 end-of-support date and the consumer extended-security route with the terms Microsoft actually published, cited to the lifecycle page with the date it was read, because the widely repeated version of those dates is wrong.</summary>
  </entry>

  <entry>
    <title>Free RAM is the wrong number</title>
    <id>tag:tlwinset.com,2026:/free-ram/</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/free-ram/"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="memory"/>
    <summary type="text">On a healthy machine, available memory is not supposed to be large — empty RAM is RAM you paid for and are not using. This article explains what a working set is, what the standby list holds, and why Task Manager's "in use" figure mixes at least four different things. Then the mechanism of the trick: 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 when the user switches windows. Verdict HARMFUL, with the loss stated as extra hard faults rather than as an adjective, the 2004 argument credited to the person who made it, and the one counter that would actually tell you whether you are short of memory.</summary>
  </entry>

  <entry>
    <title>What a "registry error" actually is</title>
    <id>tag:tlwinset.com,2026:/registry/</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/registry/"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="registry"/>
    <category term="claims"/>
    <summary type="text">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 rots or fills up, and there is no documented condition called a "registry error" for a scanner to be counting. So what is a tool counting when it reports 2,317 of them, by what definition, and with what measurable effect on anything? Includes what Microsoft's own support policy on registry cleaners says, and — because overreading a source in our own favour is not permitted here — what it pointedly does not say, even though the overreading would suit us.</summary>
  </entry>

  <entry>
    <title>What a service costs when it is doing nothing</title>
    <id>tag:tlwinset.com,2026:/services/</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/services/"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="services"/>
    <summary type="text">An idle service costs a countable number of threads, handles and kilobytes, and the count is smaller than the tweak lists assume. This article shows how to get the real figure for your own machine with tasklist /svc and Resource Monitor, works through what the service control manager does at boot in order, and explains the documented Start values under HKLM\SYSTEM\CurrentControlSet\Services — including delayed auto-start running at lowest thread priority, trigger-start registrations, and the svchost split that changed the arithmetic on machines above a documented memory threshold. It also states why "disable these forty services" is the most machine-breaking advice in this genre, with the recovery procedure for a machine already broken by it.</summary>
  </entry>

  <entry>
    <title>What happens before your desktop appears</title>
    <id>tag:tlwinset.com,2026:/boot/</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/boot/"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="boot"/>
    <summary type="text">Prefetch, ReadyBoot and SysMain are a measurement system rather than clutter. This article opens on the folder people are told to empty — C:\Windows\Prefetch, its .pf files, its ReadyBoot subdirectory and Layout.ini — explains what a .pf file records and why it makes the next launch fewer, larger and more sequential reads, and states plainly that deleting the folder makes the next several boots slower. It also gives the event log entry and the two fields that let a reader measure their own boot, so the claim in the headline is one they can check rather than take. Where the sourcing is weaker than we would like, the section says so on the page.</summary>
  </entry>

  <entry>
    <title>What "junk files" are, and what Windows already deletes</title>
    <id>tag:tlwinset.com,2026:/junk-files/</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/junk-files/"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="disk"/>
    <summary type="text">"We found 4.7 GB of junk" is meaningless without a definition of junk and a method, and none of these products publish either — "junk" is not a Windows concept, so every tool using the word is shipping a private list. This article gives the first-party list instead: the handler set Windows' own Disk Cleanup and Storage Sense will delete, because Microsoft has committed to those being safe to remove. Then the component store, which appears to be enormous and is mostly the same bytes counted twice, and the supported command that reports its true size rather than its apparent one.</summary>
  </entry>

  <entry>
    <title>Sixteen places Windows can start a program</title>
    <id>tag:tlwinset.com,2026:/autostart/</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/autostart/"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="services"/>
    <summary type="text">"Startup programs" is not one list. It is at least sixteen separate registration mechanisms, enumerated here from a primary source: boot execute, AppInit DLLs, Explorer add-ons, sidebar gadgets, image hijacks, browser add-ons, known DLLs, logon startups, WMI event subscriptions, Winsock protocol and network providers, codecs, printer monitor DLLs, LSA security providers, autostart services and drivers, scheduled tasks, and Winlogon entries. One short paragraph each: what it is, where it lives, what legitimately uses it and what breaks if it is switched off. The article opens on the capability boundary as an idea — the most credible thing any startup manager can publish is an explicit list of what it does not cover.</summary>
  </entry>

  <entry>
    <title>Measure it yourself, with what is already installed</title>
    <id>tag:tlwinset.com,2026:/measure-it-yourself/</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/measure-it-yourself/"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="claims"/>
    <summary type="text">A tool page with no downloads on it, which is both the editorial point and the reason this site never needs an affiliate link to a utility. Nine in-box instruments, what each one actually measures, and the exact counter to watch for each claim this site examines: the four Performance Monitor counters that matter here and what each does not mean, Resource Monitor's hard-faults column, Task Manager read correctly with the overlap between "in use", "cached", "committed" and "compressed" made explicit, the boot timing entries in the event log, and the supported way to get the component store's real size. The governing principle is stated first: if a claim cannot be confirmed or refuted with something already on the machine, treat it as unfalsifiable and stop.</summary>
  </entry>

  <entry>
    <title>How one XML file put a two-person vendor on a thousand download sites</title>
    <id>tag:tlwinset.com,2026:/one-xml-file-nine-languages/</id>
    <link rel="alternate" type="text/html" href="https://tlwinset.com/one-xml-file-nine-languages/"/>
    <updated>2026-08-06T00:00:00Z</updated>
    <published>2026-08-06T00:00:00Z</published>
    <category term="claims"/>
    <summary type="text">The most under-documented piece of 2000s software history is the PAD file — Portable Application Description, a flat XML document of nested elements describing a product, its price, its download URL and its descriptions at three lengths. The vendor hosted one file, catalogues polled it, and listings updated themselves. This is the direct, mechanical explanation for why this domain carries backlinks in Czech, Slovak, Hungarian, Romanian, Finnish, German, Croatian, Russian and Spanish, and it is the reason link counts from that era measure distribution rather than endorsement. Adoption figures are pinned to a primary source or stated as reported, with the reporting named.</summary>
  </entry>

</feed>
