How Windows 2000 Updates Drivers in Device Manager

This article provides a concise overview of how Microsoft Windows 2000 manages hardware driver updates through Device Manager. It covers accessing the utility, navigating the Upgrade Device Driver Wizard, handling INF installation files, and the operating system's built-in digital signature verification and file protection mechanisms.

Accessing Device Manager

In Windows 2000, Device Manager serves as the central administrative interface for managing hardware configurations and drivers. To access it, administrators navigate to the Control Panel, open System, select the Hardware tab, and click the Device Manager button. Alternatively, it can be launched via the Computer Management console (compmgmt.msc).

Initiating the Driver Update

Once in Device Manager, users can update a device by following these steps:

  1. Locate the target hardware component within the hardware tree.
  2. Right-click the device and select Properties (or select Update Driver... directly from the context menu).
  3. In the device properties window, switch to the Driver tab.
  4. Click the Update Driver... button.

The Upgrade Device Driver Wizard

Clicking the update button launches the Upgrade Device Driver Wizard, which guides the user through the installation process using two primary methods:

  • Search for a suitable driver for my device (recommended): Windows 2000 automatically scans specified locations—such as floppy disk drives, CD-ROM drives, optional local search paths, or Microsoft Windows Update—for a compatible .inf setup information file matching the hardware's Plug and Play (PnP) hardware ID.
  • Display a list of the known drivers for this device so that I can choose a specific driver: This method allows the user to view all compatible devices found in the Windows driver cache or click Have Disk... to manually direct the wizard to a folder containing a manufacturer-supplied .inf file.

INF Processing and Driver Staging

When a driver is selected, Windows 2000 reads the target .inf file. The operating system identifies the hardware IDs, compares the driver version and date against the currently installed driver, and copies the necessary binary files (typically .sys, .dll, and .vxd where applicable) into the C:\WINNT\System32\drivers directory. It then updates the relevant hardware registry keys under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services and Enum.

Driver Signing and WHQL Verification

Windows 2000 introduced strict driver signing verification via the Windows Hardware Quality Labs (WHQL) program. During the update process:

  • If a driver is digitally signed by Microsoft, installation proceeds silently.
  • If a driver lacks a valid digital signature, the system checks the global Driver Signing Options policy (configured under System Properties > Hardware > Driver Signing). Depending on whether the policy is set to Ignore, Warn, or Block, Windows 2000 will either allow the driver to install, present a "Digital Signature Not Found" warning prompt requiring user confirmation, or block installation entirely.

Finalizing the Update

After copying the files and committing the registry changes, Windows 2000 attempts to restart the driver stack dynamically using its Plug and Play subsystem. If the device is hot-pluggable or supports dynamic driver reloading, the new driver becomes active immediately without downtime. If the device controls critical system resources (such as storage controllers or legacy non-PnP hardware), the wizard prompts the user to restart the operating system to complete the configuration.