Map Microsoft-Windows-Partition%4Diagnostic.evtx for EventID 1006 #25
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Windows 10 creates an entry in Microsoft-Windows-Partition%4Diagnostic.evtx, EventID 1006, each time a USB device is connected to or disconnected from the system.
USBs can have two serial number values and they are not always the same. The serial number commonly referred to as iSerialNumber, is almost always unique and the value used in the WIndows registry to track USB activity. The other serial number value, which I will refer to as the "alternate" serial number, can have duplicates or may be null. The serial number value recorded in this event log is the non-unique one, the alternate serial number.
When analyzing the physical USB device, different tools display one or the other serial number. There a few tools that display both. You also use PowerShell to display both serial numbers. In the absence of the physical devices, this log allows us to map between the non-unique serial number and the unique one stored in the registry by using the DiskID. The DiskID is provided in this log and in the SYSTEM\CurrentControlSet\Enum\USBSTOR\ Device-Class\Device-SerialNumber\Device Parameters\Partmgr.