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.
Installation on partition instead of drive / dual boot support
Reported by Danmoreng · filed Aug 27, 2025Closed upstream on 2025-08-31 by dhh. GitHub close reason: completed. No closing PR or commit is recorded — "completed" alone is not 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
I had my laptop setup to have dual boot between Manjaro Arch and Windows. Both on separate SSDs.
My plan was to simply install Omarchy instead of Manjaro on the same partition on drive 1, using the new Omarchy 2.0 ISO, while Windows stayed on drive 2.
First issue
There was not an option to install it on a partition, I could only select a drive. I guess this is due to the drive encryption, it would be nice to have the option though to install it on a partition only.
Whatever I thought: my Windows is on the other drive anyways, so I can wipe the entire drive. (bad idea, I had a second windows data partition on drive 1 - data gone, my bad)
Second issue
Since the complete drive got deleted including the UEFI partition which was on that drive and had a grub bootloader which allowed for dual boot, dual boot was gone. I don't know if that issue is easy to fix, as I suppose the whole system is not designed for dual boot, but it would be nice to have. Manjaro has that option when you install it.
ChatGPT managed to guide me through the process of restoring the windows boot loader onto the newly created UEFI partition by omarchy. So now I can boot back into Windows.
For anyone who needs to restore a Windows bootloader, I used this to repair it. You need to boot from a Windows USB installation stick.
Choose Repair your computer → Troubleshoot → Advanced options → Command Prompt.
Once inside the recovery Command Prompt:
1. Open diskpart and assign a drive letter to EFI partition
diskpart
list volLook for the FAT32 partition (\~512MB–1GB). That is your EFI (sda1 from Linux).
Suppose it is listed as Volume 2.
Assign it a letter:
select vol 2
assign letter=Z
exitNow the EFI partition is mounted as Z:.
2. Run bcdboot to restore Windows Boot Manager
Your Windows installation is on nvme0n1p2 (the big NTFS partition). In recovery it’s usually C:. Confirm with:
dir C:\WindowsIf you see the familiar System32, then C: is correct.
Now run:
bcdboot C:\Windows /s Z: /f UEFIExplanation:
C:\Windows→ points to your Windows installation./s Z:→ puts boot files on the EFI partition./f UEFI→ ensures UEFI boot format.
3. Reboot
Exit the command prompt and restart your system. Now your EFI partition will contain:
/EFI/Microsoft/Boot/bootmgfw.efiView raw text
I had my laptop setup to have dual boot between Manjaro Arch and Windows. Both on separate SSDs. My plan was to simply install Omarchy instead of Manjaro on the same partition on drive 1, using the new Omarchy 2.0 ISO, while Windows stayed on drive 2. ## First issue There was not an option to install it on a partition, I could only select a drive. I guess this is due to the drive encryption, it would be nice to have the option though to install it on a partition only. Whatever I thought: my Windows is on the other drive anyways, so I can wipe the entire drive. (bad idea, I had a second windows data partition on drive 1 - data gone, my bad) ## Second issue Since the complete drive got deleted including the UEFI partition which was on that drive and had a grub bootloader which allowed for dual boot, dual boot was gone. I don't know if that issue is easy to fix, as I suppose the whole system is not designed for dual boot, but it would be nice to have. Manjaro has that option when you install it. ChatGPT managed to guide me through the process of restoring the windows boot loader onto the newly created UEFI partition by omarchy. So now I can boot back into Windows. <details><summary>For anyone who needs to restore a Windows bootloader, I used this to repair it. You need to boot from a Windows USB installation stick.</summary> ## Choose Repair your computer → Troubleshoot → Advanced options → Command Prompt. Once inside the recovery **Command Prompt**: ### 1. Open diskpart and assign a drive letter to EFI partition ```cmd diskpart list vol ``` Look for the **FAT32** partition (\~512MB–1GB). That is your EFI (`sda1` from Linux). Suppose it is listed as `Volume 2`. Assign it a letter: ```cmd select vol 2 assign letter=Z exit ``` Now the EFI partition is mounted as `Z:`. --- ### 2. Run bcdboot to restore Windows Boot Manager Your Windows installation is on `nvme0n1p2` (the big NTFS partition). In recovery it’s usually `C:`. Confirm with: ```cmd dir C:\Windows ``` If you see the familiar `System32`, then `C:` is correct. Now run: ```cmd bcdboot C:\Windows /s Z: /f UEFI ``` Explanation: * `C:\Windows` → points to your Windows installation. * `/s Z:` → puts boot files on the EFI partition. * `/f UEFI` → ensures UEFI boot format. --- ### 3. Reboot Exit the command prompt and restart your system. Now your EFI partition will contain: ``` /EFI/Microsoft/Boot/bootmgfw.efi ``` </details>
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.