Which USB drives were plugged into this PC
Open the machine's own setupapi.dev.log and read the device installs out of it, with the vendor, product and serial number of each USB drive and the moment Windows first saw it. In your browser.
1. The log
Windows keeps it at C:\Windows\INF\setupapi.dev.log. Copy it off the machine and open it here; nothing is uploaded and the file on disk is never written to.
No log open yet.
2. What the log covers
3. The devices
Every device install the log records, oldest first. A row is written when Windows installed the device, which is the first time it was seen on this machine or the time its driver changed, not every time it was plugged in.
| Installed (that machine’s clock) | Kind | Device | Serial | Result |
|---|
How it works
What this answers, and what it does not
The log is a record of installs, not of insertions, and everything below follows from that one fact.
- It answers: was this device ever attached to this machine, and when was it first attached. Windows writes a section the first time it sees a device and when the driver changes. That first timestamp is good evidence and is often the one that matters.
- It does not answer: how many times, or how long for. Plugging in an already-installed drive writes nothing. A drive used every day for a year appears once. Nothing in this file counts insertions, and a tool that claimed to would be inventing it.
- A failed install still means the device was plugged in. Windows cannot install a driver it does not have, and the section it writes says
FAILUREand a code. The device was physically connected all the same, which is why those rows are shown by default rather than filtered away as noise. - The times are that machine's local clock. Not UTC, not yours. If the clock was wrong, the log is wrong in the same direction, and no tool can tell from the file alone.
- Absence is weak. The log is capped; when it fills, Windows renames it with a date and starts a new one. A device missing from the file you have may be in a backup beside it, and the backups are deleted routinely.
- A generated ID is not a serial number. A USB storage device that reports a serial has it in the last part of its instance ID. One that does not gets an ID Windows made up, and the test is the second character: an
&there means generated. A generated ID identifies the device on that one computer and nowhere else, so matching one against another machine's log is a mistake that looks like a finding. Rows here say which kind each one is. - This is one artefact. Corroborate it: the
USBSTORkeys in the SYSTEM registry hive carry the same devices with their own timestamps, and the Windows event log records more. A conclusion resting on this file alone is resting on one leg.
If the copy of the log might be relied on, hash it before you read it (CHECKSUM takes a SHA-256 in the browser), and record where it came from with CHAIN. The first question asked of any examination is whether the copy examined is the copy received.
Questions people ask about PLUGGED
Where do I find setupapi.dev.log?
C:\Windows\INF\setupapi.dev.log. It is a plain text file and reading it needs administrator rights on that machine, though copying it does not once you have access. Windows keeps dated backups beside it, named like setupapi.dev.20260514_081233.log, and those open here too.
Does this tell me how many times a drive was plugged in?
No, and nothing does from this file. Windows writes a section when it installs a device: the first time it sees it, or when the driver changes. Plugging in a drive that is already installed writes nothing at all. So a drive used daily for a year appears once, at the start. What the log gives you, and gives you well, is when a device was first attached to that machine.
What is a generated serial number?
A USB storage device that reports a serial number has it in the last part of its device instance ID. One that does not (and cheap drives often do not) gets an ID that Windows makes up, and the long-standing test is the second character: an & there means Windows generated it.
The difference matters. A reported serial identifies that physical drive anywhere. A generated one identifies it on that one computer, so matching it against a second machine’s log proves nothing while looking exactly like proof.
Are the times UTC?
No. They are the local clock of the machine that wrote the log, as it was set at the time. This page shows them exactly as written and does not shift them into any other zone, because a timestamp quietly moved by an hour is how a statement ends up wrong. If the machine’s clock was off, the log is off with it, and nothing in the file reveals that.
A device I know was used is not in the log. What does that mean?
Less than it looks like. The log is capped, and when it fills Windows renames it with a date and starts a new one, so the file you have may not reach far enough back. Those backups are also cleaned up routinely. Absence here is weak evidence, and it is worth checking the USBSTOR keys in the SYSTEM registry hive before concluding anything.
Can I use this for phones and cameras?
Up to a point. A phone or camera connected over MTP appears as a SWD\WPDBUSENUM device and the log records the install with its timestamp, but the identifier is a Windows GUID rather than a make and model, so it tells you something was connected and not what. Tick off “removable storage only” to see those rows.
Is the log uploaded?
No. It is read in this tab by the script on this page, and the copy on your disk is never written to. That matters here more than for most files: a device log is usually taken off somebody else’s machine, often under an authority that does not extend to handing it to a website.
Is this enough on its own?
No, and the page says so rather than letting you find out later. It is one artefact. The registry carries the same devices with their own timestamps, the event log carries more, and a conclusion resting on this file alone is resting on one leg. Hash the log with CHECKSUM and record where it came from with CHAIN before you read it, because the first question asked of any examination is whether the copy examined is the copy received.
Doing this often? The Sovereign Console loads disk images and Windows artefacts into one case, and puts every device and timestamp on one timeline. On its own, US$2 a month; with everything else, US$5 a month or US$48 a year.