Proof Portal
Omarchy
ProbeLabs65 findings · 95 requirementsA proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.
Installer partitioning step lets users resize a live Windows NTFS partition with cfdisk, resulting in unbootable Windows
Reported by alkevintan · filed Aug 23, 2026 · open at source
At a glance
- 1 · What is claimed?
- Only the report text below — no validator has restated it as checkable claims yet.
- 2 · What does it affect?
- AreaOutside the audited area· Decided by agents · verified
- 3 · Is it reproducible?
- No validation has been run yet.
- 4 · What remains unclear?
- Not validated yet: no claims, no reproducer.
- 5 · What happens next?
- Decided by agents and verified by a second, independent agent — see the decision.
Original report
Bug description
During install alongside existing Windows 11 on the same drive, the guided partitioning step launches cfdisk. I selected the existing Windows C: partition and used [ Resize ] to shrink it from 237.5G to 202.5G, then wrote.
cfdisk only rewrites the GPT entry — the NTFS filesystem inside still reported its original size. On next boot into Windows:
STOP CODE: UNMOUNTABLE_BOOT_VOLUMEWindows validates that the boot sector's declared volume size matches the partition and refuses to mount otherwise.
Evidence
From /var/log/omarchy-install.log: cfdisk session showing /dev/sdb3 resized 498059264 → 424673280 sectors ("Partition 3 resized"), followed by table write. No ntfsresize was ever run.
Expected behavior
Either
- warn/block when resizing a partition containing an in-use NTFS filesystem, pointing users to shrink from Windows Disk Management first, or
- run ntfsresize after the cfdisk resize when the target filesystem is NTFS (ntfsprogs available), or
- document this prominently in the dual-boot install docs.
Notes
Recoverable after the fact (patch NTFS boot sector size field to match the partition + ntfsfix + chkdsk), but data extents beyond the new boundary are already lost — this trap can cause silent data loss for dual-booters.
Omarchy version: 4.0.0. Full install logs available on request.
View raw text
### Bug description
During install alongside existing Windows 11 on the same drive, the guided partitioning step launches `cfdisk`. I selected the existing Windows C: partition and used `[ Resize ]` to shrink it from 237.5G to 202.5G, then wrote.
`cfdisk` only rewrites the GPT entry — the NTFS filesystem inside still reported its original size. On next boot into Windows:
```
STOP CODE: UNMOUNTABLE_BOOT_VOLUME
```
Windows validates that the boot sector's declared volume size matches the partition and refuses to mount otherwise.
### Evidence
From `/var/log/omarchy-install.log`: cfdisk session showing `/dev/sdb3` resized 498059264 → 424673280 sectors ("Partition 3 resized"), followed by table write. No `ntfsresize` was ever run.
### Expected behavior
Either
- warn/block when resizing a partition containing an in-use NTFS filesystem, pointing users to shrink from Windows Disk Management first, or
- run `ntfsresize` after the cfdisk resize when the target filesystem is NTFS (ntfsprogs available), or
- document this prominently in the dual-boot install docs.
### Notes
Recoverable after the fact (patch NTFS boot sector size field to match the partition + ntfsfix + chkdsk), but data extents beyond the new boundary are already lost — this trap can cause silent data loss for dual-booters.
Omarchy version: 4.0.0. Full install logs available on request.Validation
Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.
Linked
Not linked to any known issue, other report or change yet.
Decision
Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.
- Out of scopeDecided by agents · verified · 2026-10-09 08:30 UTC