Repository navigation
WParted v0.3.0-alpha
Pre-release
Pre-release
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