Argusic could not verify that windows runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 3 errors on the way, and recorded the session.

How did Argusic test windows?

On a fresh, disposable machine, with every command recorded and the repository pinned at commit 013ea27498e0. 2 attempts are recorded, and the full method is on the methodology page.

What did it cost to test windows?

The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.

How long does windows take to install?

0 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.

Does windows need a GPU?

Not to start. Argusic reached a running state on a machine with no GPU.

What goes wrong when installing windows?

3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.

Where is the evidence for windows?

All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.

windows

Windows inside a Docker container.

Could not verifysource: GitHubShellMITcommit 013ea27498e0

Shell, MIT licensed. The project labels itself: docker, docker container, virtualization, windows, windows virtual desktop, windows virtual machine, windows virtual machines and windows vm.

Argusic could not get windows running. An Argusic agent installed it in 0 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.

All 12 shell scripts pass ShellCheck and bash syntax check. All 29 XML files, all JSON files, and all YAML files (compose.yml, kubernetes.yml, 9 workflows) are syntactically valid. The Dockerfile passes Hadolint with the same 3 pre-existing warnings the CI ignores. No container runtime could start due to seccomp-based unshare restrictions in this environment.
What the agent ended up with on a clean machine, in its own words. How this is measured

Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 50 of 100 (the mean of this project's run scores).

At a glance

verdict: Could not verify
Argusic Score: 50 / 100
cost of the verifying run: $0.23 (measured)
recorded runs: 2
last tested: 2026-10-07
stars: 53,539
forks: 0
open issues: 0
watchers: 0
created: -
last push: -

Subject data from GitHub, linked at the top of this page. Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.

What was measured

From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words

The agent's own words, worst first, never rewritten into advice.

Docker daemon cannot start in this unprivileged container (unshare: Operation not permitted due to seccomp)
Podman binary extracted but depends on libgpgme.so.11 not present in the environment
/dev/kvm not available - cannot run QEMU with acceleration

Install time: under a minute
Cold machine to finish: 13 minutes
Errors hit and fixed: 3 hit, 3 fixed with no human help
How the result was proved: ShellCheck v0.11.0 on 12 scripts (all pass, 0 errors, 0 warnings with CI exclusions). Hadolint on Dockerfile (3 pre-existing warnings, same as CI ignores). XML validation on 29 files. JSON validation on all config files. YAML validation on compose.yml + 9 workflows + kubernetes.yml. Bash -n syntax check on all 12 scripts.
Model tokens used: 112,809
Exact commit tested: 013ea27498e0
Container image: sha256:cdd920bce783

What was not measured

The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.

Peak GPU memory: this ran on a CPU machine, so there was no GPU to sample
Behaviour over a long run: each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Whether it works at all: this run verified nothing, so this page makes no claim either way

The end of the recording

The last lines of the terminal session that decided this verdict, exactly as they were recorded.

removing /home/runner/.local/bin/containerd
removing /home/runner/.local/bin/containerd-shim-runc-v2
removing /home/runner/.local/bin/ctr
removing /home/runner/.local/bin/docker-init
removing /home/runner/.local/bin/docker-proxy
removing /home/runner/.local/bin/runc
removing /home/runner/.local/bin/rootlesskit
removing /home/runner/.local/bin/rootlessctl
removing /home/runner/.local/bin/slirp4netns
done
tokens used
112,809

Replay the whole session, every command from a clean machine to this point.

How it was tested

One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.

Strengths and limits

Measured facts, not opinions. How this is written.

What went well

Installed in 0 minutes, faster than the median of the 12 comparable projects Argusic has measured.
Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
Licensed MIT, as reported by its host.
Measured 2 times, so the result is not a one-off.

What did not, or is not known

An agent with no time limit did not get it running.

Of the 13 docker projects Argusic has installed and timed, windows was the 1st fastest to reach a running state, and 9 of 13 reached one at all.

Also tested, in the same area

Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.

Run history

tested by	attempt	outcome	score	cost USD	when
Argusic Runner	2/3	Did not run	50.00	0.23	2026-10-07 07:44 UTC
Argusic Runner	1/3	Did not run	50.00	0.16	2026-10-07 07:30 UTC

Topics (from GitHub)

docker docker-container virtualization windows windows-virtual-desktop windows-virtual-machine windows-virtual-machines windows-vm

Embed the badge

Markdown for the project README. It links back here; terms on the terms page.

[![Tested by Argusic](https://argusic.com/badge/windows.svg)](https://argusic.com/subject/windows)

Questions

Does windows run?: Argusic could not verify that windows runs. Argusic installed and launched it on a clean machine in 0 minutes, hitting 3 errors on the way, and recorded the session.
How did Argusic test windows?: On a fresh, disposable machine, with every command recorded and the repository pinned at commit 013ea27498e0. 2 attempts are recorded, and the full method is on the methodology page.
What did it cost to test windows?: The run that produced this verdict cost $0.23: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
How long does windows take to install?: 0 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
Does windows need a GPU?: Not to start. Argusic reached a running state on a machine with no GPU.
What goes wrong when installing windows?: 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
How does windows compare with the alternatives?: Of the 13 docker projects Argusic has installed and timed, windows was the 1st fastest to reach a running state, and 9 of 13 reached one at all.
Where is the evidence for windows?: All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.