WindowsToGo Boot Test
This test validates that the USB storage can be provisioned with a Windows image and the following requirements are met:
Boot into Windows from the device.
Operates at SuperSpeed when plugged into a USB 3.0 port.
Enter and resume from S3 sleep.
Enter and resume from S4 hibernate.
Note
This is a system-specific implementation of an existing test. For more information on this test, see WindowsToGo Device Boot Test.
Test details
Associated requirements |
System.Fundamentals.USBBoot.BootFromUSB |
Platforms |
Windows 8 (x64) Windows 8 (x86) Windows 8.1 x64 Windows 8.1 x86 |
Expected run time |
~45 minutes |
Categories |
Certification Functional |
Type |
Automated |
Running the test
The hardware requirements are as follows:
The device must be USB 3.0 and certified for Windows To Go.
The device under test must be plugged into a USB 3.0 port to run this test.
The computer running the test should have no other USB storage devices attached.
The computer running the test does not have an equal amount or more system memory than the WTG certified device (for example, if the system has 32Gb of RAM, you can't use a 32Gb WTG drive).
The software requirements are as follows:
- User must copy a valid Windows Image (WIM) file to the test computer. It must include any drivers needed to use the system’s hardware.
Troubleshooting
For troubleshooting information, see Troubleshooting Device.Storage Testing.
If you cannot boot from the Windows To Go device, use the following to troubleshoot this issue:
Ensure that the Windows image does not include any 3rd party USB drivers.
Ensure that the system you are using to run this test has the latest firmware.
If boot was interrupted by an INACESSIBLE_BOOT_DEVICE stop error, the UFD likely became unresponsive after receiving a certain sequence of commands. Take a USB trace to determine what caused the UFD to become unresponsive.
If the system did not attempt to boot the Windows To Go drive, the UFD likely did not enumerate quickly enough for the system's firmware. Take a USB trace to determine what caused the system to abort its attempt to boot the UFD.
If you have taken these debugging steps and believe your device is behaving correctly, run the test again with a certified device and compare the results.
If the device cannot enter S3 sleep, your WIM image may not have the correct graphics drivers installed. Use the following steps to see what is blocking S3 sleep:
Provision a Windows To Go device with the same image you use with the test and then boot from it.
Open a command prompt, and the run the following command: powercfg a
Note which device is blocking S3 sleep, add the appropriate driver to the WIM file, and run the test again.
If the computer lost state when resuming from S3 sleep or S4 hibernate, this could mean that the computer lost power to the Windows To Go device before all of the data in its cache could be written.
If the computer resumes to the host operating system instead of the Windows To Go operating system from hibernation, the computer had a problem booting the Windows To Go device and the host computer was booted instead. Take a USB trace to determine what caused the computer to revert back to the host operating system.
If you receive Surprise Removal events during the test that were not caused from the Windows To Go device being unplugged and then plugged back in, the Windows To Go device may not be properly maintaining its link to the host operating system per the USB 3.0 specification or the Windows To Go device may not be properly saving all data to non-volatile memory when the system enters a sleep state. Take a USB trace to determine what caused the Surprise Removal events.
If the system successfully boots to the Windows To Go operating system, but appears to hang for an extended period of time, manually reboot the system. The following warning may be found in the Te.wtl log file for the 'Process Test Results' task:
Warning: Something prevented the system from entering sleep (S3) or Connected Standby. When booted from the WTG drive open a command prompt and run "powercfg -a" and note what component is listed as blocking S3 or Connected Standby. This is usually the result of missing graphics drivers. Add any missing drivers for your machine to the WIM file you're using for this test.
Note
If the logs show the test as passing after the manual reboot, it is acceptable to submit the results for certification with this warning in the logs.
More information
Parameters
| Parameter | Description |
|---|---|
WimPath |
To run this test the user must provide a full Windows Image (WIM) file. This parameter specifies the location the test should look for the WIM file. A WIM can be obtained from within Windows installation media or from an ISO file – in either case look inside the “Sources” folder for “install.wim”. The provided WIM must meet the following requirements:
Default value: C:\install.wim |
WimIndex |
WIM files can contain multiple images. If using a WIM file with multiple images, use this parameter to select the appropriate one for your test computer. Most WIM files contain only a single image so it is usually not necessary to modify this parameter. Default value: 1 |
File list
| File | Location |
|---|---|
boottest.dll |
<testbinroot>\pw_device_logo\boottest.dll |
unattend.xml |
<testbinroot>\pw_device_logo\unattend.xml |
pwrtest.exe |
<testbinroot>\pwrtest\pwrtest.exe |