Every tool in this suite was a claim about one specific part of Windows. Here is the list, and here is each part.

The archived help index for this product enumerates twenty-eight numbered capabilities, and every one of them is a claim about a named surface: a registry value, a Win32 call, a service Start type, a folder at a volume root, a licensing timer. That is what makes a dead 2012 utility worth an article. You cannot check a tool you cannot run, but you can check the operating system it claimed to be changing — Microsoft documents most of these surfaces, states a default for many of them, and in several cases says outright that the setting is no longer read.

You probably arrived here from a download portal. A third-party backlink index reports two links at this exact URL, from deutschedownloads.de and downloadcentral.fi, which listed this page as the download for Windows Winset; we have not inspected either placement ourselves. The listing is roughly fourteen years old, the vendor stopped publishing around 2016, and the domain is ours now. What follows is not the software. It is the software’s own feature list used as a table of contents for how Windows actually works.

---

§1The software is not on this page, and the three download mirrors it advertised no longer answer

Last vendor capture we read

2016-04-23

Advertised mirrors still resolving

0 of 3, checked 2026-08-06

Cost of not installing it

0 bytes, 0 reboots

This domain distributes no executables and never will. That is a standing policy rather than a property of this page, and it is stated the same way on the page for the other binary this domain once served.

The 2012 capture of this URL offered the download three ways, labelled Europe, America and Asia. Read as engineering rather than as marketing, those labels are three different hosts: the Europe link pointed at a Google Code project, the America link at the vendor’s own /update/ directory, and the Asia link at a third party on a .org.cn host. We requested all three on 2026-08-06: the Google Code URL returns HTTP 404 and the other two do not complete a connection. Google Code project hosting no longer serves files at all. So the practical situation is that the product is obtainable, if it is obtainable, only from redistributors — which is the worst possible provenance for a program that installs itself with the privilege needed to rewrite service start types and the Winlogon key.

We think the correct advice is the flat one, and we label it as our judgement: do not hunt for this installer. A fifteen-year-old system-level utility from a vendor that stopped publishing has an unbounded downside and, as the rest of this article shows, a bounded upside of approximately zero, because Windows has since absorbed most of what it did.

---

§2The vendor’s own numbers disagree with each other across captures

Advertised tool count

40+ (2008) · 50+ and 40+ on one page (2010) · 50 (2012)

Advertised price

$19.95 (2009) · $19 (2012-03) · $29 (2012-08)

Advertised download size

8.0 MB (2009, 2010) · 4 MB (2012)

Everything in this section is claimed, by the vendor, on a dated capture we fetched ourselves. None of it is a measurement and none of it is our assertion about the product.

Capture	Page	What it advertises
2008-10-24	/index.htm	Vista Winset Utilities v2.0, more than 40+ tools, for Vista and XP/2003/2000; ten named modules
2009-11-03	/winset/xiazai.htm	Version 3.9, $29.95 struck through to $19.95, 8.0 MB, three download links
2010-05-30	/main.htm	Windows WinSet v4.0.8, “more than 50+ tools” and “more then 40+ windows utilities” in adjacent sentences; $19.95; 8.0 MB
2012-03-07	/winset/xiazai.htm	More than 50 tools, 19$, 4 MB, mirrors labelled Europe / America / Asia, plus a separate XP build
2012-08-23	/main.htm	Version 2011, $49 struck through to $29, 4 MB, Home licence $29 for one computer and Professional $39 for three, 32-bit and 64-bit, no XP
2016-03-16	/winset/help.htm	An index of 28 numbered capabilities, each with its own help topic

