Running Buildkitd.exe standalone under Windows

Description

Currently, when trying to run buildkitd.exe as a normal process under Windows, an explicit worker would be required.

C:>buildkitd
time="2025-12-22T17:11:14+01:00" level=warning msg="skipping containerd worker, as "\\\\.\\pipe\\containerd-containerd" does not exist"
buildkitd: no worker found, rebuild the buildkit daemon?
main.newWorkerController
/src/cmd/buildkitd/main.go:911
main.newController
/src/cmd/buildkitd/main.go:804
main.main.func3
/src/cmd/buildkitd/main.go:362
github.com/urfave/cli.HandleAction
/src/vendor/github.com/urfave/cli/app.go:524
github.com/urfave/cli.(*App).Run
/src/vendor/github.com/urfave/cli/app.go:286
main.main
/src/cmd/buildkitd/main.go:429
runtime.main
/usr/local/go/src/runtime/proc.go:285
runtime.goexit
/usr/local/go/src/runtime/asm_amd64.s:1693

No default worker would be available under Windows, even running the process as an Administrator

How such support could be implemented to be able to run Buildkitd standalone natively on Windows?

I can think about leveraging CIM/CIMFS - https://github.com/containerd/containerd/issues/8346 in Windows - Host Compute Service Shim (hcsshim) as done in Containerd.

Start in cmd/buildkitd/main.go at the worker-controller and startup locations shown in the stack trace: lines 362, 804, and 911. Trace how workers are selected on Windows and define what is needed for buildkitd.exe to run standalone with an available default worker.