v1.4.1 — quiet start from a network share

A quiet start when the tool sits on a network share.

Download pitr-config.cmd below — that single file is still the whole tool. No installation,
no dependencies. Double-click it; it requests administrator rights itself.

Started from a network share, cmd.exe printed a warning of its own before the tool ran:

"\\server\share\path"
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.

It looks like a failure and is none. The loader works from %~f0, its own full path, and
never needs the current directory — the tool runs correctly from a share either way. But the
message is the first thing a user sees, and @echo off cannot suppress it: cmd.exe writes
it itself, to stderr, before the first line of the file is read.

The loader now recognises a start from a UNC path and clears the console, leaving a short line
in its place. The selftest is deliberately left alone — it writes into a console whose
contents nobody wants cleared.

Also in this release: the guide notes that the file runs just as well from a USB stick or a
network share, and one sentence in the Spanish guide still addressed the reader
(hasta que pulse un botón), missed when the address forms were removed in 1.3.1.

Guide: https://henmedia.github.io/windows-pitr-config/guide.html
· Full list of changes: CHANGELOG.md

SHA-256

c5eefcc5b23e2041ff871ca983ca3ad9714d6561a9fd61affc9ca3e3dc05ff3f  pitr-config.cmd
27678373ae4e4269b3a0ff88127f389c344ed927bcf6d5ada7d62a1fbcd29eb4  guide.html

Worth comparing before running something that writes to HKLM:

Get-FileHash pitr-config.cmd -Algorithm SHA256

v1.4.0 — Create snapshot now

A restore point on demand, one click from the top of the window.

Download pitr-config.cmd below — that single file is still the whole tool. No installation,
no dependencies. Double-click it; it requests administrator rights itself.

Create snapshot now. The tool could already force a restore point, but only through
Apply and run now at the bottom of the window, which saves the settings along with it.
Creating a snapshot on demand is the more common reason to open the tool at all, so it now has
its own highlighted button at the top — and one that writes nothing but the point itself. No
setting is changed, no value written. One click before a driver installation, a registry edit,
or the first run of unfamiliar software.

This works even while the machine is in use, which a manual start of the scheduled task does
not: PITRTask runs with RunOnlyIfIdle = True and simply stays Queued. The button lifts
that condition for exactly one run and restores it afterwards, including when an error occurs
in between.

Apply and run now is unchanged and still has its place — it is the right button when a newly
chosen frequency should take effect at once rather than at the next scheduled run.

The guide covers the new button in all five languages, with its own section and a row in the
button table. Also fixed: the German interface used a mixed pair of quotation marks in the
unofficial-approach notice.

Guide: https://henmedia.github.io/windows-pitr-config/guide.html
· Full list of changes: CHANGELOG.md

SHA-256

ca7ea128466de79b198f0cf74caca10da5b13e793ef65db78cdf6a784ccfb7ce  pitr-config.cmd
c67390d5a6d26f57d27b2e442041de14a358d6ce830de902092ec296c4b2d59f  guide.html

Worth comparing before running something that writes to HKLM:

Get-FileHash pitr-config.cmd -Algorithm SHA256

pitr-config 1.3.1

A date formatting fix, and wording that no longer addresses the reader.

Download pitr-config.cmd below — that single file is still the whole tool. No installation,
no dependencies. Double-click it; it requests administrator rights itself.

Last run and next run were shown in US notation on every system, 08/27/2026 instead of
27.08.2026 on a German machine. PowerShell formats a date inside a double-quoted string
with the invariant culture rather than the user's, so "$date" silently produced US order
while the restore point list, which formats explicitly, was correct. Every timestamp now goes
through one helper that uses the short date and time format of the region — the same
everywhere in the window.

Guide and interface no longer address the reader. German had to pick between "du" and
"Sie", and Spanish, French and Portuguese between their familiar and polite forms. That
choice is now avoided altogether by phrasing everything impersonally. In the Romance
languages the imperative carries the same distinction — haga/haz, cliquez/clique,
dê/dá — so those instructions were rewritten as noun phrases, which is the usual register
for technical documentation in those languages anyway. English follows the same style for
consistency.

