FAQ
Common questions about what LocalDocks does, what it deliberately does not do, and where it is going.
Does LocalDocks need administrator rights?
No. LocalDocks never elevates and never requests SeDebugPrivilege. The consequence is that it can only see processes your own Windows account owns, which is a deliberate limit rather than a missing feature. See Processes.
Does LocalDocks send anything over the network?
No. There is no network client, no analytics, no crash reporter and no account. The only thing written outside its own settings is a local log of warnings and errors, capped at 512 KB, which is never transmitted.
Which platforms are supported?
Windows 10 version 1809 or later, x64 only. LocalDocks reads processes and sockets through Win32 APIs directly. Other platforms are future scope rather than a near-term plan.
Is LocalDocks on the Microsoft Store?
Not today. The Store requires an MSIX package and the build pipeline produces an NSIS installer, which cannot be submitted. A publisher identity is reserved, but no package has been built, signed or certified. See Download.
Why is a service missing from Developer mode?
Either it holds no listening socket, so it is a process rather than a service, or the Developer Registry classified it as something else, or it has never been seen by the registry and is reported as unclassified. System mode shows all three cases with the verdict on each row. See Classification.
Why does the conflicts tile show a dash instead of zero?
Port conflict detection is not implemented in V1. Showing zero would claim a detector ran and found nothing, so the tile shows an em dash and says detection is not implemented.
Can LocalDocks start, stop or restart my services?
Not in V1. It can force-terminate a process you own, with the identity re-verified first. Starting, stopping and restarting services is planned for V2 and is not built.
Does it work with Docker or WSL?
Not yet. Containers and WSL run their processes outside the Windows process table LocalDocks reads, so their workloads do not appear as processes. Sockets forwarded to the Windows host are still listed in Ports. Docker and WSL integration are future scope.
Why are CPU and GPU temperatures not shown?
Reading package temperatures requires model-specific registers, which requires a kernel driver. LocalDocks does not ship one and will not for a readout. What it does show is ACPI thermal zones, labelled as zones, because their mapping to physical components is defined by your firmware rather than by the application. See System telemetry.
How much does LocalDocks cost to run?
One Rust-owned sampler owns the cadence and the interface never triggers a scan. The cost of the most recent tick is published live in the Overview meta row, broken down into processes, sockets and telemetry, so you can measure it on your own machine rather than trust a number here.
Is LocalDocks open source?
It is MIT licensed. The repository becomes public as part of the V1 release, after the security and git history audit that shipping a process-reading tool deserves.
How do I report a wrong classification?
Open the service, copy the classification reason from the detail panel, and open an issue with that reason and the process name. Those two together identify which rule is wrong.
Something else
The repository carries the architecture notes, the roadmap and the release process, each written against the code rather than against intent. For anything not covered there, open an issue.