Repository navigation
Releases
PoolWatch v1.0.0
PoolWatch 1.0.0, the first stable release. Install it with the signed setup, PoolWatch-v1.0.0-setup-win-x64.exe, and report a problem with Report an issue... in the tray menu (a security problem privately, as SECURITY.md says).
If you have a 1.0.0 beta: run this setup over it, and uninstall (if you want to) only after that, with this
version's uninstaller; if the setup says the update finishes when Windows next restarts, restart first. From this
release on, PoolWatch's own update check tells you when a new stable version is out.
Changes since 1.0.0-beta.2
- What PoolWatch keeps on disk is your choice. Reports only, the default, writes a report each time the pool
grows and keeps no record of the day. Detailed recording also keeps a record of the whole day and report
folders for spawn storms. Choose in setup's new Records step, or under Records in Settings. If you had
1.0.0-beta.2, which always recorded, you get Reports only, and the Records step opens on its own to ask you once. - Settings... in the tray menu, in either view.
- Notices you can click, and choose. A click on a growth notice opens PoolWatch. Under Notifications in
Settings, choose a notice for every growth, only when it needs attention, or none. Starting PoolWatch while it runs
brings its window to the front, and its tray icon comes back after Windows' taskbar restarts. - Lighter under agentic load. On a PC starting hundreds of processes a minute, PoolWatch's per-sample analysis
takes 0.14% to 0.17% of one core, where it took 2.6%, and holds about 40 MB of managed memory from the sixth hour
on, where it held 101 MB after 4 hours and rose. PoolWatch as a whole is still over its own budget on such a PC;
About and every report say how much. - Lighter on the disk. Git Bash's copies of itself no longer count as a spawn storm, and one program's storms
within an hour share one report folder. Reports are written within a disk budget. With Detailed recording, the
day's files write about 2.1 MB an hour where they wrote 4.7 MB. - Incident reports that hold together.
- An incident's
events.csvholds both ends of the window its report shows: the first 500 events from where the
report says the growth started, and the latest 500, with a row saying how many were left out between them. It
matchesreport.md, late events included. - A trace you start with Capture now gets a report that covers exactly your trace, from its start to its end.
- A closed incident's report says when each level was measured ("244 MB at 07:05:53") and what was so at the close.
- The non-paged pool's title names the limit it went over ("Non-paged pool over 5.0 GB and rising").
- When another program holds a closed incident's report file open, PoolWatch tries again about once a minute and
once as it stops; while that file istimeline.csvorprocesses.csv, the rest of the report is written
meanwhile. - The draft bug report lists only the files the folder holds.
- An incident's
- Memory given back. Closing one of PoolWatch's windows gives back the memory it used, and About and Report an
issue give PoolWatch's working set as it is now. - No error box when Windows switches desktops. The Pool causes page no longer shows an error box, or stops
laying out, when Windows switches desktops (a lock, a UAC prompt) while it lays out. - Updated components: TraceEvent 4.0.0, System.Management 10.0.14, and the test and CI tools.
What is in PoolWatch 1.0.0
The first public release. PoolWatch keeps a Windows 11 PC fast and stable through long days of agentic coding: it
watches the kernel pool, empties the standby cache before the pool slows you down, fixes known issues and, if you
want, trims background work. Every change it makes is listed, with a way to put it back.
- What PoolWatch keeps on disk is your choice. PoolWatch watches the kernel pool live and tells you when it grows
either way. Reports only, the default, writes a report each time the pool grows and keeps no record of the day
(beside the reports, only its log, its settings, a summary of each boot and the Since boot report);
Detailed recording also keeps a record of the whole day (the pool and its tags, programs and their handles,
services, every program started) and report folders for its spawn storms, up to about 60 MB a day on a PC doing heavy
agentic coding. Choose in setup's new Records step, or under Records in Settings (Settings... in the tray
menu, in either view), where a change applies at once; both also set when reports, records and exports are cleaned
up (7 days by default). People upgrading from 1.0.0-beta.2, which always recorded, get Reports only and are asked
once to choose: the Records step opens alone at the first start, and again at each start until they press Done or
save a change of the record mode or the cleanup in Settings. What beta.2 recorded is cleaned up by the usual rule. - Setup that fits itself to your PC. At first start, Set up PoolWatch opens on its own, in eight short steps
(about 3 minutes), before the main window. It reads the PC and lists each known cause of a growing kernel pool with
how much it affects this PC, the highest first (high, medium, low, not known where it could not check, then none), and
which step fixes it. You choose when PoolWatch empties the standby cache (on a schedule, at a pool size, whichever
comes first, or decide later) and the fixes that fit: starting at sign-in (a sign-in task you turned off shows as
off, and stays off unless you switch it on), the token-leak guard if this Windows build has the leak, a Codex shortcut
without its shader cache when the Codex app is installed, and where to find Defender's performance mode for a Dev
Drive. The token-leak check says plainly what it found. On the steps that change things, Next pauses for a second,
so you can read what it will do. Setup changes no services. Last, you choose what PoolWatch keeps on disk.
How PoolWatch works, from every step, explains the
kernel pool and why emptying the cache is safe. The first time, closing setup asks first, with No (keep it open) the
default; if you close it, PoolWatch keeps running in the tray, what you set with Next stays, and setup opens again
when you open PoolWatch and at its next start. Open setup again from the tray menu: Run setup again...; and
Settings from there too, Settings..., in either view. - Watches the kernel pool. The kernel pool is the memory Windows and its drivers keep for themselves. PoolWatch
sits in the tray, checks it every 10 seconds with little overhead, and when it grows works out which program,
service or driver is behind it, and says how sure it is. - Notices you can click, and choose. When the kernel pool grows, a notice by the clock says what grows; a click
on it opens PoolWatch's window. Under Notifications in Settings, choose a notice for every growth (the
default), only when it needs attention (when the tray icon turns red, so a growth's notice comes once a trace
confirms its cause), or none; the token-leak guard's notices, which need your click, always appear. Starting
PoolWatch while it runs brings its window to the front, and its tray icon comes back after Windows' taskbar restarts. - A Simple view that shows, not tells. The kernel pool now, an arrow for which way it went in the last 10
minutes, when the next cache clear runs (with a ring that fills as it comes) and what the last one freed; four tiles
for the last 6 hours (growth per hour with the clears added back, what the clears freed, the net change, and the
memory in use); the graph, with a mark at every cache clear; and Get more from PoolWatch, up to three cards for
what PoolWatch found on this PC and for parts of the app you may not have found. It stays calm, and turns red only
for a real risk. - An Advanced view with the details. A graph of the last hour, 6 hours or 24 hours (the time before PoolWatch
started shows as a labelled band), with the growth and clears beside it, and Show RAM, on at first, for RAM in
use, the cache and free memory behind it. Pool causes lists what grew, what the clears freed of it, its impact,
the likely cause and how sure PoolWatch is, with what PoolWatch already does about it. Every list sorts by the column
you click. The Pool causes page no longer shows an error box, or stops laying out, when Windows switches desktops (a
lock, a UAC prompt) while the page is laid out, as when its window resizes. - Clears the cache automatically. On PCs with plenty of memory, Windows' file cache can hold file records in the
kernel pool and grow it by gigabytes, above all on ReFS drives such as a Dev Drive. PoolWatch can empty the standby
cache on a schedule, when the pool reaches a size, or whichever comes first, and shows what each clear freed. Your
files and programs are not touched. A clear takes a few seconds, and video or the mouse may stutter while it runs:
PoolWatch says so where you turn clearing on. - Tells its own cache clears apart. What PoolWatch's own cache clear frees is reported as the clear's result, not
as the pool or one kind of kernel memory (a pool tag) falling, everywhere it reports growth. Growth after a clear
counts from the level the clear left, growth before it still counts, and each alert keeps its own time span and
size. A pool tag's growth in the 2 minutes until a clear is measured counts as the clear's, so a leak just over an
alert's size that the clears keep trimming can go unreported: at the default 10-second sampling, up to about 4% over
the hourly growth alert with hourly clears, and about 8% with clears every 30 minutes (or in an hour where a light
clear is followed by a full one); more with a longer sampling int...
PoolWatch v1.0.0-beta.2
A second beta of PoolWatch 1.0.0, for testing: install it with the signed setup, PoolWatch-v1.0.0-beta.2-setup-win-x64.exe, and report a problem with Report an issue... in the tray menu (a security problem privately, as SECURITY.md says).
If you have 1.0.0-beta.1: run this setup over it, and uninstall (if you want to) only after that, with this
version's uninstaller; if the setup says the update finishes when Windows next restarts, restart first. PoolWatch's own
update check offers only stable releases, so beta.1 does not tell you about this beta, and this beta will not tell you
about the next one: watch the releases page.
Changes since 1.0.0-beta.1
- Setup. Step 2 lists the causes by impact, the highest first, and a cause PoolWatch could not check reads Not
known in grey instead of None; that includes a drive it could not read whole, which the row names. The first setup
can now be closed: its close button or Esc asks first, with No (keep it open) the default, and if you close it,
PoolWatch keeps running in the tray, what you set with Next stays, and setup opens again when you open PoolWatch and
at its next start. A sign-in task you turned off shows as off and stays off unless you switch it on. - Starting and installing. PoolWatch now starts through a launcher: the install folder's
PoolWatch.exeasks for
administrator rights and starts PoolWatch itself, nowapp\PoolWatch.exe, with an environment it builds from Windows'
own values. To pin PoolWatch to the taskbar, pin its Start menu entry: a window started at sign-in or from Explorer
offers no Pin to taskbar. The setup closes no other program. When another program still has one of PoolWatch's
files in use after the setup's wait, the update finishes the next time Windows restarts, and the setup says so and
names each file in use and the program that has it open. Neither the setup nor the uninstaller restarts Windows
itself; a silent setup then ends with exit code 3010. The setup and the uninstaller end a token-leak test helper left
running instead of waiting for it. Started by hand, the uninstaller waits only a few seconds for PoolWatch to close (a
silent one up to a minute), and what is still in use in the install folder then is deleted at the next restart,
unless the uninstaller says it could not arrange that. If PoolWatch's cleanup fails, the uninstaller removes no
file: it says why and what to do and, started by hand, offers Retry. The zips now hold the launcher and anapp
folder: unpack the whole zip intoC:\Program Files\PoolWatchand startPoolWatch.exe. The framework-dependent
zip needs the .NET 10 Desktop Runtime installed for all users, with Microsoft's installer. - Token-leak guard. It shows a notice only when it needs your click: when it turns Windows' setting on by itself, or
after your click, nothing is shown, and the log and the findings say what it did. Later in a sign-in it opens no
window: it turns the setting on again at its regular check when Windows lets it, and until then the tray icon's dot is
amber (a red one stays red), and its tooltip and menu say Token-leak guard: not protected right now. Click to turn
it on. Turning the guard off also puts back the Windows setting it changed when Windows allows it; if Windows does
not allow it just then, Active changes lists the setting with Put back to try again. If the guard's test at
sign-in is cut short, each later sign-in on that Windows build turns the workaround on without testing until a test
finishes; Run setup again tests now. - Services. If PoolWatch cannot read the list of services, the Services tab says so, and Turn off, Put back, Set to
Windows default and a profile applied at start change nothing until it can. Turn off names each service that depends
on the one you turn off and has not stopped, with what it is doing. The State column shows paused, starting and
stopping as they are, "state not known" when Windows could not say, and "could not read" for a service PoolWatch
cannot open. Put back starts a service again only if PoolWatch saw it running when it turned it off; a service beta.1
turned off without seeing it running gets its start type back, its row says "not known if it was running", and you can
start it from Services (services.msc) if you need it. The uninstall summary calls a service put back that way "Partly
put back". - Windows and settings. Advanced... in Settings describes the setting you select: what it does, its default and,
where it has them, its unit and limits. The sign-in box in Settings is ticked only while PoolWatch really starts when
you sign in; when its task is there but does not start PoolWatch, a line under it says why, and Active changes says
the same, with Remove. The Find boxes on the Services and Tasks tabs show their hint while they have the focus. In
a small window, Tab and the arrow keys reach the Pool causes details. Export report is always there for a Pool
causes row; Copy summary and Open report folder show when they have something to work on. About judges
PoolWatch's own overhead from 15 minutes after it starts, once it has 5 minutes of that. Hiding the main window frees
the graph's data and the Tasks rows. On a PC whose processor has a large cache, PoolWatch uses less memory: .NET no
longer sizes part of PoolWatch's memory by the processor's cache. - Data and reports. A day's folder, an incident or an export is deleted once nothing in it was written for 7 days
(by default), counted on the PC's own timer while it is on and awake, so a change of the PC's clock never deletes
anything early; while PoolWatch runs, growth, clears and alerts are timed on the PC's own timer too, so a change
of its clock then moves none of them. How sure PoolWatch is about a cause reads the same in the window, Copy
summary, the reports and the exports: weak evidence, some evidence, strong evidence or confirmed by a trace. In
report.md, names, command lines and paths are shown as plain text: web and e-mail addresses,@names, issue
numbers and commit hashes in them go in code spans. When PoolWatch has to keep its data in a folder of its own
(C:\ProgramData\PoolWatch.safe-...), it records that folder inHKLM\SOFTWARE\PoolWatchand moves the data back
once it can; the uninstaller leaves both, for you to delete if you will not install PoolWatch again. A pre-release
build's folder,%LOCALAPPDATA%\PoolWatch, is no longer moved: PoolWatch leaves it as it is, for you to delete. - For scripts.
TECHNICAL.md lists every
exit code of PoolWatch and its launcher in one table, and the setup's below it: for example--service-off
exits 13 when a service was not turned off,--selftest15 when a check failed, and a silent setup 3010 when
it finishes at the next restart.--stop-runningalso ends the token-leak test helpers still running. - Fixed from beta.1's known issues. All of them: Turn off names a dependent service that is paused, starting or
stopping, not only a running one; the Services tab shows a paused service as paused and one PoolWatch cannot open as
"could not read"; the check that a turned-off service stayed off no longer runs on the wall clock;--service-restore
run while the app is open no longer shows a "turned back on" warning; a steady token leak that starts after a quiet
spell is no longer reported up to an hour late; the keyboard reaches the Pool causes details; step 2 shows Not known
in grey, not None in green, when a check could not run; a token-leak check left running no longer holds an uninstall
or upgrade for a minute; the setup's wait now shows a moving progress bar; the links on the Get more from PoolWatch
cards line up, and setup's close box works.
What is in PoolWatch 1.0.0
The first public release. PoolWatch keeps a Windows 11 PC fast and stable through long days of agentic coding: it
watches the kernel pool, empties the standby cache before the pool slows you down, fixes known issues and, if you
want, trims background work. Every change it makes is listed, with a way to put it back.
- Setup that fits itself to your PC. At first start, Set up PoolWatch opens on its own, in seven short steps
(about 3 minutes), before the main window. It reads the PC and lists each known cause of a growing kernel pool with
how much it affects this PC, the highest first (high, medium, low, not known where it could not check, then none), and
which step fixes it. You choose when PoolWatch empties the standby cache (on a schedule, at a pool size, whichever
comes first, or decide later) and the fixes that fit: starting at sign-in (a sign-in task you turned off shows as
off, and stays off unless you switch it on), the token-leak guard if this Windows build has the leak, a Codex shortcut
without its shader cache when the Codex app is installed, and where to find Defender's performance mode for a Dev
Drive. The token-leak check says plainly what it found. On the steps that change things, Next pauses for a second,
so you can read what it will do. Setup changes no services. How PoolWatch works, from every step, explains the
kernel pool and why emptying the cache is safe. The first time, closing setup asks first, with No (keep it open) the
default; if you close it, PoolWatch keeps running in the tray, what you set with Next stays, and setup opens again
when you open PoolWatch and at its next start. Open setup again from the tray menu: Run setup again.... - Watches the kernel pool. The kernel pool is the memory Windows and its drivers keep for themselves. PoolWatch
sits in the tray, checks it every 10 seconds with...
PoolWatch v1.0.0-beta.1
A beta of PoolWatch 1.0.0, for testing: install it with the signed setup, PoolWatch-v1.0.0-beta.1-setup-win-x64.exe, and report a problem with Report an issue... in the tray menu (a security problem privately, as SECURITY.md says).
The first public release. PoolWatch keeps a Windows 11 PC fast and stable through long days of agentic coding: it
watches the kernel pool, empties the standby cache before the pool slows you down, fixes known issues and, if you
want, trims background work. Every change it makes is listed, with a way to put it back.
- Setup that fits itself to your PC. At first start, Set up PoolWatch opens on its own, in seven short steps
(about 3 minutes), before the main window. It reads the PC and shows, for each known cause of a growing kernel pool,
how much it affects this PC (none, low, medium or high) and which step fixes it. You choose when PoolWatch empties
the standby cache (on a schedule, at a pool size, whichever comes first, or decide later) and the fixes that fit:
starting at sign-in, the token-leak guard if this Windows build has the leak, a Codex shortcut without its shader
cache when the Codex app is installed, and where to find Defender's performance mode for a Dev Drive. The token-leak
check says plainly what it found. On the steps that change things, Next pauses for a second, so you can read what it
will do. Setup changes no services. How PoolWatch works, from every step, explains the kernel pool and why
emptying the cache is safe. Open setup again from the tray menu: Run setup again.... - Watches the kernel pool. The kernel pool is the memory Windows and its drivers keep for themselves. PoolWatch
sits in the tray, checks it every 10 seconds with little overhead, and when it grows works out which program,
service or driver is behind it, and says how sure it is. - A Simple view that shows, not tells. The kernel pool now, an arrow for which way it went in the last 10
minutes, when the next cache clear runs (with a ring that fills as it comes) and what the last one freed; four tiles
for the last 6 hours (growth per hour with the clears added back, what the clears freed, the net change, and the
memory in use); the graph, with a mark at every cache clear; and Get more from PoolWatch, up to three cards for
what PoolWatch found on this PC and for parts of the app you may not have found. It stays calm, and turns red only
for a real risk. - An Advanced view with the details. A graph of the last hour, 6 hours or 24 hours (the time before PoolWatch
started shows as a labelled band), with the growth and clears beside it, and Show RAM, on at first, for RAM in
use, the cache and free memory behind it. Pool causes lists what grew, what the clears freed of it, its impact,
the likely cause and how sure PoolWatch is, with what PoolWatch already does about it. Every list sorts by the column
you click. - Clears the cache automatically. On PCs with plenty of memory, Windows' file cache can hold file records in the
kernel pool and grow it by gigabytes, above all on ReFS drives such as a Dev Drive. PoolWatch can empty the standby
cache on a schedule, when the pool reaches a size, or whichever comes first, and shows what each clear freed. Your
files and programs are not touched. A clear takes a few seconds, and video or the mouse may stutter while it runs:
PoolWatch says so where you turn clearing on. - Tells its own cache clears apart. What PoolWatch's own cache clear frees is reported as the clear's result, not
as the pool or one kind of kernel memory (a pool tag) falling, everywhere it reports growth. Growth after a clear
counts from the level the clear left, growth before it still counts, and each alert keeps its own time span and
size. A pool tag's growth in the 2 minutes until a clear is measured counts as the clear's, so a leak just over an
alert's size that the clears keep trimming can go unreported: at the default 10-second sampling, up to about 4% over
the hourly growth alert with hourly clears, and about 8% with clears every 30 minutes (or in an hour where a light
clear is followed by a full one); more with a longer sampling interval. For the same reason a program's own release
in those 2 minutes is credited to the clear, and a release across a clear is raised only on what the tag fell after
the clear was measured. - Recognises known issues. A built-in list of known problems: the Windows 11 token leak, ReFS file records kept
by the file cache, NTFS file records piling up while some AI desktop apps run, and the Codex desktop app's GPU shader
cache. When what PoolWatch measures matches one, it says what it is, what helps and who found it. For the shader
cache, PoolWatch can make a desktop shortcut that starts the Codex app without it; it never changes the app itself.
Know another one? - Token-leak guard, and a watch for the leak. Some Windows 11 builds leak a little of the kernel pool every time
one program starts another, and coding assistants start thousands of programs an hour. PoolWatch tests your PC for
the leak and, only if it has it, offers the workaround, which it applies again each time PoolWatch starts. While it
is on, other programs can bring their windows to the front and take your keystrokes, even while you type. When the
leak was not found, PoolWatch keeps watching for it, checks again after a Windows update, and offers the guard if it
appears. Turn the guard off in Active changes; the setting itself lasts until you sign out. - Trims background work, if you want. The Services tab shows Windows' own services with the source PoolWatch
follows for each (Microsoft's virtual-desktop optimisation tool, the CIS security checklist for company PCs, or no
official source), and the services of other apps apart; what is not running and the protected services stay hidden
until you ask. Decide with your AI agent saves a prompt for Claude Code, Codex or any other agent, never with
your name, paths or files in it (as best it can: it shows you every word first), and Import answer shows every
change your agent suggests before anything is turned off. The new Tasks and startup apps tab ranks startup apps,
scheduled tasks and apps busy in the background by what each costs now, with a panel that says what each one runs and
when, and plain actions. Save the services you keep off as a named profile, next to the built-in Telemetry only
and Agentic coding PC; a profile can be applied each time PoolWatch starts, a few minutes later, so a service a
Windows update turned back on goes off again (more in the user guide). - Active changes: a way to put each change back. Every lasting change PoolWatch makes to your PC is in one window:
the features you turned on, each with Turn off, what PoolWatch turned off, each with Put back, any other change it
made (a service set to its Windows default, a task or startup app turned on), also with Put back, and Put all
back for the lot. The window says when one cannot fully come back. - Uninstalling puts your changes back. The uninstaller lists what PoolWatch changed and, by default, puts back
everything it can (you can keep your changes instead); it lists anything it cannot put back, with why. It says what
stays until you sign out and what it put back, and, once everything is put back, asks whether to delete PoolWatch's
reports, logs and settings. A silent uninstall and/DELETEDATAput back without asking. - Evidence you can share. When something keeps growing, PoolWatch writes a report with a timeline, the likely
causes and the evidence for each, ready for a bug report to the vendor. By default, Export report takes out your
user and machine names, your home folder and values that look like passwords or keys. It does its best, so read the
export before you share it. - Report an issue. From the tray menu: PoolWatch writes what it saw with your user and machine names taken out,
shows it to you, copies it, and opens GitHub's issue form in your browser. Nothing is public until you paste it and
submit. - Tells you when a new version is out. Once a day it checks GitHub for a new release. Information only: nothing is
downloaded or installed. It sends only PoolWatch's version, nothing about your PC (GitHub sees your IP address, as it
does for any web page). Turn it off on setup's last step or in Settings. - An installer. A signed setup program installs PoolWatch in Program Files with .NET included. It says what
PoolWatch does and what happens next: a welcome page; before anything is installed, the three steps (install, start
in the tray, set up in about 3 minutes) and "You stay in control"; and, once it is installed, where PoolWatch lives
and that its setup guide opens first. Setup, upgrade and uninstall first ask PoolWatch to close, then wait up to a
minute for any part of it still running before they change its files. Two zips are there too, if you would rather install by hand. - A guide for your AI assistant. An
AGENTS.mdin PoolWatch's data folder and in every export explains its files,
so an AI assistant can help you read them. - The binoculars everywhere. PoolWatch's icon on every window, the taskbar and the tray, where a coloured dot
shows the status.
Known issues in this beta (most are rare):
- When Windows refuses a stop because other services depend on it, the result names only the running ones.
- The Services tab can show a protected or Windows-default service as off while it is paused, and a service PoolWatch
cannot open reads as stopped. - The check that a turned-off service stayed off runs on the wal...