Unclassified Signature Program
Some devices have no applicable category in the current Windows Logo Program requirements. For these devices, you can use the Unclassified Program to submit devices and drivers for signature.
The Unclassified Program is designed to enhance system security and the overall customer experience by signing drivers that:
| • | Pass the basic Windows driver reliability and stability tests. |
| • | Meet all of the Device Fundamental requirements. |
| • | Are submitted by partners that are registered with the Windows Logo Program. |
The device or the driver must meet the Device Fundamental requirements and will be subjected to a core set of driver tests to validate stability under Windows Vista. These driver components must not cause crashes or leak resources, including but not limited to the following:
| • | Memory |
| • | GDI / user objects |
| • | Kernel objects (files, mutexes, semaphores, device handles, and so on) |
| • | Critical sections |
| • | Disk space |
| • | Printer handles |
The Unclassified Program does not validate device and driver functionality. Therefore, devices and drivers that are submitted for driver signature under the Unclassified Program are not eligible to use either the Basic or Premium logo.
You can use the Unclassified Program to obtain a signature for a driver even if a Basic or Premium logo program is defined for the device or driver category. However, such signed drivers and devices will not qualify to use the logo. Neither can you use such drivers and devices in a system that you are submitting for a Premium logo.
For further details about the Unclassified Program, refer to Policy-0021 on the LogoPoint tool. The Device Fundamental requirements are also available on LogoPoint.
The Driver Reliability tests for the Unclassified Program, which are defined in the Windows Logo Kit (WLK), include the following:
| • | Plug and Play Driver Test |
| • | Device Path Exerciser |
| • | INF Test |
| • | Disable Enable with IO Test |
| • | Sleep Stress with IO Test |
| • | Common Scenario with IO Test |
Note: The Static Driver Verifier Test and PREfast for Drivers Test are not required at this time, but we strongly recommend that you run these tests before submitting your driver for signature. Any issues that these tests flag must be understood and either explained or resolved.
The Microsoft static analysis tools - PREfast for Drivers (PFD) and Static Driver Verifier (SDV) - are highly effective for improving driver reliability because they identify coding issues that would otherwise be difficult to find. For Unclassified Signature submission packages that contain a kernel-mode driver or service, you must run PFD on source code and include the PFD summary results file with the submission package. To receive a signature for the driver, the PFD summary results file that you submit is not required to be error free. PFD can produce false errors or warnings, so you must fix only those errors and warnings that are identified as true problems in the driver code.
The WLK Test documentation describes how to use the PREfast for Drivers Test to import PFD summary results that might have been created at a remote development organization. This allows developers to run PFD on their driver source code and then pass the summary results file to a separate organization that uses WLK to run the Logo or Unclassified Program tests.
SDV is not a requirement, but we highly encourage its use if your submission contains a kernel-mode driver or service. In the future, we anticipate that SDV will become a logo requirement for all kernel-mode driver or service components.