Three things are worth naming rather than smoothing over. The tool count is a range, not a figure: the same 2010 page says 50+ in one sentence and 40+ in the next, which means the number was never a count of anything. The price on the download page and the price on the product page disagree within the same year — 19$ in March 2012, $29 in August 2012 with $49 struck through — and a struck-through price with no stated reference period is a presentational device rather than a fact about what anyone paid. And the download shrank from 8.0 MB to 4 MB between 2010 and 2012 while the advertised tool count went up. We cannot tell you what that means, because we do not have either build; we can tell you that both numbers are the vendor’s, on captures dated four years apart, and that they are the kind of figure a buyer’s test should ask about. That test is the standing preamble at the Ledger.

---

§3Each advertised capability, mapped to the Windows surface it must have been writing to

Items in the archived index

28, capture 2016-03-16

Items with a documented surface

18 named · 6 with none we could find · 4 not OS settings

Items with a Ledger row

11 of 28, plus 6 from the 2008 module list

This table is why the article exists. The middle column is not what the product did — we have not run it and we make no claim about its code. It is the surface the advertised behaviour must touch on Windows if the claim is true at all, which is a statement about the operating system and is checkable against Microsoft’s documentation. Where we could not find a documented surface, the cell says so. Where a claim–surface pair has a row in the Mechanism Ledger, the row id is a link and carries the documented default, the version boundary and the verdict.

Six entries in that table name no surface we could document, and that is the finding rather than an omission. Two of them — the one-click optimiser and the checklist with a Recommend button — are the commercially important ones, because they are where the product decided on the user’s behalf what to change. The vendor never published which settings either one wrote, which is the second question in the Ledger’s standing preamble: does the product publish a capability boundary? Sysinternals’ Autoruns does, as a table of command-line switches. Almost nothing in this category does, and a Recommend button whose recommendations are unpublished cannot be checked by anyone, then or now.

Item 6 is the clearest case in the table, so it is worth following all the way down. Windows exposes the free-memory figure through GlobalMemoryStatusEx, and Microsoft’s definition of that figure is explicit: available physical memory “is the sum of the size of the standby, free, and zero lists”. The standby list is the file cache. It is already counted as available and it is already handed to any process that asks for memory. A trigger that fires when that number drops below 30% is therefore firing on a condition that is not a shortage. And the documented way to move the number is EmptyWorkingSet, which Microsoft describes as removing “as many pages as possible from the working set of the specified process”. A working set is by definition the pages resident in physical memory, so every page removed has to be faulted back from disk on next access. A single trim recovers. A timer guarantees the recovery never completes. That is row M-01, verdict HARMFUL, and the full argument, including what changed after 2013, is the memory article.

Item 16 rests on the premise in that card, and Microsoft documents that the premise stopped applying more than twenty years ago. The registry size quota is a Windows 2000 concept; the current reference page states that on Windows XP and Windows Server 2003 “there are no explicit limits on the total amount of space that may be consumed by hives”. Row R-01 is SUPERSEDED for that reason and carries the single exception, which we do not suppress. What Microsoft says about registry cleaners themselves is narrower than the folklore, and this site refuses to overread it even though the overreading would suit us: the retired support policy says Microsoft does not support their use, is not responsible for problems they cause, and makes no warranty about their performance or reliability. It does not say they fail to make a computer faster. It is a support-scope and liability position, not a measurement. The current and better citation is Microsoft’s unwanted-software criteria, which name displaying exaggerated claims about device health and making misleading or inaccurate claims about registry entries as grounds for classification. The registry article works through what a scanner is actually counting.

Item 3 is the honest one. Removing a program from the Run keys and the Startup folders is the one intervention knowledgeable users consistently endorse, and it is reversible. It is also the item the operating system took back: since Windows 8 the Startup tab in Task Manager lists those same locations and computes an impact rating for each entry, and Microsoft publishes the thresholds — high impact is more than one second of CPU time or more than 3 MB of disk I/O at startup, medium is 300–1000 ms or 300 KB–3 MB, low is under both. That is a better instrument than an unlabelled list, and it costs nothing. The in-box list has the same documented gap the paid tools had — it covers Run, RunOnce and the Startup folders and not scheduled tasks — which is the subject of the sixteen-surfaces article. One more documented property is worth carrying: Microsoft states that when more than one program is registered under a Run key, “the order in which those programs run is indeterminate”. Any tool that presents startup entries as an ordered sequence is presenting something the platform does not promise.

