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.
Windows Update broke the Dockur Virtual Machine
Reported by pelephant2 · filed Jun 21, 2026Closed upstream on 2026-07-18. 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
System details
Omarchy 3.8.2
What's wrong?
On Omarchy 3.8.2 I've used the Windows Dockur as a virtual machine (VM) several times on my machine and it's worked great. I just did the first Windows update, restarted the VM, and it won't start. When I omarchy-windows-vm launch here are some of the errors I see:
- no RDP scancode found
- [ERROR][com.freerdp.core.transport] - [transport_read_layer]: BIO_read returned a system error 104: Connection reset by peer
- [ERROR][com.freerdp.core] - [transport_read_layer]: ERRCONNECT_CONNECT_TRANSPORT_FAILED
- [ERROR][com.freerdp.core] - [freerdp_connect]: freerdp_post_connect failed
- RDP session closed. Stopping Windows VM...
I don't even know how to begin troubleshooting this. Is there any way to repair such a thing? I have several things on Windows not backed up and don't want to have to wipe anything if possible.
View raw text
### System details Omarchy 3.8.2 ### What's wrong? On Omarchy 3.8.2 I've used the Windows Dockur as a virtual machine (VM) several times on my machine and it's worked great. I just did the first Windows update, restarted the VM, and it won't start. When I `omarchy-windows-vm launch` here are some of the errors I see: - `no RDP scancode found` - `[ERROR][com.freerdp.core.transport] - [transport_read_layer]: BIO_read returned a system error 104: Connection reset by peer` - `[ERROR][com.freerdp.core] - [transport_read_layer]: ERRCONNECT_CONNECT_TRANSPORT_FAILED` - `[ERROR][com.freerdp.core] - [freerdp_connect]: freerdp_post_connect failed` - `RDP session closed. Stopping Windows VM...` I don't even know how to begin troubleshooting this. Is there any way to repair such a thing? I have several things on Windows not backed up and don't want to have to wipe anything if possible.
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.