Guide: https://henmedia.github.io/windows-pitr-config/guide.html
· Full list of changes: CHANGELOG.md

SHA-256

975590d2f699d4cfe27eabbc00204e6f289ed7cac622db1b925f423a10f237ec  pitr-config.cmd
19c733ba71ba2f3604d191062edb48092d0e51c076c9d72358cb55f9e54148d7  guide.html

Worth comparing before running something that writes to HKLM:

Get-FileHash pitr-config.cmd -Algorithm SHA256

pitr-config 1.3.0

A more compact window that fits your screen, and a corrected scheduled interval.

Download pitr-config.cmd below — that single file is still the whole tool. No installation,
no dependencies. Double-click it; it requests administrator rights itself.

The scheduled interval was wrong when a run had been skipped. It was computed as next
run minus last run, which only equals the configured interval if no run is ever missed. But
the task runs only while the system is idle, so skipped runs are the normal case — an hourly
schedule then displayed as two hours, with a note wrongly claiming the value came from an
earlier setting. The interval is now read from the repetition of the task's time trigger,
where it actually lives.

Skipped runs are shown next to the task status now. They are what explains a gap between two
restore points that is longer than the configured interval:

Scheduled interval:  60 minutes = 1 hour
Task status:         ready  ·  runs skipped: 1

The window adapts to the screen. It opens at 800 pixels at most and never taller than the
work area minus a margin. The work area excludes the taskbar, so the window can no longer end
up behind it. On a tall screen it grows past 800 when that lets everything fit without
scrolling, and re-centres itself afterwards.

Less wasted space. The introduction and the "unofficial approach" notice now run the full
width instead of sitting in a column beside the language buttons, where they wrapped early
and left the area under the buttons empty. Paddings, margins, the restore point list and the
log box were tightened throughout, and the restore point count shares a line with the oldest
point. The same content needs about 200 pixels less height than in 1.2.1.

The README now shows what all this looks like.

Full list of changes: CHANGELOG.md
· Guide: https://henmedia.github.io/windows-pitr-config/guide.html

SHA-256

a1d859ed82b98db9d455384054bce99772bf84392741a4990575ad896f8d1d36  pitr-config.cmd
8574d8de6fc69f1ff904095fe253dcf519b79b6bdfa9982b61d8b038d1fe917a  guide.html

Worth comparing before running something that writes to HKLM:

Get-FileHash pitr-config.cmd -Algorithm SHA256

pitr-config 1.2.1

Two display fixes, both found while taking the screenshot that now heads the README.

The Windows edition was wrong. On Windows 11 the tool showed Windows 10 Pro. It read
ProductName from the registry, and Microsoft never updated that value for Windows 11 — it
still says "Windows 10" there, for application compatibility. The build number is used as
the discriminator instead (22000 and above is Windows 11), and the line now also carries the
feature update and the full build:

Windows 11 Pro (EditionID: Professional)  —  25H2, Build 26200.9168

Restore point timestamps were formatted German-style. dd.MM.yyyy was hard-coded, in all
five languages. They now follow the date format of your region, like every other date in the
window.

Nothing else changed — same settings, same registry values, same update check introduced in
1.2.0. If 1.2.0 works for you, this is cosmetic; if you run Windows 11 in any language other
than German, it is worth taking.

Full list of changes: CHANGELOG.md
· Guide: https://henmedia.github.io/windows-pitr-config/guide.html

SHA-256

b61a52fa2425cafa3f7836c7971eb9abb5475ecf97cf6d52e7ea7b752fa5f804  pitr-config.cmd
8574d8de6fc69f1ff904095fe253dcf519b79b6bdfa9982b61d8b038d1fe917a  guide.html

Worth comparing before running something that writes to HKLM:

Get-FileHash pitr-config.cmd -Algorithm SHA256

pitr-config 1.2.0

The tool now tells you when a newer version is out.

Download pitr-config.cmd below — that single file is still the whole tool. No installation,
no dependencies. Double-click it; it requests administrator rights itself.