Item 4 deserves a sentence of its own, because it is the one place where the module list touches security directly. Automatic logon is a documented Windows feature and Microsoft documents its cost in the same page: when it is turned on, “the password is stored in the registry in plain text”, in a key that can be read remotely by the Authenticated Users group. The archived help topic for this item sells the feature as solving the problem of not setting a password. That framing is the opposite of what the documented mechanism does, and it is the sort of inversion a reader can check in one fetch.

The 2008 Vista product page named ten modules, six of which map to Ledger rows that the 2016 index no longer advertises. They are worth recording because they date the product to the era it came from.

2008 module	Surface	Ledger
Accelerate menu display speed	HKCU\Control Panel\Desktop\MenuShowDelay, REG_SZ, documented default 400 ms	R-04
Set the desktop icon cache size	...\Explorer\Max Cached Icons. No Microsoft reference page exists for it	R-11
Optimised CPU priority and delay time	...\Control\PriorityControl\Win32PrioritySeparation, documented default 0x2	R-05
Automatically close non-responding applications	HKCU\Control Panel\Desktop\AutoEndTasks, documented default 0	R-09
Auto-set MTU, MSS and transmission unit cache size	...\Services\Tcpip\Parameters\TcpWindowSize · netsh interface ipv4 set subinterface mtu=	S-09 S-11
Customise the right-click menu	...\Shell Extensions\Approved	A-06

The networking module is the cleanest demonstration of the whole thesis, and the demonstration is not ours to make here: receive-window auto-tuning, and the registry value it stopped reading, belong to the Windows 8 article, which owns that discontinuity and quotes Microsoft on it. The fact this section needs is only the date. This product was still advertising a tweak for that value in 2008, two operating-system generations after the platform stopped reading it.

---

§4“Immunize disk partition” meant occupying a filename, and the threat it addressed was closed by a Windows update

Surface it touches

1 directory named autorun.inf per volume root

Microsoft pages documenting the technique

0

KB 971029 at support.microsoft.com

HTTP 404, checked 2026-08-06

This is the most interesting entry in the list and the one nobody explains, so here it is in mechanism terms. In the late 2000s a large family of worms spread by removable media. The vector was autorun.inf: a plain text file at the root of a volume, naming a program for Windows to offer or to launch when the volume was attached. “Immunisation” is a filesystem trick, not a security product. A directory and a file cannot share a name in the same directory, so if something already occupies the name autorun.inf — a folder, ideally one whose permissions make it awkward to remove — the worm cannot create its file there.

Two things follow, and the second one is why this row is UNVERIFIED rather than settled. First, the technique is undocumented: it is not described on any Microsoft page we could find, so there is no stated default to restore, and the two values Microsoft does document for this purpose, NoDriveAutoRun and NoDriveTypeAutoRun, come with an explicit warning that “applications should not modify these values, as there is no way to reliably restore them to their original values”. A tool operating in this area is operating where Microsoft has told applications not to.

Second, the threat was closed from the platform side. The AutoRun restriction update for Windows XP and Vista, KB 971029, limited AutoRun entries in the AutoPlay dialog to optical media and was pushed broadly in early 2011; on Windows 7 and later the restriction is the default behaviour. We would rather cite that update directly than describe it, and we cannot: on 2026-08-06 the numeric URL support.microsoft.com/help/971029 returns HTTP 404, and the article does not resolve at any support URL we requested. So the version boundary here is recorded as an absence. Microsoft’s AutoPlay registry page remains live and is what row D-06 cites. The honest statement is that the technique addressed a real threat, that the platform closed that threat around fifteen years ago, and that we could not read the update that closed it.

---

