KitForma field notes

Read Wi-Fi evidence without confusing support and connection

Collect a useful Windows report and understand what each observation can establish.

Collect one device and one connection

Start with the PC that has the problem, connected in the location where you notice it. Record the date and the exact access point if a mesh system is involved. A report from a different laptop or an earlier driver can create a convincing but incorrect diagnosis.

  • Use winver for the installed Windows version.
  • Use netsh wlan show drivers for adapter capabilities.
  • Use Windows Wi-Fi properties for the connected protocol and band value.

Keep capability and observation separate

The driver list answers what the installed adapter driver exposes. The connection properties answer what the current link reports. Enter each in its own field. A manufacturer feature on a box is not a substitute for either observation.

When answers disagree, stop changing settings and collect fresh evidence. Multiple adapters, USB dongles and older mesh nodes are common reasons that a report describes a different path from the one in use.

Share only the useful part

The parser uses the radio and authentication capability fields. Names, physical addresses and network identifiers do not help this diagnosis. The downloaded analysis includes extracted capability values, not the original pasted text. Review any screenshot separately before sharing it with support.

The evidence behind the check

Sources & assumptions

Rules are reviewed against the references below. Manufacturer updates, firmware and your exact setup can change the result.

Reviewed 2026-10-13. Read our methodology or report an issue.

Essential local storage remembers this choice for up to 180 days. Your choice applies to this subdomain. Global Privacy Control and Do Not Track override optional measurement.

Advertising has a separate choice. Use Advertising preferences in the footer to allow or reject the optional guide-page banner.