Update check. On start the tool asks GitHub whether a newer release exists. If one does,
the window shows a line with a link to it, in whichever of the five languages you are using.
The check runs in the background, so the window stays responsive, and it fails silently — no
network, a firewall, or a rate limit simply means no notice appears.

Nothing is downloaded or installed automatically, by design. A tool that writes to HKLM
has no business replacing its own code over the network, and doing so would make the
checksums below pointless. The notice is a link; the decision stays with you.

This is also the only network connection the tool makes. The request reveals nothing about
your system beyond what any web request does — an IP address and a pitr-config user agent.
To skip the check entirely, start it as:

pitr-config.cmd noupdate

That argument is passed on across the UAC prompt, which starts a new process that would
otherwise lose it.

Unchanged: the settings themselves, the five languages (EN DE FR ES PT), and the three
things worth knowing — restore points are only created while the system is idle, only the
Windows drive is covered, and the configuration values are undocumented by Microsoft.

Full list of changes: CHANGELOG.md
· Guide: https://henmedia.github.io/windows-pitr-config/guide.html

SHA-256

1b58bf593440a9858ab1fb3e7533ca9d58e4842e3ee78465a251539c7b67552f  pitr-config.cmd
8574d8de6fc69f1ff904095fe253dcf519b79b6bdfa9982b61d8b038d1fe917a  guide.html

Worth comparing before running something that writes to HKLM:

Get-FileHash pitr-config.cmd -Algorithm SHA256

pitr-config 1.1.0

Five languages, links out of the window, and a short guide.

Download pitr-config.cmd below — that single file is still the whole tool. No installation,
no dependencies. Double-click it; it requests administrator rights itself.

Now in five languages. The interface speaks English, German, French, Spanish and
Portuguese. It starts in whichever one matches your Windows display language, and the
buttons in the top right (EN DE FR ES PT) switch at any time without losing what you have
selected.

A short guide. The window header now links to the project page and to a guide that
covers the same ground in all five languages, opening in the one you are currently using:
https://henmedia.github.io/windows-pitr-config/guide.html

guide.html is attached to this release as well. Put it next to pitr-config.cmd and the
tool opens that local copy instead of the online one — so a USB stick with both files stays
fully usable without a network.

Nothing changed about what the tool does. Same settings, same registry values, same
three things worth knowing: restore points are only created while the system is idle, only
the Windows drive is covered, and the configuration values are undocumented by Microsoft.

Full list of changes: CHANGELOG.md

SHA-256

d8d9e0df04752feee83d0e9fa4c65e05a9212c9acf40e364752e9733e6bcce2f  pitr-config.cmd
f665a62917f4422a6c495378b089f5a5d4e1210b84bbf9bc41a467429540383a  guide.html

Worth comparing before running something that writes to HKLM:

Get-FileHash pitr-config.cmd -Algorithm SHA256

pitr-config 1.0.0

First public release.

Download pitr-config.cmd below — that single file is the whole tool. No installation, no
dependencies, no PowerShell modules. Double-click it; it requests administrator rights itself.

What it does. Windows exposes restore point frequency and retention on the Enterprise
edition only. The edition gate sits in the Settings user interface, not in the engine, so
this tool writes the engine's configuration directly and makes both settings available on
Home and Pro as well.

Interface. English and German, detected from the Windows display language, switchable at
any time. Shows the current state, the existing restore points, the scheduled task's status
and the shadow storage figures.

Three things worth knowing.

• Frequency is an earliest possible interval, not a guarantee — restore points are only
  created while the system is idle. The tool shows when a run is waiting for that, and
  Apply and run now forces a point immediately.
• Only the OS volume is covered. Other partitions and disks are neither captured nor rolled
  back, not even on the same physical disk.
• The registry values this tool writes are undocumented by Microsoft. A future Windows
  release may change them, at which point the default behaviour simply applies again.
  Reset everything undoes all of it.

See the README for how it works and
what was verified how.

SHA-256 of pitr-config.cmd

32eaf80704c2a5ede1714ee174ca3d9799a2a47f0f2f492f338cda5791c2b57b

Worth comparing before running something that writes to HKLM:

Get-FileHash pitr-config.cmd -Algorithm SHA256