§5The licence feature advertised 360 days; the documented mechanism stops at 120

Documented grace period

typically 30 days

Documented rearms

3 maximum, per KB 929828

Documented ceiling vs advertised

120 days vs 360 days

The documented mechanism in this family is public and short. Microsoft’s unattend reference for SkipRearm states that the activation grace period “is typically 30 days”, beginning after Setup finishes and the machine boots for the first time, and that on Windows 7 and Windows Vista there is a limit to the number of times Windows can be rearmed. The support article on sysprep /generalize, KB 929828, gives the number: “the Rearm process can be run a maximum of three times in a Windows image.” Thirty days plus three resets of thirty days is one hundred and twenty. That is the ceiling the documentation describes, and it is a fact, not an opinion.

The advertised figure is three times the documented ceiling, and the archived help topic sets out how it is reached: repeated use of a menu item, with an option to be ticked once the feature has been used three times, taking it from four to twelve. Twelve times thirty is three hundred and sixty. We state the arithmetic because it explains where a strange number came from. We do not describe how the option works, we name no procedure, and we publish no value a reader could apply. Row R-12 carries the verdict UNSAFE-CLAIM for exactly this case, and it is the only one in the table.

The thing worth noticing is not the technique. It is the business decision. A paid commercial utility shipped a licence-grace extension as a bundled feature, in the same menu as a 7-Zip front end and a timed shutdown, in a product sold through mainstream download catalogues in nine languages. That is a fact about how this category behaved in 2012, and it is the kind of fact that a review of the software could never have established, because you would have had to read the help file rather than the box.

---

§6Tenglnet’s own address and company name change between captures, and we report that as an inconsistency

Captures read

6, dated 2008-10-24 to 2016-04-23

Distinct company names

4 · distinct street-address countries: 2

Inferences about intent or legality

0 — see this section

The eighth question in the Ledger’s standing preamble is whether the vendor’s identity stays the same on every page, because a consistent answer is the cheapest trust signal available and its absence is information. This domain is the worked example, so we owe it precisely.

The 2008 home page gives the company as Tenglnet Share Software Net Science & Technology Co., Ltd, with a street address of E-98, Chitranjan Marg, C-Scheme and a telephone number beginning +91-141. That page names no city at all: the address line ends at the neighbourhood. The country code and area code are India and Jaipur respectively, and C-Scheme is a Jaipur district, so the reading is easy — but the page does not say it, and we are not going to write a city onto a page that omits one. By 2009 the same street address appears on the download page with a different phone number. By 2010 the product page carries the same street address, a company styled Tenglnet Share Technology Co., Ltd, and a Chinese ICP number, 10025419, in the footer. By August 2012 the product page gives the address as E-98, Chitranjan Marg, Washington, DC, United States of America, under the name Tenglnet Software Company, with the same ICP number still in the footer and a copyright line reading Tenglnet Software Science & Technology Company. Contact addresses across the captures run through live.cn, 126.com, live.com and the domain itself.

One correction to our own earlier notes, which is the kind of thing this site prints rather than edits away: the ICP number is not confined to the Windows 8 pages. It is in the footer of the 2010 product page, the 2012 capture of this download page and every 2016 help topic we read. It has been present alongside the United States address the whole time.

We report the inconsistency and we stop there. We make no claim about where anyone was, what any of it meant, or whether any of it was lawful, and we do not publish inferences about intent. This pattern — a street address that migrates between countries, several company names that differ by a word, free webmail contacts, a national registration number that does not match the stated country — was characteristic of the mid-2000s international shareware trade, and it is a legitimate subject for a publication that cares about who is behind a system utility. Whoever they were, they wrote their own help file, which is more than several better-known vendors in this category managed.

---

§7There is no screenshot on this page, and there will never be one

Screenshots on this site

0, permanently

Vendor images republished

0

Generated or recreated interface

0 pixels

