ContextCleaner: see every entry in the Windows 11 right-click menu, and which app added it — on the Microsoft Store.
Guided workflow variation

The port is free.Windows still won't let you bind it.

That "socket forbidden" error means the port fell inside a Hyper-V/WinNAT reserved range. Port Detective shows you instantly that nothing owns it — so you fix the exclusion instead of hunting a process that was never there.

If the port shows no owner in Port Detective, it's a Hyper-V/WinNAT reserved range, not a live conflict — so you go straight to the exclusion fix instead of hunting a phantom process.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Get it from Microsoft

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Full PortDetective overview
One-time purchase No telemetry Local-first

windows · native Rust · free + one-time Pro · no telemetry

If this sounds like your week

"An attempt was made to access a socket in a way forbidden by its access permissions."

This isn't your app and it isn't a normal "in use" conflict. Windows has *reserved* a block of ports for Hyper-V / WSL2 / Docker via WinNAT, and the port fell inside one of those excluded ranges. Nothing is listening on it — you simply aren't allowed to bind, and the error message tells you nothing about why.

Where tooling usually breaks

You search the port. Nothing is using it. It still won't bind.

`netstat` shows the port as free, so every "kill the process" tutorial is a dead end. The real answer is buried in `netsh int ipv4 show excludedportrange tcp` — a command almost nobody knows to run — and the fix involves reserving your range or restarting WinNAT. Hours disappear here.

Where PortDetective lands

Tell the difference between "in use" and "reserved" instantly.

Port Detective shows the port with no owner, which is your signal that this is an exclusion range, not a live conflict — so you stop hunting a process that was never there and go straight to the WinNAT fix. It's the fast triage that turns a confusing permission error into a two-minute decision.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Get it from Microsoft

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Compare free vs Port Detective Pro

windows · native Rust · free + one-time Pro · no telemetry

What you get

Feature highlights

Free

live listening-port visibility with process name, PID, and executable path, instant port lookup, and 5 free kills to try safe token-guarded termination.

Pro — Unlimited safe kills

end any rogue process in one click, guarded by a secure Process Token so you never terminate a recycled PID.

Pro — Port Guard

a native system-tray daemon watches your critical ports every 250 ms and can auto-kill an intruder and relaunch the right owner.

Pro — Full stack visibility

every TCP and UDP connection across IPv4 and IPv6, smooth even with thousands of connections.

Pro — Remote & Docker aware

scan VMs, Docker bridges, and network servers, and map host ports back to the container and image that published them.

Pro — Power workflow

Ctrl+K command palette, deep parent/child process inspection, connection-history timeline with CSV/JSON export, and per-port notes with backup/restore.

Both editions

native Rust, typically under 50 MB RAM, signed, no telemetry, no account wall — one-time Pro purchase on the Microsoft Store, no subscription.

Especially when

  • Find what process is using a port on Windows before you kill the wrong service
  • Resolve EADDRINUSE and listening-port conflicts without juggling netstat, tasklist, Task Manager, and Resource Monitor
  • Keep critical local ports protected from rogue processes with an always-on watchdog (Pro)
  • Map Docker host ports to containers and scan remote hosts during developer and IT troubleshooting (Pro)

Who benefits

Real-world scenarios

The mid-sprint context switch

You alt-tab from a call, run your dev server, and it dies on the port. A crashed instance from an hour ago never let go of the socket, and your flow state goes with it.

You type the port into Port Detective, see the zombie process by name, and end it with one guarded click. Back in your editor in under ten seconds — no terminal archaeology.

The three-repo afternoon

You're juggling several services and two of them want the port. You can't remember which repo is already running, and Task Manager has no port column to tell you.

Port Detective's live list shows exactly which executable and path owns the port, so you stop the right one instead of killing blind. Pro lets you pin the ports you care about so the clash is flagged before it bites.

The port that keeps coming back

You free the port, start your app, and ten minutes later a background service has grabbed it again. You're playing whack-a-mole with the same socket all day.

Port Detective Pro's Port Guard watches the port every 250 ms and can auto-end an intruder and relaunch the right owner — so the port you reserved stays yours without you babysitting it.

Deep dive

Why a "free" port still refuses to bind on Windows

When Hyper-V, WSL2, or Docker is enabled, Windows hands large blocks of the dynamic port range to WinNAT and reserves them. Any port inside a reserved block is off-limits to your app even though nothing is listening on it — which is why "kill the process" advice never works here. The tell is simple: a normal conflict has an owner you can see; a reserved-range block has no owner at all.

Port Detective makes that distinction obvious. If the port shows a process, end it. If the port shows nothing yet still won't bind, you're looking at an exclusion range, and the fix lives in WinNAT — not in Task Manager.

# List the ranges Windows has reserved (your port may fall inside one):
netsh int ipv4 show excludedportrange tcp

# Reserve your port so the dynamic range stops eating it, then restart WinNAT:
netsh int ipv4 add excludedportrange protocol=tcp startport=3000 numberofports=1
net stop winnat
net start winnat
Trusted by pragmatic desktop users

Built for people who prefer tools that stay local.

Real workflows: focus timers that stay visible, batches that never leave the disk, and renames you can rewind.

Customer review 01

PinPoint: Always On Top saves me so much time as I can organize all my report materials without having to flip between windows or tabs. I love the fact that it is straightforward and simple.

Senior Accountant · Manufacturing Company · United States · PinPoint Reviewed About PinPoint
Customer review 02

I used to get so frustrated when my Taskbar would freeze and disappear. Taskbar Sentinel has eliminated that pain without subjecting me to another subscription.

Darren · Calgary, Alberta, Canada · Taskbar Sentinel Reviewed About Taskbar Sentinel
Customer review 03

