When a support ticket needs the MAC address of the correct Windows adapter, use getmac /v /fo list to inspect a verbose local inventory. If you need a structured attachment, getmac /v /fo csv requests CSV output. Neither command changes adapter settings. The crucial step is matching the returned adapter information to the connection involved in the ticket, rather than copying the first address you see.
This is an evidence-collection workflow, not a network repair or a general explanation of MAC addressing. It is useful when a laptop has Ethernet, Wi-Fi and virtual interfaces and someone asks which address belongs in an inventory record.
Start with a readable local listing
Open Command Prompt on the affected computer and run:
getmac /v /fo listMicrosoft documents /v as verbose output and /fo list as the list output format. Without a remote-computer option, the command targets the local computer. Read the adapter-identifying fields alongside the physical address, and retain enough context to distinguish similarly named interfaces.
Do not assume the first row is the connection carrying the failing application. A machine can have several interfaces, and a returned identifier is not a statement about which route an application selected. Record the computer name, collection time and whether a dock or VPN was in use as separate ticket notes rather than treating them as facts supplied by this command.
Match the reader’s actual support task
Suppose a hypothetical support request says, “Please provide the dock’s Ethernet address, not the laptop’s wireless address.” Review the verbose connection and adapter information for the likely Ethernet entry, then compare it with the adapter shown in Windows network settings. If two entries remain ambiguous, ask the device or network administrator to confirm the intended interface before changing a reservation or inventory database.
Do not disconnect the dock, disable Wi-Fi or reset the adapter solely to make the list shorter. Those changes can interrupt work and alter the state you are trying to document. A list that includes virtual or disconnected interfaces is a reason to preserve context, not a reason to delete drivers.
If your task concerns a neighbour’s address rather than the local computer’s adapters, that is a different investigation. Our guide to reading the Windows ARP cache for one adapter explains the separate cache-inspection workflow. Do not submit a neighbour’s cached address as the local device’s inventory identifier.
Request CSV without dropping the headers
For a structured view, run:
getmac /v /fo csvMicrosoft supports table, list and CSV formats. Leaving out /nh retains the header row, which helps a recipient interpret the columns. Do not split a CSV line by every comma in a script: CSV can contain quoted fields, so downstream processing should use a CSV-aware parser.
If an attachment is required, you can direct the output to a new file in a disposable collection folder:
getmac /v /fo csv > adapter-inventory.csvImportant: this redirection creates a file in the current directory and can overwrite an existing file with the same name. Choose an empty, approved working folder and confirm the name is unused first. Then open the resulting file and check that it actually contains headers and adapter rows, not an error message. Do not describe an empty attachment as a successful inventory.
Know what the snapshot cannot establish
A recorded address does not prove DHCP reservation correctness, switch-port placement, successful name resolution or application connectivity. The command does not validate the address against an asset database. It also should not be treated as proof that an identifier is permanent or that the device is authorised to use a network.
Keep the original output rather than manually shortening it to an address alone. If the downstream system requires a particular address format, record any reformatted value separately and preserve the collected version. That makes transcription errors easier to identify without silently rewriting the evidence.
Keep collection local and protect the attachment
Microsoft also documents remote-computer and credential options. They are unnecessary for this local workflow. Do not paste passwords into command lines or copy credential-bearing examples into a ticket. If remote collection is needed, use your organisation’s approved administration process and permissions.
Share inventory files only with the people who need them. Adapter names, identifiers and network-related metadata can reveal details about a device even when no password is present. Remove the temporary attachment after the approved retention period, not before the ticket’s evidence has been preserved properly.
Final support checklist
- Collected on the intended computer, with no remote target supplied.
- Correct adapter identified rather than the first result copied.
- Original labels and address retained with collection context.
- CSV headers and actual records inspected before attachment.
- No connection reset, reservation change or connectivity claim made from the inventory alone.
Source: Microsoft Learn’s getmac syntax, parameters and examples. These commands are documentation-based examples; no Windows execution is claimed here.
Educational-use disclaimer: Test commands in an approved environment before production use. The site owner is not responsible for misuse, damage, data loss or production issues.
