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.
Dual boot (on 1 SSD)
Reported by peregrinus879 · filed Aug 18, 2025Closed upstream on 2025-08-18 by its own reporter peregrinus879. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.
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?
- Not yet mapped to any requirement or component.
- 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?
- Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.
Original report
As archinstall does not currently support "pre-mount" partitioning option with LUKS encryption, this is what I did to dual boot ArchLinux & Win11 on a single SSD.
General:
-- BIOS: Secure Boot on
-- (Optional) archinstall: Unified Kernel Image enabled
-- Prepare GParted, ArchLinux & Win11 live usb's
Assumption:
Manual or automatic partitioning during archinstall created 2 partitions:
-- nvme0n1p1 as boot; &
-- nvme0n1p2 as encrypted root with all the btrfs subvolumes.
Steps:
01 Boot into GParted live usb
02 Select default options
03 Select /dev/nvme0n1
04 Unlock encryption on /dev/nvme0n1p2
05 Shrink /dev/nvme0n1p2 to create unallocated space at the end (according to your Win11 space preference)
06 Lock /dev/nvme0n1p2
07 Apply changes
08 Reboot into ArchLinux live usb
09 Run "gdisk /dev/nvme0n1"
10 Create 2 partitions:
-- p3 and assign last sector as "+128M" & type as "0C01"; &
-- p4 and assign type as "0700"
11 (Optional) Run "cfdisk /dev/nvme0n1" to check partition types were done correctly
12 Run "mkfs.ntfs /dev/nvme0n1p4" (this will take time)
13 Reboot into Win11 live usb
14 Select nvme0n1p4 partition and install Win11
15 Boot into BIOS and change first boot option from Windows to Linux.
16 Systemd or Grub bootloader will automatically detect Win11 and you will have the option to choose either on boot.
I'm not a tech person, if anyone has a simpler approach, please let me know. Also let me know if you run into any issues as I've done it a few times on different machines over the weekend.
For step 12, if you run the command with "-f" it will not take time but Win11 was crashing after installation. This might not be a persistent issue though.
View raw text
As archinstall does not currently support "pre-mount" partitioning option with LUKS encryption, this is what I did to dual boot ArchLinux & Win11 on a single SSD. General: -- BIOS: Secure Boot on -- (Optional) archinstall: Unified Kernel Image enabled -- Prepare GParted, ArchLinux & Win11 live usb's Assumption: Manual or automatic partitioning during archinstall created 2 partitions: -- nvme0n1p1 as boot; & -- nvme0n1p2 as encrypted root with all the btrfs subvolumes. Steps: 01 Boot into GParted live usb 02 Select default options 03 Select /dev/nvme0n1 04 Unlock encryption on /dev/nvme0n1p2 05 Shrink /dev/nvme0n1p2 to create unallocated space at the end (according to your Win11 space preference) 06 Lock /dev/nvme0n1p2 07 Apply changes 08 Reboot into ArchLinux live usb 09 Run "gdisk /dev/nvme0n1" 10 Create 2 partitions: -- p3 and assign last sector as "+128M" & type as "0C01"; & -- p4 and assign type as "0700" 11 (Optional) Run "cfdisk /dev/nvme0n1" to check partition types were done correctly 12 Run "mkfs.ntfs /dev/nvme0n1p4" (this will take time) 13 Reboot into Win11 live usb 14 Select nvme0n1p4 partition and install Win11 15 Boot into BIOS and change first boot option from Windows to Linux. 16 Systemd or Grub bootloader will automatically detect Win11 and you will have the option to choose either on boot. I'm not a tech person, if anyone has a simpler approach, please let me know. Also let me know if you run into any issues as I've done it a few times on different machines over the weekend. For step 12, if you run the command with "-f" it will not take time but Win11 was crashing after installation. This might not be a persistent issue though.
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.
No decision has been recorded yet.