Three sentences, because it comes up on precisely this page. We cannot make our own screenshots of Windows Winset: we do not have the software, we will not obtain it, and we would not redistribute it if we did. We may not republish the previous owner’s captures, which are their work and not ours to reprint. And a fabricated or model-generated picture of this program’s interface would be a misrepresentation rather than a design choice, which is why the images on this site are schematic diagrams with no window chrome in them at all. The longer version, including what we do instead, is at why this site has no screenshots. The archive holds one image path under a down. subdomain that this site pointedly does not rebuild, and that omission is deliberate.

---

§8The thirty-two language links were a translation widget, not a localisation

Entries in the language menu

32 locales, plus 1 label

Pages the vendor translated

0 — every entry is a machine-translation URL

Mirrors labelled by continent

3, on 3 unrelated hosts

The inbound links to this domain sit on download portals in Czech, Slovak, Hungarian, Romanian, Finnish, German, Croatian, Russian and Spanish, and the obvious explanation has always been the language menu on the product pages. We read the menu’s markup in the 2012-03-07 capture of this URL, and the obvious explanation is wrong. The menu is a select element with thirty-two entries, and every entry’s value is a translate.google.com URL carrying langpair=en|fr, en|de and so on, pointed back at this same page. The vendor published one language. The rest was a widget.

That matters for anyone reading a link profile as evidence. Thirty-two locales on a page look like international reach and cost nothing to add; nine languages of inbound links look like popularity and are also not what they appear to be. The actual mechanism behind the multilingual listings is a single XML file, and it is its own article: a PAD file put a very small vendor into a thousand download catalogues, in every language those catalogues published in, without a single editorial decision being made about the product. Link counts from this era measure distribution, not endorsement. The two links reported at this address are from catalogues of exactly that kind.

---

§9If you arrived wanting a tune-up, the instruments are already installed

Cost of the in-box instruments

$0, 0 downloads

Windows 7 end of support

2020-01-14

Windows 10 end of support

2025-10-14

Every version of Windows this product was built for is out of support. Microsoft publishes the dates in one table: Windows Vista ended on 2017-04-11, Windows 8 on 2016-01-12, Windows 7 on 2020-01-14, Windows 8.1 on 2023-01-10 and Windows 10 on 2025-10-14. If you followed this link on a machine running Windows 7, the useful answer is a security answer with a date on it rather than a performance answer, and no utility changes it.

If you are on something current and the machine feels slow, the honest starting point is measurement, and every instrument worth using ships with Windows or is published free by Microsoft: Task Manager’s Startup tab with its documented impact thresholds, Resource Monitor for hard-fault rate, the Diagnostics-Performance operational log for boot timings, Autoruns for the autostart surfaces a startup manager does not show you, and DISM /Online /Cleanup-Image /AnalyzeComponentStore for the true size of WinSxS, which File Explorer reports wrongly because it counts hard-linked files more than once. Which counter answers which claim is a page of its own, and nothing on it needs to be downloaded.

The one item in the 2016 list we would still call worthwhile is item 20, and it is a backup feature rather than a cleaning feature: taking a copy of a hive before changing anything. The supported forms are reg save per hive and a System Restore point, and both are in the box. A tool that backs up before it writes and lets you undo one item six months later is answering the seventh question in the standing preamble. A tool that reports a count of problems and offers to fix them is not.

---

§10What this article establishes, what it infers, and what it could not settle

Documented from a primary source

18 surfaces, 22 Ledger rows

Inferences, labelled as such

3

Not established

5 items, listed below

---

§11Sources, and how this piece was researched

Numbered sources

28

Fetched by us

28, on 2026-08-06

Archived vendor pages

10 captures, 2008–2016

Method, in one sentence: we fetched every archive capture and every documentation page listed below ourselves on 2026-08-06, read the vendor’s own help topics for the capability list rather than the marketing copy, mapped each advertised capability to the Windows surface it would have to touch, and recorded as a gap every item for which we could not find a primary source — the five gaps are named in §10 rather than smoothed over, and no statement in this article rests on having run the software, which we have not.

