Repository navigation
Releases
WParted v0.4.0-alpha
WParted v0.4.0-alpha
Pre-release. Read the compatibility matrix before use.
Fourth pre-release and the first one built and published on GitHub: the privileged-helper channel of
ADR-0002 as a prototype, and the first verification on real hardware with administrator rights
(read-only). Physical disks are still never written.
Added
- Privileged-helper prototype (ADR-0002):
wparted-helper.exetalks to WParted over a named pipe
(one instance, no remote clients, DACL for the user, SYSTEM and Administrators), accepts only the
process that started it when that iswparted.exe/wparted-cli.exenext to it, validates the
plan itself and executes only after a confirmation carrying the SHA-256 of the plan it validated.
wparted-cli apply-plan --execute --helper. Image files only; it is not elevated yet. wparted-cli rescue-scan <disk>: read-only rescue scan of a physical disk (administrator).tools/verify/elevated-readonly.ps1: manual read-only verification on real hardware.
Verified
- Real hardware, administrator, read-only (Windows 11 Pro x64; NVMe SSD with GPT, USB SSD with
msdos/exFAT): partition tables read without diagnostics, every partition offset equal to Windows'
view, boot manager / Windows / page file marked, BitLocker "not encrypted" matching
manage-bde -status, rescue scan on both disks, Windows' view unchanged afterwards.
Changed
- WParted is developed on GitHub (https://github.com/jtracht/WParted): code, pull requests, CI
(GitHub Actions, same jobs as before) and releases. Project management - issues, milestones and
the board - stays on Gitea injtracht/WParted-PM; the Gitea repositoryjtracht/WPartedbecomes
a read-only pull mirror, as for every public repository in the TDS-Ops sync.
Removed
- The project website (sources and generator) moved out of this repository; it will be maintained
separately.
Known limitations
- The helper is a prototype: it executes on disk image files only, is not elevated and is started
without UAC. Physical-disk execution still needs the human security review of ADR-0002. - Only the BitLocker state "not encrypted" has been observed on real hardware. High-contrast mode,
Windows 7–10, ARM64 binaries and Windows' chkdsk on NTFS created by WParted are not verified. - The release binaries were not run on a real Windows machine before publication (maintainer decision
for alpha releases); equivalent MSVC builds were tested on Windows 11 x64, including the helper path. - See 0.3.0-alpha for the file-system limitations, which are unchanged.
Verification
- SHA-256 checksums:
WParted-v0.4.0-alpha-checksums.sha256 - SBOM (CycloneDX):
WParted-v0.4.0-alpha-sbom.json - Code signing: not signed (no certificate configured)
Supported platforms: see docs/compatibility/windows-support-matrix.md
WParted v0.3.0-alpha
Originally published on 2026-10-28 (Gitea). Same files and checksums as the original release.
WParted v0.3.0-alpha
Pre-release. Read the compatibility matrix before use.
Third pre-release: file systems, data rescue and resumable executions on disk image files.
Physical disks are still never written.
Added
- Interrupted executions can be resumed. A journal next to the image records the plan and the
progress; after a crash, power loss or cancel during a block move or between operations, WParted
continues exactly there (GUI: Resume when the image is opened; CLI:wparted-cli resume).
Steps that change data in place are reported, not resumed. Tested in CI by killing the process in
the middle of an overlapping move and resuming (e2fsck, sgdisk and payload hashes). - ext2/ext3/ext4 on image files: create, grow, shrink (when the space behind the new end is free)
and a read-only check, implemented natively. Grow and shrink also handle file systems made by
mke2fs with its default features (flex_bg, 64bit, metadata_csum, resize_inode). Verified in CI with
e2fsck, dumpe2fs, blkid and debugfs. - Extended partitions can be moved (their boundaries; the EBR chain is rewritten).
- BitLocker state as reported by Windows (administrators only), the boot-manager volume and the page
file are shown; new validation rulesop.bitlocker_active,op.bitlocker_unknown,
op.bitlocker_recoveryandop.bcd_offset(moving the start of the Windows or boot-manager
partition on msdos disks breaks booting). - NTFS create (NTFS 3.1, simplified system files) and a read-only NTFS check (records,
$MFTMirr, every referenced cluster marked in$Bitmap, no cluster used twice). Verified in CI:
ntfsfix, ntfsls andntfsresize --checkaccept volumes WParted creates, ntfs-3g writes files into
them, and they stay consistent after growing and shrinking; the WParted check is clean on mkntfs
volumes. - exFAT grow and shrink (the FAT may use the space in front of the cluster heap; shrinking needs a
free tail). exFAT volumes WParted creates align FAT and cluster heap to 1 MiB from 32 MiB on, which
leaves room to grow. Verified with fsck.exfat on WParted- and mkfs.exfat-made volumes. - Lost partitions can be recreated from the rescue scan: Add to the plan in the GUI,
wparted-cli rescue-scan-image --plan. The partition is recreated exactly around the file system,
nothing inside it is written, and the file system is detected and checked afterwards. CI: ext4,
NTFS and FAT32 whose table entries were deleted with sgdisk are recreated at their sectors and pass
e2fsck,ntfsresize --checkand fsck.fat with intact payloads. - CI builds Windows on ARM64 binaries with llvm-mingw (not run: no ARM64 Windows in CI).
Changed
- Image files are flushed to disk (
_commit/fsync), not only to the C library buffer.
Known limitations
- ext: no data relocation when shrinking; growing beyond the existing group descriptor blocks, and
meta_bg, bigalloc, sparse_super2, MMP and external journals are refused. File systems created by
WParted have no metadata checksums. - NTFS created by WParted has not been checked by Windows' chkdsk; it uses version-1.2 standard
information without security ids, an empty$Secureand$Extend, and an up-case table built from
the Unicode simple mappings of the common scripts – Windows may complete these on first use. - exFAT cannot grow beyond the space in front of the cluster heap; no exFAT check yet. No data is
relocated when shrinking NTFS, exFAT or ext. - The BitLocker state is only available to administrators; it has not been checked on a machine with
BitLocker. ARM64 binaries have not been run. Windows 7–10 and administrator mode are not verified. - The release binaries were not run on a real Windows machine before publication (maintainer
decision for alpha releases); equivalent MSVC builds were tested on Windows 11 x64 (unelevated):
creating and growing NTFS, ext4 and exFAT on image files withwparted-cli, a full rescue cycle,
the resume dialog and the rescue dialog in the GUI. - Only disk image files can be changed; physical disks are planned and validated only.
Verification
- SHA-256 checksums:
WParted-v0.3.0-alpha-checksums.sha256 - SBOM (CycloneDX):
WParted-v0.3.0-alpha-sbom.json - Code signing: not signed (no certificate configured)
Supported platforms: see docs/compatibility/windows-support-matrix.md
WParted v0.2.0-alpha
Originally published on 2026-10-28 (Gitea). Same files and checksums as the original release.
WParted v0.2.0-alpha
Pre-release. Read the compatibility matrix before use.
Second pre-release: GParted-style planning for every disk, and execution on disk image files.
Physical disks are still never written.
Added
- GParted-style planning GUI: new, delete, resize/move, copy/paste, format, label, name, flags, new
partition table; future-layout preview, pending operations, undo, Apply summary with safety checks,
plan export/import with disk identity checks. Fluent-inspired redesign with one workflow from
selection to apply; English and German throughout. - Data rescue scan (read-only): searches unallocated space at MiB steps and legacy cylinder boundaries
for lost file systems and reports start sector, type, size and label.wparted-cli rescue-scan-image
and GUI Device → Attempt Data Rescue… (background thread). Recovery itself is not automated; the
device scan has so far only been run on image files, not on real disks. - Operation log model (plan → steps with status) with JSON and escaped HTML export; Save details
(HTML)… in the Apply summary. - Validation refuses plans on disks managed by Windows (dynamic disks, Storage Spaces, spanned volumes).
- Validation diagnostics carry the operation number and their parameters; the GUI shows operations,
risks and validation messages in the UI language (English/German). - High-contrast mode: the GUI uses the system colours.
- Project website (EN/DE) generated from the repository, checked in CI; not deployed yet.
- Plans can be applied to disk image files (GUI: Apply to image file; CLI:
apply-plan, dry run
by default): partition tables, create/delete, move and copy as raw blocks, resize of unformatted
partitions, flags, names. Every step is read back and compared with the plan. Results are checked in
CI with sgdisk, sfdisk, e2fsck and debugfs. Physical disks are still never written. - File-system operations on image files, implemented natively from the on-disk specifications:
FAT16/32 create, grow, shrink (with data relocation), read-only check, label and serial; NTFS grow,
shrink (when the space behind the new end is free), label and serial; exFAT create, label and serial;
ext2/3/4, XFS, btrfs and Linux swap label and UUID (metadata checksums stay valid via csum_seed,
meta_uuid and metadata_uuid); copies of Linux file systems get a new UUID. Every operation is checked
in CI with dosfstools, mtools, ntfs-3g (ntfsresize --check), exfatprogs, e2fsprogs, xfsprogs,
btrfs-progs and util-linux. - Used space of FAT and NTFS partitions on images (list columns; validation refuses shrinking below the
data). Validation checks labels per file system and maximum FAT sizes. - Accessibility: the disk map exposes its segments through MSAA.
wparted-cli fs-supportand View → File System Support list what can be changed on image files.- Disks managed by Windows (dynamic disks, Storage Spaces) are marked and never planned on.
- Labels of NTFS, exFAT and F2FS (and the F2FS UUID) are read; detection is checked in CI against
images made by the real mkfs tools, with blkid as reference.
Security
- Physical disks are never written: the read-only guard in CI rejects any device write API and any file
opened for writing outside 7 reviewed exemptions (report/plan/log files chosen by the user and the
image-file executor, which refuses device paths and opens images exclusively).
Known limitations
- Only disk image files can be changed. On physical disks WParted plans and validates, but does not
execute (the privileged helper of ADR-0002 and a human security review come first). - The binaries attached to the release were not run on a real Windows machine before publication
(maintainer decision for alpha releases). They passed all tests and a GUI start-up smoke test under
Wine in the release pipeline; an equivalent MSVC build was tested on Windows 11 x64 (unelevated),
including planning and applying plans to image files in the GUI. - Administrator mode is not verified on real hardware; Windows 7 to 10 and ARM64 are not verified;
the binaries are unsigned. - Not yet possible: creating or checking NTFS; resizing ext2/3/4, XFS or btrfs; moving an extended
partition; repairing file systems (the FAT check is read-only). Such plans are refused before
anything is written. There is no automatic rollback if writing to an image fails half-way. - High-contrast mode maps to the system colours but has not been checked visually.
Verification
- SHA-256 checksums:
WParted-v0.2.0-alpha-checksums.sha256 - SBOM (CycloneDX):
WParted-v0.2.0-alpha-sbom.json - Code signing: not signed (no certificate configured)
Supported platforms: see docs/compatibility/windows-support-matrix.md