Windows Client: WSD Device Icons Displaying Incorrectly? Here's Why.

Table of Contents

Web Services for Devices (WSD) provides a standard way for devices like printers, scanners, and cameras to be discovered and used over an IP-based network. Introduced and heavily integrated into Windows Vista and Windows 7, WSD aimed to simplify device installation and management by leveraging web protocols for discovery and communication, often replacing older methods like LPR or proprietary network protocols. When a WSD-compliant device is connected to the network, Windows can automatically discover it and often install basic functionality without requiring a separate driver CD.

The integration of WSD in Windows 7 was part of a broader effort to create a more cohesive device experience, prominently featuring the “Devices and Printers” control panel and the innovative “Device Stage” feature. Device Stage was designed to provide a rich, graphical interface for managing connected devices, offering access to device-specific tasks, information, status updates, and even online services directly from the desktop. For Device Stage to function correctly and display the appropriate information and iconography, Windows relies on device metadata packages, typically downloaded from Microsoft or directly from device manufacturers.

Symptoms: Device Icons Displaying Incorrectly¶

A specific issue encountered by some users in Windows 7 involved WSD devices, particularly network printers. Instead of appearing with the expected printer icon under the “Printers and Faxes” category in the “Devices and Printers” window, the WSD device might show an incorrect icon, such as a generic device icon or even an icon suggesting a different device class like a server or computer. Furthermore, these devices might be listed under the general “Devices” category rather than their correct, function-specific category like “Printers and Faxes” or “Cameras”.

This miscategorization and incorrect visual representation could lead to confusion for users attempting to manage their devices. Locating the printer to set it as default, check its status, or access advanced printing preferences becomes less intuitive when it’s not listed where expected or doesn’t look like a printer. While basic functionality might still work (e.g., printing from an application that lists available printers), the user experience within the Devices and Printers interface is degraded. The visual discrepancy suggests a problem with how Windows is identifying and presenting the device, despite the underlying WSD communication potentially functioning correctly.

Cause: Faulty Device Stage Metadata Package¶

Investigating this issue traced the root cause back to a specific, incorrect Device Stage metadata package. Microsoft periodically releases updates to device metadata packages to ensure accurate identification and display of a wide range of devices within Windows. These packages contain information such as the device type, its capabilities, links to device-specific software or support pages, and crucially, the correct iconography and categorization information used by Device Stage and the Devices and Printers interface.

During a particular period, specifically between June 8 and June 22, 2010, an erroneous metadata package was released by Microsoft and made available for download. Systems running Windows 7 that connected to the internet during this timeframe were likely to download this incorrect package as part of the standard metadata update process. Once downloaded and cached on the user’s system, this faulty package would override the correct information for certain WSD devices, leading to the display of incorrect icons and categorization within the Devices and Printers control panel. This highlights the critical dependency of features like Device Stage on accurate and up-to-date metadata.

Resolution: Clearing the Device Stage Metadata Store¶

Fortunately, the resolution for this issue is relatively straightforward and involves clearing the locally cached Device Stage metadata. When Windows needs device metadata, it first checks its local cache. If the required metadata isn’t found, or is outdated, Windows attempts to download the latest version from Microsoft’s online services. By deleting the contents of the local cache, we force Windows to discard the faulty package and redownload the correct one during the next check.

Follow these steps to clear the Device Stage Metadata Store:

1. Open an elevated Command Prompt: Click the Start button, type cmd in the search box. Right-click on “Command Prompt” in the search results and select “Run as administrator”. User Account Control (UAC) may prompt you to confirm; click “Yes”. This is necessary because the metadata cache is located in a system-protected area within the user profile.
2. Execute the deletion command: In the elevated Command Prompt window, carefully type the following command exactly as shown:
   

   del /s "%systemdrive%\users\%username%\AppData\Local\Microsoft\Device Metadata\*\*"
   

   
   Then press the Enter key.
   • del: The command to delete files.
   • /s: This switch tells the del command to delete files in all subdirectories within the specified path.
   • "%systemdrive%\users\%username%\AppData\Local\Microsoft\Device Metadata\*\*": This is the path to the Device Stage metadata cache.
     • %systemdrive%: A system variable representing the drive where Windows is installed (usually C:).
     • %username%: A system variable representing the currently logged-in user’s profile folder name.
     • AppData\Local: This is a hidden folder within the user profile where application-specific data is stored locally.
     • Microsoft\Device Metadata: The specific folder used by Windows to cache device metadata packages.
     • *\*: This wildcard pattern targets all files (*) within all subdirectories (*) inside the Device Metadata folder.
3. Confirm deletion: The command prompt will likely ask for confirmation before deleting the files, displaying a prompt similar to Are you sure (Y/N)?. Type Y and press Enter.
4. Confirm additional deletions (if prompted): Depending on how many metadata packages are cached on your system, you might be prompted multiple times to confirm deletions within different subfolders. For each such prompt, type Y and press Enter. Continue until the command finishes executing.

