FAQ for Windows Logo Kit Support Issues

In WLK 1.4, you must use the Windows Server 2008 R2 tests for all 64-bit server system testing. 64-bit systems that qualify for a Windows Server 2008 R2 logo automatically qualify for a Windows Server 2008 logo also.

On the computer you want to use as your DTM Controller, run KitSetup.exe from the WLK installation media. This will automatically install .NET Framework 2.0 and SQL Server 2005 Express Edition SP2.

No, you can leave Windows Defender enabled.

Run a complete test against each INF file in the driver package and submit a CPK file for each INF file.

Yes it is acceptable. You must re-run the job to completion.

On the DTM Client computer, restart the wttscv service. Then close and reopen DTM Studio. You should then be able to create your submission.

To avoid this problem in the future, always completely install the device under test before installing DTM Client and do not make any driver or other configuration changes after you install DTM Client.

This problem may arise if you have installed DTM Studio from the %programfiles% directory, which is not supported. You must uninstall DTM Studio and then reinstall it from the installation share on the DTM Controller.

A PRS-signed build is configured as a released build, including regular Microsoft certificates. These builds are available through official channels such as the Connect Web site. To verify that a build is PRS-signed, check that it has a standard Microsoft certificate and not a “test” certificate.

There are two ways you can do this. The first option is to search for QFE in the Submissioninfo.xml file for a submission. The second way is to go to the control panel and open “Add/Remove Programs.” Choose the option “View installed updates.” All of the WLK QFE’s will appear under the Windows Logo Kit.

Make sure that the Internet Connection Firewall (ICF) port for DTM is enabled on the DTM Client computer and the DTM Controller computer. Also, both the DTM Client computer and the DTM Controller computer must either be running IPsec or have IPsec disabled. If the DTM Client computer still does not appear, uninstall and reinstall DTM Client on the computer.

No. For debugging, you can copy the test binary files to a standalone client. Refer to the file manifest and command syntax information in DTM Help.

There is no MobilePC\TabletPCDigitizer option in WLK 1.4. For the multitouch tests, you should use the Wdk\ConfigureDigitizerInput MCU policy and select either Input->Digitizer Pen/Singletouch or Input->Digitizer Windows Touch.

When you install Windows 7 on the system under test (SUT), enable Windows Firewall. When you install DTM client on the SUT, in the Internet Connection Firewall Agreement dialog, select Yes I will allow a port to be opened.

Normally, changing the status of the machine to Reset in DTM Studio will return it to ready status. If this does not work, you must reinstall DTM Client on the machine.

Create a minidump folder to help identify the source of the error and then rerun the test. To create a minidump folder: open the System Control Panel; click Advanced system settings; under Startup and Recovery, click Settings; under Write debugging information, select Small memory dump.

You do not have the symbols for the correct build. You can work around this by supplementing your locally installed symbol package with symbols cached from an Internet symbol server. First, ensure that you have created a crash dump and have the debugging tools installed; the easiest way to do this is to run the test and let it fail. Then open a command prompt with administrator permissions and run the following command: c:\debuggers\kd -z c:\windows\memory.dmp -y srv*c:\symbols*http://msdl.microsoft.com/download/symbols. At the 0: kd> prompt, type .reload /f. This forces the debugger to load and cache all symbols for modules loaded in the dump.

These failures are expected or are acceptable. You may ignore a failing task if the parent job of the task succeeds.