OpticBatch and MetaForge are a lifesaver for me as a person with a passion for photography. They give me the ability to stay organized and keep personal information confidential when I post pictures online.

Sherri · United States · OpticBatch & MetaForge Reviewed Browse the full catalog

Quotes are shown with customer permission; names and locations appear as reviewers provided them.

Free vs Pro editions

Free vs Pro

Start free. Upgrade when you want the active layer.

Both editions are native Rust, signed, and telemetry-free. Pick the free finder or unlock the full toolkit with a one-time Pro purchase.

Recommended

Pro

Port Detective Pro

One-time

One-time purchase · Perpetual license · No subscription

Get it from Microsoft

Everything in Free, plus the active layer: Port Guard, remote & Docker scans, deep inspection, and exportable history.

Free

Port Detective

Free

No account · No telemetry · Microsoft Store

Get the free edition

The everyday port finder: see what is listening, who owns it, and 5 kills to try safe termination.

CapabilityFree Pro
Live listening-port viewer with process name, PID & pathIncluded in FreeIncluded in Pro
Instant port lookup (type a port, get the process)Included in FreeIncluded in Pro
Safe, Process-Token-guarded kills5 free killsUnlimited
TCP + UDP across IPv4 and IPv6Not in FreeIncluded in Pro
Port Guard watchdog (250 ms) with auto-remediationNot in FreeIncluded in Pro
Remote scans of VMs, Docker bridges & serversNot in FreeIncluded in Pro
Docker host-to-container port mappingNot in FreeIncluded in Pro
Deep parent/child process inspectionNot in FreeIncluded in Pro
Connection-history timeline with CSV / JSON exportNot in FreeIncluded in Pro
Per-port notes with backup & restoreNot in FreeIncluded in Pro
Ctrl+K command palette & copy-as-commandNot in FreeIncluded in Pro
Get it from Microsoft Get the free edition

Our Core Moat

Engineered to respect your system boundaries.

System Resource Monitor (Idle State Comparison)
Automata Labs low idle memory footprint compared to generic Electron applications

Lightweight Native Stack

Compiled Rust core wrapped inside an optimized Tauri shell. No heavy background node loops or duplicate Chromium engines cooking your memory footprint (<25MB idle RAM).

100% Local-First Privacy

Executes entirely on-device with full offline isolation. Absolute zero background telemetry policies, no metrics aggregation, and zero mandatory cloud-sync accounts.

Perpetual Fallback Licenses

Pay a single, clear one-time purchase price. Own your specific native software utility execution tier permanently without artificial subscription paywalls or ongoing usage tax.

FAQ

Straight answers—no glossary dump

Why do I get "socket forbidden" when nothing is using the port?

Hyper-V/WSL2/Docker reserve blocks of ports through WinNAT, and the port likely fell inside one. Nothing is listening — you simply can't bind. If Port Detective shows no owner for the port, that's your confirmation it's a reserved range, and the fix is in `netsh` excludedportrange, not Task Manager.

Is it safe to kill the process — and will I kill the wrong one?

That's the real risk with the manual approach: Windows recycles PIDs, so the number you copied from netstat can point at something else by the time you run taskkill. Port Detective verifies process identity with a Process Token before it ends anything. The free edition includes 5 of these safe kills to try; Port Detective Pro makes them unlimited.

What does Port Detective Pro add over the free edition?

Free is the everyday finder: live port list, instant search, process name and path, and 5 one-time safe kills (they don't reset). Pro unlocks unlimited kills and the active layer — a Port Guard watchdog that re-frees a port every 250 ms, TCP + UDP across IPv4/IPv6, remote and Docker-aware scans, deep process inspection, exportable connection history, per-port notes, and a Ctrl+K palette. One-time purchase, no subscription, no telemetry.

Is Port Detective local-first, and how do I get it?

Yes — it reads your machine's own networking stack with no account, no cloud, and no telemetry for core use, and installs from the Microsoft Store. The free edition and Port Detective Pro are both listed there.

Related pages

Free in WSL. Taken in Windows. Same port, two stories. The port is free. Windows still won't let you bind it. Something's on port 3000. Find it. Free it. Get back to work. Something's on the port. Find it. Free it. Get back to work.

Stop debugging your OS.
Start shipping your code.

Find the process on any port and kill it safely with the free edition. Port Detective Pro adds the active layer — a background Port Guard watchdog, remote and Docker-aware scans, deep process inspection, and exportable history. One-time purchase, no subscription, no telemetry.

Pay once. Own it forever.

One-time purchase on the Microsoft Store · No subscription · Instant install

Get it from Microsoft

Buy through the Microsoft Store—instant install, automatic updates, and a Microsoft receipt for easy expensing. No account needed on our site, and no subscription on Store purchases.

Open full product page

Technical specifications

Technical specifications for procurement

Spec Implementation
Data Sovereignty Port and process data stays on the workstation; core features make no external network calls and no cloud dashboard is involved
Telemetry Status None; signed builds, no telemetry
Core Runtime Native Windows app built entirely in Rust (Tauri 2); typically under 50 MB RAM
Network Requirements Local inspection is fully offline; remote scans and Docker mapping are user-initiated outbound actions, not telemetry
Deployment Compatibility Windows 10 and 11; free edition plus one-time Pro purchase on the Microsoft Store
Free edition Live listening-port viewer, instant lookup, token-guarded safe kills
Pro — Port Guard Tray daemon polls watched ports every 250 ms with optional auto-remediation
Pro — Coverage TCP + UDP across IPv4/IPv6, remote scans, Docker host-to-container mapping
Pro — Workflow Ctrl+K palette, process lineage, connection history + CSV/JSON export, per-port notes