Own Backup 0.1.9-beta

Prerelease for Windows 10/11 x64 and Linux (Ubuntu 24.04+, Debian 13+, amd64).

• own-backup-install_0.1.9-beta.exe — Windows setup wizard in English and Russian: installs the program for all users and starts its backup service; needs administrator rights. It installs over an earlier version, keeping settings and jobs.
• own-backup_0.1.9.beta_amd64.deb — Linux package: sudo apt install ./own-backup_0.1.9.beta_amd64.deb installs the program, starts its service and adds you to the own-backup group (sign in again to open the window).
• OwnBackup-Linux-0.1.9.beta_amd64.iso — Linux boot medium (Debian 13 live): boots from a CD or a USB stick, UEFI with Secure Boot or BIOS, to back up or restore the computer's disks, Windows ones included.

Added

• Windows: disk cleanup. A new section, Cleanup, before Settings: temporary files, Windows error reports, crash dumps, setup logs, the WinINet and shader caches, thumbnails, Prefetch and the Recycle Bin, for the system and the chosen users. Analyse shows how much each item takes, Clean up removes it — plainly and fast, not into the Recycle Bin. Files lists what an item will remove (search, largest first), and the cleanup removes exactly that list. Only the folders of the items are touched, never a mask over a whole disk; files younger than a day in the temporary folders, files in use, links and junctions stay. The result goes into Activity.
• Cleanup: browsers. The caches and crash reports of Chrome, Edge, Vivaldi, Brave, Yandex, Opera, Firefox and Thunderbird in every profile; history, cookies and sessions — open tabs (off by default; cookies and sessions are separate items, sign-ins live in the cookies). A browser that is open is left and the item says to close it; passwords, bookmarks and autofill are never touched, nor Firefox's history, which shares a database with the bookmarks. Browser history can keep its last day, week or month: only older visits are removed from the history database, edited on a copy, checked and then put in place.
• Cleanup: programs. Microsoft Office recent documents (the places pinned to the lists stay), the recent files of Paint, WordPad, Windows Media Player, MPC-HC, 7-Zip, WinRAR, Adobe Acrobat Reader; the caches of XnView MP, Discord, Visual Studio Code, Steam, Telegram Desktop, npm, pip, Yarn and NuGet; the logs of qBittorrent, Zed, DaVinci Resolve, OBS Studio; NVIDIA driver installers. The programs' settings and data are not touched; a program that is open is left.
• Cleanup: Windows Update cache — downloaded update files (SoftwareDistribution\Download) older than a day; the update history stays.
• Disk cleanup on Linux. The Cleanup section and the automatic cleanup on Linux too: the apt cache, old logs, the systemd journal (to 200 MB), crash reports, old snap revisions, unused Flatpak runtimes, apt autoremove (off); the trash, thumbnails, shaders, browsers (snap and flatpak Firefox too), programs' caches (VS Code, Discord, Slack, Obsidian, Signal, TradingView, Termius, Steam), the Telegram cache (off), developer caches, editors' junk (Zed's npm cache too). A user's folders are cleaned with that user's own rights; the system's part by an administrator only (root, the sudo group). The mask search no longer enters hidden folders (.cargo, .npm…) — on Windows either; the *.err mask is off by default.
• Automatic cleanup and cleanup before a copy. The service cleans by itself, with no window: on a schedule (a day, weekdays, a day of the month, a missed one after start-up) and before the copy of jobs that tick "Clean the disk before the copy". The set is what is ticked on the Cleanup page (files by masks excluded); the result goes into Activity.
• Cleanup profiles. What is ticked on the Cleanup page can be saved under a name, opened again and deleted; a job's Cleanup tab chooses the profile to clean the disk by before its copy.
• Cleanup: Windows components by Windows' own means — through Disk Cleanup's handlers: update cleanup (WinSxS), the previous Windows installation (Windows.old), Delivery Optimization files, setup temporary files and logs, Defender's files, old driver packages, ESD installation files. Only a computer's administrator removes them (the window need not be run "as administrator" — the service does the work).
• Cleanup: files by masks (off by default) — a list of masks as in Ace Utilities (temporary files and junk on; backups, logs, *.chk off), own masks, but carefully: only in the users' profiles and in folders an administrator added; Windows, Program Files, ProgramData, AppData, .git, node_modules, cloud folders and the program's own files are never touched; masks too broad (*.*) are refused; files older than a week (the age is chosen). Removed only after the Files list was looked through, where any file can be unticked — which works for the other items too.
• Cleanup: Windows traces (off by default): recent documents (shortcuts and the registry's lists, the Open and Save As dialogs' too), jump lists (the folders pinned to Quick access stay), the Run box's, Explorer's address bar's and search history, Remote Desktop connections (saved passwords stay). A user who is not signed in has their registry loaded by the service for itself alone and only for the cleanup; the Files list shows what each registry entry holds.

Fixed

• Linux: mounting a whole-disk copy. The service mounted a whole-disk copy as one volume and got an ntfs-3g error; each partition is mounted on its own now, the folder is visible to the user (/run/own-backup-mounts) and the window shows it with an "Open folder" button.

Changed

• The ready-made boot medium from GitHub comes from the latest release that has one, not only from the installed version's release.
• "Add backup" is a green button, like "Back up now".
• The chain number in backup file names. A new full starts the next number and its versions carry it: Disk_C_Win11_disk4_3-full_….obk, Disk_C_Win11_disk4_3-inc_….obk, so it is plain which full an increment belongs to, and sorted by name a folder lists each chain together. Backups made before keep their names (a version finds its parent by that name), and versions added to such a chain stay unnumbered; the next full is numbered past the chains already in the folder.

Windows: settings and jobs are kept in C:\ProgramData\OwnBackup, the service log in the Logs folder next to the program. The window needs the Microsoft Edge WebView2 Runtime: Windows 11 has it, and the installer says so if a Windows 10 does not. Linux: settings and jobs in /var/lib/own-backup, the log in journald (journalctl -u own-backup).

License: PolyForm Noncommercial 1.0.0; third-party components keep their own licenses. The checksums of the files are in SHA256SUMS.txt.