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