Archived vendor pages, cited only as evidence of what was claimed:

1. Vista Winset Utilities product page, tlwinset.com/index.htm, capture 2008-10-24. Accessed 2026-08-06.
2. Windows Winset download page, tlwinset.com/winset/xiazai.htm, capture 2009-11-03. Accessed 2026-08-06.
3. Windows Winset product page, tlwinset.com/main.htm, capture 2010-05-30. Accessed 2026-08-06.
4. Windows Winset download page, tlwinset.com/winset/xiazai.htm, capture 2012-03-07 — the source for the mirrors, the price, the 4 MB figure and the language menu markup. Accessed 2026-08-06.
5. Windows Winset product page, tlwinset.com/main.htm, capture 2012-08-23 — the source for the licence tiers and the United States address. Accessed 2026-08-06.
6. Windows Winset help index, tlwinset.com/winset/help.htm, capture 2016-03-16 — the twenty-eight numbered capabilities. Accessed 2026-08-06.
7. Help topic, boot speed, capture 2016-04-23. Accessed 2026-08-06.
8. Help topic, memory, capture 2016-04-23. Accessed 2026-08-06.
9. Help topic, registry, capture 2016-04-23. Accessed 2026-08-06.
10. Help topic, disk immunisation, capture 2016-04-23. Accessed 2026-08-06.
11. Help topic, licensing, capture 2016-04-23. Accessed 2026-08-06.

Microsoft documentation, primary unless noted:

12. EmptyWorkingSet function (psapi.h). Accessed 2026-08-06.
13. MEMORYSTATUSEX structure (sysinfoapi.h). Accessed 2026-08-06.
14. Registry storage space. Accessed 2026-08-06.
15. Microsoft support policy for the use of registry cleaning utilities (KB 2563254), archived capture 2020-12-27; unpublished by Microsoft and readable only in an archive. Accessed 2026-08-06.
16. How Microsoft identifies malware and potentially unwanted applications. Accessed 2026-08-06.
17. Run and RunOnce registry keys. Accessed 2026-08-06.
18. Startup apps, with the Task Manager startup-impact thresholds. Accessed 2026-08-06.
19. The HKLM\SYSTEM\CurrentControlSet\Services registry tree, with the Start value table. Accessed 2026-08-06.
20. Guidance on disabling system services on Windows Server 2016 with Desktop Experience — server-scoped by its own statement. Accessed 2026-08-06.
21. Turn on automatic logon in Windows, with the plaintext-password warning. Accessed 2026-08-06.
22. Enabling and disabling AutoRun. Accessed 2026-08-06.
23. SkipRearm, with the 30-day activation grace period. Accessed 2026-08-06.
24. Error when running sysprep /generalize (KB 929828), which states the three-rearm maximum. Accessed 2026-08-06.
25. User Account Control settings and configuration. Accessed 2026-08-06.
26. SMB: No registry setting for tuning the TCP window size in TCP/IP should exist (archived), which states that TcpWindowSize is ignored. Accessed 2026-08-06.
27. Determine the actual size of the WinSxS folder. Accessed 2026-08-06.
28. Windows 7 support ended on January 14, 2020, which carries the end-of-support table for every version named in §9. Accessed 2026-08-06.

Recorded by its absence, because it changed a verdict: support.microsoft.com/help/971029, the AutoRun restriction update cited everywhere as the end of the autorun.inf threat, returned HTTP 404 to us on 2026-08-06.

---

Previous: The Mechanism Ledger — every claim this category sells, joined to the operating-system surface it must be touching if the claim is true at all.
Next: What Windows 8 changed that broke the tweak industry — a Vista-era suite could not be recompiled for Windows 8, because Windows 8 moved or removed most of the surfaces it wrote to.