🎯

Aim / Objective

To identify missing or malfunctioning hardware drivers in Device Manager, inspect Hardware IDs, install, update, and rollback device drivers, and practice installation and clean uninstallation of application software using GUI and CLI package managers.

🧰

Hardware & Software Requirements

Hardware Components

✓ PC running Windows 10/11 or Ubuntu Linux
✓ External USB Peripheral (e.g., USB Wi-Fi dongle, USB-to-Serial adapter, webcam, or USB sound card) to demonstrate driver detection
✓ Internet connection for fetching vendor driver packages

Software, OS & Tools

✓ Windows Device Manager (`devmgmt.msc`) and PowerShell
✓ Linux Driver & PCI utilities (`lspci -k`, `lsusb`, `modprobe`)
✓ Windows Package Manager (`winget`) and Linux `apt`
✓ Sample software installers (MSI and EXE installers, portable software, and open-source utilities like 7-Zip, VLC, Git)

👨‍🏫

Teacher's Lab Delivery Guide

Essential briefing notes, pedagogy, and setup tips for lab instructors

Faculty Exclusive

⏱ 5-Minute Pre-Lab Lecture Briefing:

Explain that a computer without drivers is like having a foreign musician in an orchestra who doesn't speak the conductor's language. Device drivers run with kernel-level privileges; bad drivers are the #1 cause of Windows Blue Screen of Death (BSOD) crashes. Teach how to find vendor Hardware IDs (VEN and DEV codes).

📝 Key Concepts to Write on Whiteboard:

Kernel-mode drivers vs User-mode drivers
Device Manager visual status: Normal, Yellow Exclamation Mark (Driver Missing/Failed), Down Arrow (Disabled)
Hardware IDs: Vendor ID (VEN_xxxx) and Device ID (DEV_xxxx)
Driver lifecycle: Install, Update, Roll Back, Disable, Uninstall
Application distribution formats: `.exe`, `.msi` (Windows Installer), CLI Package Managers (`winget`, `apt`, `choco`)
Residual files and registry clean-up during uninstallation

⚙ Pre-Class Lab Setup:

Demonstrate Device Manager on projector. Intentionally disable a non-critical device (like audio or Bluetooth) to show students what an inactive device looks like and how to re-enable/update it.

⚠ Common Student Pitfalls & Fixes:

Students download drivers from sketchy 3rd-party "driver updater" scam websites. Teach them to ONLY obtain drivers from the official OEM manufacturer website (Intel, Realtek, Dell, HP, ASUS).

🛡 Lab Safety & ESD Precautions:

Do not uninstall core system drivers such as display adapter or storage controller without instructor guidance.

📜

Step-by-Step Practical Procedure

1

Open Device Manager and Inspect Hardware Hierarchy

Press `Win + X` and choose "Device Manager" (or run `devmgmt.msc`). Expand categories (Display adapters, Network adapters, Sound, video and game controllers). Check for any items flagged with a yellow warning triangle.

Command / Action:

Shortcut: Win + R -> devmgmt.msc

💡

Teacher Note / Pro-Tip: A yellow triangle indicates the OS detects physical hardware but lacks a compatible driver to communicate with it.

2

Inspect Hardware ID (Vendor & Device Codes)

Right-click an adapter -> "Properties" -> "Details" tab. In the Property dropdown, select "Hardware Ids". Observe strings like `PCI\VEN_10EC&DEV_8168`. Explain that `VEN_10EC` identifies Realtek and `DEV_8168` identifies the Gigabit Ethernet Controller.

Command / Action:

Path: Device Properties -> Details -> Hardware Ids

💡

Teacher Note / Pro-Tip: You can search the VEN and DEV codes on databases like PCI-ID (pci-ids.ucw.cz) to find the exact official driver.

3

Install, Update, and Roll Back a Device Driver

Right-click the target device -> "Update driver". Choose "Search automatically for drivers" or "Browse my computer for drivers" pointing to an extracted `.inf` folder. After updating, click the "Driver" tab and test the "Roll Back Driver" button.

Command / Action:

PowerShell: Get-PnpDevice -Status Error

💡

Teacher Note / Pro-Tip: "Roll Back Driver" restores the previously installed driver version if the newly installed driver causes system instability.

4

Install Application Software via Modern CLI Package Manager

Open PowerShell as Administrator. Search for and install an application using Windows Package Manager (`winget`). Observe how it automatically downloads the hash-verified installer, accepts agreements, and installs silently.

Command / Action:

winget search vlc && winget install --id VideoLAN.VLC -e

💡

Teacher Note / Pro-Tip: On Linux, equivalent commands are `sudo apt update && sudo apt install vlc`.

5

Perform Clean Uninstallation and Verify Residual Removal

Uninstall an application using Windows Settings -> "Installed Apps" or via `winget uninstall [AppID]`. Verify that the application directory in `C:\Program Files` and registry entries are cleanly removed.

Command / Action:

winget uninstall --id VideoLAN.VLC

💡

Teacher Note / Pro-Tip: Standard `.msi` installers log their installation and support automated repair and clean uninstall.

⚡

Interactive Hands-On Lab Simulator

Practice and test concepts virtually before or after performing on physical lab equipment

Live Interactive

Loading simulator...

📊

Observations & Student Lab Record

Students are required to record the following measured parameters, hardware specifications, and output status into their physical lab journals:

Hardware / Software Item	Method Used	Hardware ID / Package ID	Action Taken & Result
Realtek Ethernet NIC	Device Manager GUI	`PCI\VEN_10EC&DEV_8168`	Driver updated to latest WHQL version; status: Working normally
USB-to-Serial COM Port	Manual `.inf` driver install	`USB\VID_10C4&PID_EA60`	Missing CP210x driver installed; COM3 port assigned
7-Zip File Archiver	Winget CLI Package Manager	`7zip.7zip`	Silent installation executed in 5 seconds without adware bundled
VLC Media Player	Winget CLI Uninstaller	`VideoLAN.VLC`	Application binaries and desktop shortcuts removed cleanly

💡

Conclusions & Learning Outcome

Hardware device driver management was practiced using Device Manager. The role of Vendor (VEN) and Device (DEV) identifiers was confirmed for locating authentic OEM drivers. Application lifecycle management via both GUI installers and modern command-line package managers (winget/apt) demonstrated efficient, repeatable software administration.

❓

Oral Exam & Viva Questions with Answers

Essential questions asked by external examiners and lab evaluators (Accordion UI)

Answer:

A yellow exclamation mark indicates that the device has an error condition—most commonly that the operating system has detected the physical hardware but cannot find a compatible device driver, or the driver failed to initialize due to a resource conflict or code 43/code 28 error.