This test verifies SCSI device compliance on Windows®.

Test details

Associated requirements


See the device hardware requirements.


Windows Server 2012 (x64) Windows Server 2012 R2

Expected run time

~10 minutes


Certification Functional




Running the test

Before you run the test, complete the test setup as described in the test requirements at Hard Disk Drive Testing Prerequisites and SCSI Enclosure Services (SES) Device Testing Prerequisites.

To run this test you must set the DiskDeviceObjLink parameter. This parameter represents the physical path to the test device, for example \\.\PhysicalDrive1. If testing an MPIO device, this should be the path to the Pseudo-LUN.


If a failure is observed in the SES Tes, run scsicompliance.exe /device "<Device Instance ID>" /verbosity 4 /scenario SSP /operation test /SESDisk \\.\<Drive Number> (for example, scsicompliance.exe /device "SCSI\ENCLOSURE&VEN_LSI_CORP&PROD_SAS2X36\7&7B0A3DA&0&005600" /verbosity 4 /scenario SSP /operation test /SESDisk \\.\PhysicalDrive19)

Scsicompliance.exe can be found at <controller path> \Windows Kits\8.0\Hardware Certification Kit\Tests\<arch>\NTTEST\driverstest\storage\wdk\.

The most relevant log is scsicompliance.wtl.

For troubleshooting information, see Troubleshooting Device.Storage Testing.

Errors from this test occur via issues identified in the log file and in bug checks produced through stressing the driver under test.

More information

This test will focus on measuring the SCSI device compliance on Windows. The goal is twofold - to ensure that SCSI devices supported on the Windows operating system fully and completely adhere to the SCSI specifications set forth in SPC-4 and SES-3, as well as to allow us and our partners to fully respect and comply with these standards. Maintaining compliance will lead to a stronger and more reliable system overall.


For more information about these specifications, visit the Technical Committee T10 SCSI Storage Interfaces website.


The test sends the following commands to the device:

  1. Receive Diagnostic Results: 0x00, 0X01, 0X02, 0X07, 0X0A pages.

  2. Send Diagnostic: 0x02 page.

  3. Inquiry: VPD 0x83 Page.




The device object link.

Example: \\.\PhysicalDrive1


Detail of logging. Levels are cumulative. 0 = Assertions and results. 1 = Details. 2 = CDBs , data, and sense info. 3 = Debug and detailed Mode page information. 4 = Memory usage

Default value: 4


The operation ID.

Default value: test


The scenario test name.

Default value: SSP


Command syntax

For more information about this test, please install the WDK documentation.

Command optionDescription


Runs the test.


Specifies the physical path to test device, ex: \\.\PhysicalDrive1. If testing an MPIO device this should be the path to the Pseudo-LUN.


Specifies the enclosure device to be tested.


Verbosity level

  • 0 = Shows errors and warnings in all modules plus test warnings.

  • 1 = Shows assertion details (default).

  • 2 = Shows logs of test tool framework.

  • 3 = Shows CDBs sent to device.

  • 4 = Shows data, and sense info returned.


Specifies the test scenario.


Specifies the Test or Discovery test option.


Specifies the CDB list.



The command-line switches are used when running the test manually: For command-line help for this test binary, type /h.


File list







Send comments about this topic to Microsoft