Tired of exporting registry branches by hand before every Windows update or policy change?

This PowerShell script exports the key registry branches to a dated folder, writes a CSV report of what was saved, and shows how to roll back.

WHAT IT SOLVES

Manual export means opening regedit, finding the branch, right-click, export, inventing a filename, and hoping you typed the path correctly. Two minutes per branch and a real chance of a typo in the path.

The script does it in one command, names the folder with the date, and writes a report showing exactly which files were produced and how large they are.

WHAT IS INSIDE

- bekap-reestria.ps1, the script itself, PowerShell 5.1 and newer

- INSTRUKCIYA.md, launch, requirements, rollback and a table of common errors

- LIZENZIYA.txt, terms of use

- primer-vyvoda.txt, real output from an actual test run

REQUIREMENTS

Windows 10 or 11, PowerShell 5.1 which is bundled with Windows. No administrator rights required, the script only reads data and writes copies.

HOW TO RUN

powershell -ExecutionPolicy Bypass -File .\bekap-reestria.ps1

Then roll back by double-clicking any .reg file and confirming the import.

BUGS FOUND AND FIXED DURING DEVELOPMENT

1. reg.exe rejects a registry path containing a colon. The PowerShell provider requires a colon after HKLM while reg.exe rejects it and fails with invalid key name. Paths are stored in reg.exe syntax from the start.

2. A .ps1 file without a BOM is read as ANSI by PowerShell 5.1, which breaks Cyrillic comments and crashes the parser. Saved as UTF-8 with BOM.

Both were verified by re-running the script and comparing the output before and after the fix.