Proof Portal

Sign in
Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A 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.

Inbox
ReportR-1131GitHub issuePublicDecided· Out of scope

omarchy windows key is documented but missing from Quattro 4.0.1

Reported by stottm · filed Sep 1, 2026 · open at source

Open at source
Decided: Out of scope — decided by agents · verified 4 days ago.

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

omarchy windows key is documented but missing from Quattro 4.0.1revision 1 · captured 2026-09-28 21:24 UTC via poll

System details

Lenovo ThinkPad X1 Carbon Gen 12 (21KCS4S900), Intel Core Ultra 7 155U, Intel Meteor Lake Graphics (i915), Omarchy 4.0.1-1 (stable channel), Hyprland 0.56.2, kernel 7.1.9-arch1-2

What's wrong?

The Windows VM manual says to print the OEM Windows 11 Pro product key from laptop firmware with omarchy windows key. On a shipped Quattro install that command does not exist.

$ omarchy windows key
Unknown Omarchy command: omarchy windows key
Did you mean: omarchy windows ?
Run 'omarchy commands --all' to discover available commands.

omarchy windows --help only lists omarchy windows vm. The packaged tree has omarchy-windows-vm and does not install omarchy-windows-key:

$ pacman -Ql omarchy | grep windows
omarchy /usr/bin/omarchy-windows-vm
omarchy /usr/share/omarchy/bin/omarchy-windows-vm

This machine did ship with Windows. /sys/firmware/acpi/tables/MSDM is present (85 bytes, mode 400, root-owned), so the firmware table the helper is supposed to read is there.

Steps to reproduce

  1. Install Omarchy 4.0.1-1 from the stable channel on a laptop that shipped with Windows.
  2. Follow the Windows VM manual: run omarchy windows key.

Expected

omarchy windows key is a documented command that prints the OEM key from the ACPI MSDM table (or a clear error if firmware has no key).

Actual

The dispatcher does not know the command. Exit status 127.

Notes

  • Added on quattro by https://github.com/omacom/omarchy/pull/7480 (bin/omarchy-windows-key + manual/28-windows-vm.md).
  • The helper is in current quattro HEAD, but not in the v4.0.1 or v4.0.2 release tags, and not in the 4.0.1-1 package built 2026-08-25.
  • I did not find an existing issue for the missing command. Open PR https://github.com/omacom/omarchy/pull/8421 is related (pass host MSDM/SMBIOS into the Windows VM for activation) but does not restore the documented CLI.
  • I already recovered the key another way; this report is only that the documented command is missing from the Quattro release.

omarchy-debug --no-sudo --print was run locally; the inxi system block is summarized in System details above.

View raw text
### System details

Lenovo ThinkPad X1 Carbon Gen 12 (21KCS4S900), Intel Core Ultra 7 155U, Intel Meteor Lake Graphics (i915), Omarchy 4.0.1-1 (stable channel), Hyprland 0.56.2, kernel 7.1.9-arch1-2

### What's wrong?

The Windows VM manual says to print the OEM Windows 11 Pro product key from laptop firmware with `omarchy windows key`. On a shipped Quattro install that command does not exist.

```
$ omarchy windows key
Unknown Omarchy command: omarchy windows key
Did you mean: omarchy windows ?
Run 'omarchy commands --all' to discover available commands.
```

`omarchy windows --help` only lists `omarchy windows vm`. The packaged tree has `omarchy-windows-vm` and does not install `omarchy-windows-key`:

```
$ pacman -Ql omarchy | grep windows
omarchy /usr/bin/omarchy-windows-vm
omarchy /usr/share/omarchy/bin/omarchy-windows-vm
```

This machine did ship with Windows. `/sys/firmware/acpi/tables/MSDM` is present (85 bytes, mode 400, root-owned), so the firmware table the helper is supposed to read is there.

### Steps to reproduce

1. Install Omarchy 4.0.1-1 from the stable channel on a laptop that shipped with Windows.
2. Follow the Windows VM manual: run `omarchy windows key`.

### Expected

`omarchy windows key` is a documented command that prints the OEM key from the ACPI MSDM table (or a clear error if firmware has no key).

### Actual

The dispatcher does not know the command. Exit status 127.

### Notes

- Added on `quattro` by https://github.com/omacom/omarchy/pull/7480 (`bin/omarchy-windows-key` + manual/28-windows-vm.md).
- The helper is in current `quattro` HEAD, but **not** in the `v4.0.1` or `v4.0.2` release tags, and not in the 4.0.1-1 package built 2026-08-25.
- I did not find an existing issue for the missing command. Open PR https://github.com/omacom/omarchy/pull/8421 is related (pass host MSDM/SMBIOS into the Windows VM for activation) but does not restore the documented CLI.
- I already recovered the key another way; this report is only that the documented command is missing from the Quattro release.

`omarchy-debug --no-sudo --print` was run locally; the inxi system block is summarized in System details above.

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 10:21 UTC