Once the command completes, the contents of the Device Stage Metadata cache will be cleared. The next time you open “Devices and Printers” or connect/reconnect a WSD device, Windows 7 will automatically detect the absence of the required metadata in the local cache and initiate a redownload process from Microsoft’s servers. This process will pull down the corrected metadata packages (released after June 22, 2010), which contain the accurate information for identifying and displaying WSD devices. After the redownload is complete and the cache is repopulated, your WSD devices should appear with the correct icons and under the appropriate categories in “Devices and Printers”.

Understanding Device Stage Metadata¶

Device Stage metadata packages are essentially small XML files bundled with supporting assets like images and icons. These packages act as a bridge between the generic device class detected by Windows (like a USB device or a network endpoint) and the rich, branded experience intended by the manufacturer or provided by Microsoft. The metadata specifies details like:

• Device Name and Description: User-friendly names.
• Device Category: Printer, Scanner, Camera, Phone, Portable Device, etc.
• Icons and Imagery: High-resolution icons for different views.
• Tasks and Actions: Links to print preferences, scan utilities, synchronization software, online registration, support pages.
• Status Information: How to retrieve ink levels for a printer, battery status for a phone, etc.

The issue described in this article specifically relates to incorrect information within the metadata package affecting the categorization and icon displayed in the standard Windows shell, not necessarily impacting the core driver functionality.

Broader Context and Troubleshooting Layers¶

While the specific bug caused by the June 2010 package is historical and primarily affects Windows 7 systems from that era, understanding this scenario provides insight into how Windows manages device information. Troubleshooting device display issues in Windows can involve several layers:

1. Device Driver: This is the fundamental software enabling communication between Windows and the hardware. Driver issues often lead to the device not functioning at all, or appearing with a warning icon in Device Manager.
2. Plug and Play (PnP): Windows’ mechanism for discovering and configuring hardware. PnP issues can prevent a device from being detected correctly.
3. Icon Cache: Windows maintains a cache of icons used throughout the system. Sometimes, this cache can become corrupted, leading to incorrect icons for various items, not just devices. Clearing the general icon cache is a different procedure than clearing the Device Stage metadata cache, although both address icon display problems.
4. Device Stage Metadata: As discussed, this affects the rich presentation and categorization within “Devices and Printers”. Issues here typically result in the device being detected and functional, but displayed incorrectly in the user interface.
5. Network Connectivity/Discovery: For network devices like WSD printers, network issues can prevent the device from being discovered in the first place. Ensuring the device and the PC are on the same network subnet and that network discovery is enabled is crucial.

The specific resolution provided here targets the Device Stage Metadata layer, as the cause was identified as corruption or incorrect information at this level due to a faulty package release.

Why This Was Specific¶

This issue was particular to:

• Windows 7: Device Stage was a prominent feature in Windows 7 and Vista. Earlier OS versions didn’t rely on this metadata system in the same way. Later OS versions might have different mechanisms or cache locations.
• WSD Devices: The bug was tied to how WSD devices were processed by Device Stage and its reliance on network-downloaded metadata.
• A Specific Timeframe: The window between June 8 and June 22, 2010, was when the incorrect package was available. Systems online during this period were susceptible. Microsoft would have quickly identified and corrected the faulty package shortly thereafter, meaning systems downloading metadata after this date would get the correct version.

Although Windows 7 is now past its end-of-support date, this case study serves as a useful example of how seemingly minor data corruption (in a metadata package) can impact the user experience and how clearing local caches can often resolve such issues by forcing a redownload of corrected information. The steps outlined for clearing the Device Stage metadata cache might also be useful in other rare scenarios where this cache becomes corrupted for different reasons, leading to display anomalies for WSD or other devices that utilize Device Stage.

Summary of Resolution Steps:¶

To recap, if you encountered this specific issue with WSD device icons in Windows 7:

1. Open Command Prompt as Administrator.
2. Run the command del /s "%systemdrive%\users\%username%\AppData\Local\Microsoft\Device Metadata\*\*"
3. Type Y and press Enter when prompted to confirm deletion.
4. Repeat typing Y and Enter for any subsequent confirmation prompts.
5. Close the Command Prompt.

After these steps, Windows will rebuild the metadata cache with correct information, resolving the incorrect icon display.

Data Collection (Placeholder)¶

Note: The original article mentioned “Data collection” as a section header, but contained no actual content. This is a common practice in knowledge base articles to indicate that diagnostic data *could be collected if the resolution steps were insufficient or to help Microsoft understand the scope of the issue. For the purpose of this rewritten article, we acknowledge its presence in the original structure but omit the section as no specific data collection steps were provided or are necessary for the resolution.*

---

Did clearing the Device Stage Metadata Store resolve the incorrect icon display for your WSD devices in Windows 7? Or have you encountered similar device display issues in other Windows versions? Share your experiences and troubleshooting tips in the comments below! Your insights can help others facing similar problems.