Section 9: Device Properties Deep Dive

The Big Picture: The Device's Personal File

Everything Device Manager knows about one device sits in its Properties window. Think of it as the device's personal file at a doctor's office: one page with the current state (General), one with the treatment given (Driver), one with the full record of facts (Details), one with the visit history (Events), and so on.

How to open it: Double-click any device in Device Manager (or right-click → Properties). You will see tabs along the top. Which tabs you get depends on the device. A few devices lack the Resources or Power Management tabs.

┌─ Properties ─────────────────────────────────────────────────────┐
│ [General] [Advanced] [Driver] [Details] [Events] [Resources]     │
│ [Power Management]                                               │
└──────────────────────────────────────────────────────────────────┘

A device may also have an Advanced tab (settings the driver offers, such as the speed of a network card) and other tabs added by drivers. The six below exist for most devices.

9.1 General Tab (Status)

What it is: The first tab. It tells you what the device is and whether it works.

┌─ General tab ──────────────────────────────────────────┐
│ Realtek PCIe GbE Family Controller                     │
│ Device type:     Network adapters                      │
│ Manufacturer:    Realtek                               │
│ Location:        PCI bus 3, device 0, function 0       │
│                                                        │
│ Device status                                          │
│ ┌────────────────────────────────────────────────────┐ │
│ │ This device is working properly.                   │ │
│ └────────────────────────────────────────────────────┘ │
│ [ Change settings ]                                    │
└────────────────────────────────────────────────────────┘

(Mock-up. Your wording may be slightly different on your version.)

Use it for: Reading the exact error code and message of a broken device, and the location of the device. Location tells you which slot or port it uses, which is helpful when you have two identical devices.

If you see the button Troubleshoot, Windows may offer a built-in help for that device type. It is a good first try for simple problems.

9.2 Driver Tab (Version, Provider, Date, Digital Signer)

What it is: Facts about the driver currently running the device, and the buttons to change it.

The buttons are:

Reading it:

┌─ Driver tab ───────────────────────────────────────────┐
│ Driver Provider:  Realtek                              │
│ Driver Date:      <date>                               │
│ Driver Version:   <version>                            │
│ Digital Signer:   Microsoft Windows Hardware           │
│                   Compatibility Publisher              │
└────────────────────────────────────────────────────────┘

Digital Signer note. It is normal to see "Microsoft Windows Hardware Compatibility Publisher" for a maker's driver. That means the driver passed Microsoft's testing and was signed through Microsoft. It does not mean Microsoft wrote it. The exact names may look different on your version.

Common finding: A graphics card showing "Microsoft Basic Display Adapter" with provider Microsoft is running on a generic fallback (Section 3.2). The fix is to install the maker's driver.

9.3 Details Tab (Property Browser: Class GUID, Device Instance Path)

What it is: The Details tab is a property browser. At the top is a drop-down list called Property. Pick one, and its value shows below. This tab holds the facts that other tabs do not show.

┌─ Details tab ────────────────────────────────────────────────┐
│ Property:  [ Device instance path                       v]   │
│ Value:                                                       │
│  PCI\VEN_10EC&DEV_8168&SUBSYS_816810EC&REV_15\4&1c2d3e&0&00E5│
└──────────────────────────────────────────────────────────────┘

Useful properties:

(The list of properties and their names may differ slightly on your version.)

GUID. A GUID (Globally Unique IDentifier) is a long label made of numbers and letters, in groups: {4d36e972-e325-11ce-bfc1-08002be10318}. It is made so that no two things in the world have the same one. Windows uses GUIDs as class names. For example, the GUID that ends in ...08002be10318 is the class for network adapters, and every network adapter node shows it in its Class Guid. The GUID does not change from one PC to another.

Device instance path. Section 2.2 introduced it. It has three parts:

PCI\VEN_10EC&DEV_8168&SUBSYS_816810EC&REV_15\4&1c2d3e&0&00E5
│   └────────── device ID ──────────────────┘ └─ instance ID ─┘
└ bus

The last piece makes the path unique even if you own two identical cards. The command pnputil /enum-devices shows this same string as Instance ID, so you can match what you see in Device Manager with what you see in the command line.

Power data. Opening this property shows the device's power states (D0 to D3). D0 means fully on. D3 means off. Windows may put an idle device into a low state to save energy (Chapter 4, Section 5 explained power management). A list may also show which states the device can wake the PC from.

Copy what you need. Right-click a value → Copy. This is the safest way to share an exact ID with someone helping you.

Another view of the same facts. PowerShell can print the same properties:

Get-PnpDevice -PresentOnly | Select-Object Class, FriendlyName, InstanceId

9.4 Events Tab (Device Install/Config Events)

What it is: The Events tab lists a short history of what Windows did with this device: when its driver was first installed, when it was configured, when it was started.

┌─ Events tab ────────────────────────────────────────────┐
│ Information                                             │
│ Device configured (<driver name>.inf)                   │
│ Device started (<service name>)                         │
│ Device installed (<driver name>.inf)                    │
│ ...                                                     │
│ [ View All Events ]                                     │
└─────────────────────────────────────────────────────────┘

Each line has a date and time. Select one to see its details, such as the driver's INF file name.

Why use it:

View All Events. The button opens a larger view with more detail, built from Windows' event logs. For the full story use Event Viewer (eventvwr.msc). On a normal home PC, the most helpful logs are under Applications and Services Logs → Microsoft → Windows → Kernel-PnP, and also Windows Logs → System. The log names and layout may look different on your version.

Tip: After a driver update that causes trouble, the Events tab helps you see exactly when the change happened, so you can match it with the time the problem started.

9.5 Resources Tab

What it is: The Resources tab lists the resources this one device uses: IRQ, I/O range, memory range (and sometimes DMA). It is the per-device version of the Resources by type view (Section 8).

┌─ Resources tab ──────────────────────────────────────────┐
│ Resource type        Setting                             │
│ Memory Range         00000000FB000000 - 00000000FBFFFFFF │
│ I/O Range            0000E000 - 0000E07F                 │
│ IRQ                  0xFFFFFFF0 (-16)                    │
│                                                          │
│ Conflicting device list:                                 │
│ No conflicts.                                            │
└──────────────────────────────────────────────────────────┘

(Mock-up with invented values.)

What to look for:

If a device has no Resources tab, it uses no hardware resources (for example, many software devices).

Power Management tab (bonus). Some devices have this tab too. The two key choices are:

If a USB mouse or Wi-Fi adapter misbehaves after sleep, this tab is a place to look. Changing it can affect battery life, so note the original setting first.

Summary