Zney scans installed software, Windows personalization, and app configs into a single tamper-evident .zney container β then restores everything with SHA-256 integrity checks and 1-click Winget automation.
Upgrading your SSD, reinstalling Windows, or switching laptops shouldn't take an entire weekend.
A stream-lined, memory-efficient workflow built for speed and security.
Instantly scans Start Menu shortcuts, Registry uninstaller keys, Winget packages, and key %APPDATA% application configs with non-blocking async IO.
Calculates SHA-256 hashes per file, filters out sensitive credential databases, and compresses into an offline .zney container using 80KB stream buffers.
Unpacks into an isolated staging directory, verifies SHA-256 checksums before touching target paths, and triggers unattended Winget package installations.
Integrity Verification
Password / Key Leak Risk
Memory Stream Buffer
Offline Container
Every line of code is designed to protect your data and system integrity.
Hardened relative path filtering ensures Chrome/Edge Login Data, DPAPI Local State, SSH private keys, and session cookies are never exported.
Every data folder and individual file is sealed with an individual SHA-256 digest in manifest.json before write operations.
Strict whitelisting ensures files only unpack within authorized %APPDATA%, %LOCALAPPDATA%, or %USERPROFILE% folders.
Streams files with constant O(1) RAM consumption and a strict 25GB safety cap to prevent zip-bomb attacks.
Runs seamlessly under standard user privileges without demanding dangerous UAC Administrator elevation.
Equipped with live search filtering, bulk selection controls, real-time disk size estimation, and expandable log terminal.
Everything you need to know about Zney security and workflows.
No. The .zney file is an unencrypted sealed ZIP container designed for tamper-evidence and transparency. It contains preferences and settings, but explicitly excludes passwords and authentication tokens. If you store your backup on USB flash drives or cloud storage, we recommend encrypting the .zney file with BitLocker or 7-Zip (AES-256).
No. By design, Zney filters out browser credentials (Login Data, Web Data), DPAPI encryption keys (Local State), session cookies, and private key files (*.key, *.pem, id_rsa, .env). You will need to log into your accounts again after restoring.
Zney scans installed programs and matches their package IDs (e.g. Git.Git, Microsoft.VisualStudioCode). On your new Windows machine, Zney instructs Winget to download and install official packages silently without manual browser searching.
Zney uses a 'Staged Move' architecture: all archive contents are extracted into a temporary staging folder and their SHA-256 checksums are verified. If any file fails verification, the entire group restore is rolled back to protect your existing files.
