Windows ADK Release Notes

Applies To: Windows 8, Windows 8.1, Windows Server 2012

This document summarizes known issues, and workarounds for this release of the Windows Assessment and Deployment Kit (Windows ADK).

In this topic

• New Features in Windows ADK for Windows 8.1 Update

• Windows ADK Installation Known Issues

• Windows Deployment Issues

• Windows PE Known Issues

• Windows Assessment Known Issues

• Help and Support Customization Known Issues

• Application Compatibility Toolkit (ACT) Known Issues

• User State Migration Tool (USMT) Known Issues

• Volume Activation Management Tool (VAMT) Known Issues

New Features in Windows ADK for Windows 8.1 Update

For a list of new features included in the Windows ADK for Windows 8.1 Update, see What's New in the Windows ADK for Windows 8.1.

Note that the Windows ADK installer does not mention Windows 8.1 Update specifically. To determine what version of the Windows ADK you have installed, go to Control Panel > Programs > Programs and Features. The versions are:

• Version 8.100.25984 is for the Windows ADK for Windows 8.1 RTM

• Version 8.100.26629 is for the Windows ADK for Windows 8.1 Update

Version increments between 25984 and 26629 are updated versions of the RTM release. Version increments higher than 26629 are for the Windows 8.1 Update.

Whenever an item in the Windows ADK is updated, the entire kit is rebuilt and version numbers for all features in the kit are updated. Even though the version number has been updated, there might not be any changes to a feature.

Windows ADK Installation Known Issues

• [August 2012] Some antivirus and anti-malware software and Windows UAC may identify Windows ADK binaries as unverified or untrusted

  Some antivirus or anti-malware software may identify the Windows ADK kit binaries as unverified or untrusted, which might hinder automated execution of ADK binaries, for example in automated labs.

  If you encounter this issue, use the signtool from the Windows Software Development Kit (SDK) (legacy) to import the catalogs into the catalog store. You can automate this by using a script. Run the command signtool catdb * from the folder C:\Program Files (x86)\Windows Kits\8.0\Catalogs.

  Depending on your antivirus software, you might need additional workarounds:

  • You can add the Windows ADK binaries to the antivirus software safe list. For example, you can add this as a configuration step when deploying an image for testing.

  • The antivirus vendor can add the kit binaries to their software’s safe list.

  • An end-user can manually add the flagged binary to the antivirus safe list at runtime.

  In some cases, the catalog signed kit binaries shows as "unverified publisher" by Windows UAC. To work around this, run the ADK binaries from an elevated command prompt. Or, in manual scenarios, click Yes on the UAC prompt to allow the binary to run. The automated assessment execution tool (Windows Assessment Services) in the ADK already runs in an elevated environment.

• [August 2012] Installing the Windows ADK to a computer that already has the Windows OPK or Windows AIK is not supported

  If you already have a computer with a previous version of the Windows OEM Preinstallation Kit or Windows Automated Installation Kit (AIK), installing the Windows ADK is not supported. If you need to access tools available with the Windows OPK or Windows AIK, copy those tools to the Windows ADK computer. If you do install the Windows ADK Deployment Tools to a computer with the Windows OPK or Windows AIK, only use the Deployment Tools Command Prompt from the Windows ADK.

• [August 2012] Repairing shared features after a major upgrade

  If you install more than one Windows kit with a shared feature, and then remove one of the kits from your computer, that shared feature might not work when using the kit that is still installed. This can happen during a significant update, such as a Service Pack for one or more of the kits. For example, if you install the Hardware Certification Kit with a major update with the Windows Performance Toolkit and the Assessment and Deployment Kit with the Windows Performance Toolkit, and then remove the Hardware Certification Kit, the Windows Performance Toolkit might not work when used with the tools in the Assessment and Deployment Kit.

  To work around this issue, repair the installation of the installed kits.

• [August 2012] Upgrades of the Windows ADK from previous releases are not supported

  Do not upgrade the Windows ADK. You must uninstall the earlier version before you install the latest release.

Windows Deployment Issues

• [May 2014] In audit mode, the PC may hang while installing video drivers on PCs with multiple video cards. To resolve this issue:

  1. Remove one of the video cards before entering OOBE.

  2. Once OOBE has completed, shut down the PC and replace the video card removed in step one.

  3. Download the latest video drivers for these cards through Windows Update or from the manufacturers' website.

• [September 2013] The power configuration setting: "Display dimming" is no longer configurable.

  Mobile PCs will dim the display 15 seconds before the Display timeout.

• [September 2013] Do not use Windows System Image Manager (Windows SIM) on a Windows 8 technician PC to open Windows 8.1 install.wim file. Catalog creation might fail. Use a Windows 8.1 technician PC to open Windows 8.1 install.wim.

• [September 2013] Using the Windows 8 version of DISM or the Windows 7 version of DISM to service Windows 8.1 is not a supported scenario.

  Instead, you can do one of the following:

  • If you are using a Windows 8 host computer or a Windows 7 host computer, install the next version of the full ADK to your computer, or

  • In Windows PE, you will need to copy the next version of DISM to the host computer by following the steps detailed in How to Copy DISM to Another Computer. Before performing step 3, it is recommended that you copy the set of binaries located in C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\<architecture>\Forwarders\ to the DISM folder on the host computer.

  The architecture of the tools must match the native architecture of the operating system on the host computer.

• [June 2013] Do not install Windows Store apps from the store with a Microsoft account when customizing your Windows image.

  Use DISM to provision or update Windows Store apps to the installation before running Sysprep. Sysprep might fail when you use a Microsoft account to download or update apps from the store.

• [July 2013] Downloading apps from the store when customizing Windows images

  Do not install Windows Store apps from the store with a Microsoft account when customizing your Windows image. Use DISM to provision or update Windows Store apps to the installation before running Sysprep. Sysprep might fail when you use a Microsoft account to download or update apps from the store.

• [June 2013] Windows 8.1 maintenance tasks might cause Sysprep to fail

  Windows 8.1 includes a new maintenance task that runs one hour after first logon and when the PC has been idle for 15 minutes. This maintenance task cleans up Windows Store apps that have been provisioned in the installation. This includes both preinstalled Windows Store apps, as well as any apps that an OEM or IT Pro added to the image using DISM. After this maintenance task runs, Sysprep /generalize actions will fail. The following shows the error code in the Setuperr.log file:

  2013-06-12 05:41:29, Error                 SYSPRP Could not re-arm region selection, some files and registry keys are no longer recoverable.
  2013-06-12 05:41:29, Error                 SYSPRP Re-arm region selection failed with hr = 0x8000ffff.
  2013-06-12 05:41:29, Error                 SYSPRP Failed to re-arm region selection: 0x8000ffff.
  

  If this error occurs, you must recreate the image.

  To work around this issue, use Audit Mode to perform customizations to your image; the Windows 8.1 maintenance task does not run in Audit Mode.

  Optionally, you can disable the maintenance task using the following command:

  Schtasks.exe /change /disable /tn "\Microsoft\Windows\AppxDeploymentClient\Pre-staged app cleanup"

  Make sure to disable the maintenance task soon after first logon, before it has a chance to run. Running Sysprep /generalize will re-enable the maintenance task. Do not delete the maintenance task, as this will cause Sysprep to fail.

• [August 2012] Secure Boot error message: "BitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted."

  When attempting to call Set-SecureBootUEFI in PowerShell within Windows PE, you may receive the following error message: "Set-SecureBootUEFI : BitLocker Drive Encryption cannot be used because critical BitLocker system files are missing or corrupted. Use Windows Startup Repair to restore these files to your computer."

  Ignore this error. This error message is a known problem, and does not affect your ability to modify the UEFI Secure Boot configuration.

• [August 2012] The Unattend setting DoNotCleanTaskbar is deprecated

  The Microsoft-Windows-Shell-Setup\DoNotCleanTaskbar setting is deprecated in Windows 8 and Windows Server® 2012. We do not recommend adding deskbands to the desktop taskbar, because they may not work correctly.

• [August 2012] The values for setting the Desktop background color have changed

  The Unattend setting: Microsoft-Windows-Shell-Setup\Themes\WindowColor affects the color of window borders and taskbar on the desktop. The new predefined color values are: Automatic, and Color 1 through Color 15. The default value is Automatic.

• [August 2012] Specifying a ComputerName

  The ComputerName setting cannot contain any of the following characters: { | } ~ [ \ ] ^ ' : ; < = > ? & @ ! " # $ % ^ ` ( ) + / , or contain any spaces. Computer names that cannot be validated through the DnsValidateName function cannot be used. For more information, see the DnsValidateName function.

• [August 2012] Error unmounting images from multiple VHDs on a Windows 7 host

  Multiple Windows images mounted from Virtual Hard Disk (VHD) files may have the same signature. When you unmount and commit changes to multiple VHDs with the same signature simultaneously, the operation will fail on a host computer that is not running Windows 8. Use a Windows 8 host operating system to service the images or unmount the images one at a time to avoid a conflict.

• [August 2012] Installing EN-US and EN-GB language packs

  Adding both EN-US and EN-GB language packs to a single Windows image is not recommended. Both language packs are presented to the end user as "English" and might cause customer confusion. Also, this might prevent Windows from removing one of the language packs if a user does not select it as a default.

• [August 2012] Creating a task during audit mode

  Tasks are not allowed to run on triggers when in audit mode. To run a task, you must use the IRegisteredTask::RunEx method with TASK_RUN_IGNORE_CONSTRAINTS. For more information, see https://msdn.microsoft.com/en-us/library/windows/desktop/aa380768(v=vs.85).aspx.

• [August 2012] To create a bootable ISO file that does not prompt users to "Press any key"

  By default, bootable ISO files prompt users to press any key to boot from CD. Makewinpemedia.cmd does not support creating media that does not display the "Press any key to boot from CD" message. You can disable the "Press any key" message by using OSCDIMG to create the ISO file.

  On UEFI systems, use OSCDIMG with the -b option to create an ISO file that uses the Efisys_noprompt.bin boot sector file. This file is included with the Deployment Tools feature in the ADK. For example: -bC:\Efisys_noprompt.bin.

• [August 2012] The BCDBoot command-line option /s should not be used in typical deployment scenarios

  Use the /s option of bcdboot to specify a system partition when you are configuring a drive that will be booted on another computer, such as a USB flash drive or a secondary hard drive.

  UEFI:

  • BCDBoot copies the boot files to either the EFI system partition, or the partition specified by the /s option.

  • BCDBoot creates the BCD store in the same partition.

  • By default, BCDboot creates a Windows Boot Manager entry in the NVRAM on the firmware to identify the boot files on the system partition. If the /s option is used, then this entry is not created. Instead, BCDboot relies on the default firmware settings to identify the boot files on the system partition. According to the UEFI 2.3.1 spec, the default firmware settings should open the file: \efi\boot\bootx64.efi in the EFI System Partition (ESP).

  BIOS

  • BCDBoot copies the boot files to either the active partition on the primary hard drive, or the partition specified by the /s option.

  • BCDBoot creates the BCD store in the same partition.

  The following example copies BCD files from the C:\Windows folder to a system partition on a secondary hard drive that will be booted on another computer. The system partition on the secondary drive is assigned the volume letter S:

  bcdboot C:\Windows /s S:
  

  The following example creates boot entries on a USB flash drive with the volume letter F, including boot files to support a UEFI-based or a BIOS-based computer:

  bcdboot C:\Windows /s F: /f ALL
  

• [August 2012] OEM Activation Tool Available in the Windows ADK

  The OEM Activation tool, OA3Tool.exe, is now included in the Windows ADK. This tool is intended for OEMs who are implementing OEM Activation. For additional information, see https://go.microsoft.com/fwlink/?LinkID=209568.

• [August 2012] Windows unable to parse or process answer file

  Installing from an answer file returns an error: "Windows could not parse or process unattend answer file [D:\Windows\Panther\unattend.xml] for pass [specialize].  The answer file is invalid."

  This issue might occur if the ComputerName setting is longer than 15 characters. Reduce the number of characters used in the ComputerName setting.

• [August 2012] System Image Manager Answer File Validation

  When Windows SIM validates an answer file it verifies that the settings exist in the Windows image. Windows SIM also validates that the setting values matches the Type of the setting in the Windows image. For example, string values are not allowed in a setting of an integer type. The actual value of the setting is not validated. For example, a product key is not validated that it is a correct product key. Windows SIM only validates that the product key value is a string type.

• [August 2012] Provision app package (.appx) with a custom data file

  When you use the /Add-ProvisionedAppxPackage DISM command with the /CustomDataPath option, the custom file will be renamed to Custom.data when it is added to the image. The documentation uses an incorrect file extension. The correct file extension is .data.

• [August 2012] Sideloading apps on Windows 8

  Sideloading is supported on the following editions when you activate a sideloading product key:

  • Windows 8 Pro

  • Windows 8 Enterprise*

  * The sideloading product key is not required with Windows 8 Enterprise when the computer is joined to an active directory domain.

To sideload line-of-business apps on Windows Server 2012, the computer must be joined to an active directory domain.  
  
For more information, see [How to Add and Remove Apps](https://go.microsoft.com/fwlink/?linkid=231020).  
  

• [September 2012] Edition-Servicing Error Messages on Images with Language Packs

  When you use edition-servicing commands on a target image that has a partially localized language pack installed, the wrong status messages are displayed on the command line. Some status messages will appear as error messages. The correct messages are displayed in the log files, but not on the command line.

  Use the /English option to display the right status messages on the command line. For example,

  Dism /online /get-currentedition /english
  

  See Windows Edition-Servicing Command-Line Options for more information on edition-servicing commands.

  See Available Language Packs for more information on which language packs are partially localized.

• [September 2012] Changing the default program files location is not supported for the Windows® Store or Windows Store apps.

  The Unattend setting: Microsoft-Windows-Shell-Setup\FolderLocations\ProgramData is only for use in test environments. Changing this setting is not supported for Windows® Store or Windows Store apps.

• [September 2012] Changes in Out-Of-Box (OOBE) Experience

  Oobe.cmd and Setupcomplete.cmd are disabled if an OEM product key is used. This is to ensure that end-users reach Start as quickly as possible. If you have any tools or services that use this infrastructure, these must be changed to tasks that occur after the OOBE.

• [September 2012] Catalog files are no longer included with Windows

  Catalog files (.clg) are no longer included in the /sources folder. You must create catalog files by using Windows System Image Manager (SIM).

• [September 2012] Windows 8 and SkipRearm

  You no longer have to use the SkipRearm setting to reset the Windows Product Activation clock when you run Sysprep. In Windows 8, the SkipRearm setting is used to specify the Windows licensing state. If you specify a product key, Windows is automatically activated, and you can run the Sysprep command an unlimited number of times.

• Windows 8 ADK Documentation Download

  The online documentation reflects the latest version of the Windows ADK. The previous versions of the Windows ADK documentation is available for download as a .chm:

  Windows 8 ADK online documentation download

  Note that if you receive the error message Navigation to the webpage was canceled displayed in the .chm pane, or the pane is empty, use the following workaround.

  1. Right-click the .chm file, and then click Properties.

  2. Click Unblock.

  3. Double-click the .chm file to open the Help file.

  For more information, see the following Microsoft Knowledge-Base article: https://support.microsoft.com/kb/902225/

Windows PE Known Issues

• [September 2013] Running Windows PE on computers with large amounts of memory

  Windows PE is not supported on x86 PCs with more than 64 gigabytes (GB) of RAM, or x64 PCs with more than 4 terabytes (TB) of RAM. On PCs with larger amounts of memory, Windows PE might experience unexpected behavior.

Windows Assessment Known Issues

• [April 2014] Error message about Event Trace Log could not be found

  When you click on Memory Trace, you might receive an error: The file <filename>.etl could not be found. To work around this issue, copy the the results/<filename>.etl to each results/<num_AssessmentName> subfolder.

  Where <filename>.etl is the name of the ETL file. For example Boot_MemoryFp_1.etl. <num_AssessmentName> is the name of the directory that contains the results from the Assessment job. For example, 001_MemoryFootprintAsmt.

• [October 2013] Connected Standby Assessment results and workload

  • In some cases, the system may enter Connected Standby while preparing the assessment to run. In these cases, a Sleep Study iteration corresponding to this Connected Standby session may be displayed in the assessment results. Because this data was collected before the assessment workload began, this Sleep Study iteration can be ignored.

  • In some cases, the system may enter Connected Standby while preparing the assessment to run. This can be caused by the system becoming idle during these preparations (charging the battery, running maintenance tasks, etc.), which will cause the display to turn off and in some cases can enter Connected Standby. Turn the display back on to continue running the assessment.

• [October 2013] Some assessments cannot be analyzed through Windows Assessment Services on Windows Server 2008 R2

  To fix this, install the KB2533623 update. For more information, see https://support.microsoft.com/kb/2533623.

  The assessments affected include:

  • Boot Performance (Fast Startup)

  • Energy Efficiency Assessments

  • Internet Explorer Security Software Impact

  • Internet Explorer Startup Performance

• [September 2013] The Local Video Playback assessment is not supported on PCs that have been upgraded from Windows® 7.

  To run the assessment and test video performance, use a PC that has a clean installation of Windows 8.1 or a PC that has a clean installation of Windows 8 and has been upgraded to Windows 8.1.

• [September 2012] The First Logon Commands section within the First Boot Performance assessment may not show the complete list of First Logon Commands or may include Run commands.

  To measure the complete set of First Logon Commands, during OOBE type SHIFT+F10 and enter the following command.

  wevtutil sl Microsoft-Windows-Shell-Core/Diagnostic /ms:62914560 /e:true /q:true /rt:false
  

  After you reach the Start screen, open the command prompt and run the command:

  wevtutil sl Microsoft-Windows-Shell-Core/Diagnostic /ms:62914560 /e:false /q:true /rt:false
  

  Open Event Viewer and under View, select Show Analytic and Debug Logs…. Then, navigate to the Microsoft-Windows-Shell-Core/Diagnostic log located under the Applications and Services Logs. Filter the log for only 9705-9706 events. Note the time periods (9705 is the start interval and 9706 is the stop interval) for the events where the KeyName is Software\Microsoft\Windows\CurrentVersion\RunOnce. This sum of the interval(s) is the duration of the First Logon Command period. Next, filter the log for only 9707-9708 events. Look at the events that occur between the time interval(s) previously noted. The 9707 events mark the time when a First Logon Command was launched and the 9708 events mark the time when it stopped. The specific command that was run can be found within the details pane under Command.

• [August 2012] Fast Startup assessment crashes the AXE platform

  In some cases when the system reboots after running the Fast Startup assessment, you are prompted with a toast. Clicking on the toast might cause the AXE platform to crash. If the AXE platform crashes, reboot the system and re-run the assessment. If you are prompted with a toast after the system reboots, do not click it.

• [August 2012] Configuring Symbols on Windows Assessment Services

  Setting up a symbol server for Windows Assessment Services requires these additional tasks:

  1. Before deploying or performing an inventory of your clients, you must configure the symbol path in the file: \\<server>\relax\scripts\testmachine\setenvironment.cmd.

  2. After you deploy and inventory your clients, you must set the correct symbol path in c:\relax\setenvironment.cmd.

• [August 2012] Windows Assessment Services Job Settings

  The Job settings that are available in the Windows Assessment Services - Client for Failure Behavior, are Continue, Hold, and Stop. In some instances, the documentation refers to these settings as Continue, Hold, and Abort.

• [August 2012] File Organization Assessment

  When running the File Organization assessment with the Scripting Option in Windows 8, some non-English systems may fail or not be able to run the assessment completely. There is no known workaround.

• [August 2012] Memory Footprint assessment system requirements

  The Memory Footprint assessment topic in the Windows ADK documentation lists both Windows 7 and Windows 8 as supported operating systems. However, this assessment is not supported on Windows 7. It only runs on Windows 8.

• [August 2012] Using the ResultsUtil /ImportResults command

  Using the ResultsUtil /ImportResults command to import results files into a database takes time. Due to the heavy use of the database tables during import, we recommend importing during non-peak business hours.

• [August 2012] Data is not captured by default for the "Time after Start for app animations" metric in the First Boot Performance assessment

  To enable data to be captured for this metric, during OOBE type SHIFT+F10 and enter the command.

  wevtutil sl Microsoft-Windows-TwinUI/Diagnostic /ms:10485760 /e:true /q:true /rt:false

  After you reach the Start screen, wait five minutes without using the PC while you are waiting for the tiles to animate. Then open the command prompt and run the command:

  wevtutil sl Microsoft-Windows-TwinUI/Diagnostic /ms:10485760 /e:false /q:true /rt:false

• [August 2012] The First Boot Performance assessment cannot be run on PCs that have completed OOBE more than once without running specialize

  If you boot Windows, complete OOBE, and then run sysprep /oobe again without running the /generalize command, the First Boot Performance might experience unexpected behavior. This is not a supported scenario.

  To re-measure the first startup experience, the image must be generalized to complete the specialize configuration pass before booting to OOBE.

• [August 2012] Inflated numbers may be seen within the First Boot Performance assessment after multiple runs through Setup

  To avoid this issue, delete or rename C:\Windows\Panther\setup.etl before running sysprep /generalize.

• [August 2012] Misleading error message in Windows Assessment Services: Computer stopped responding

  You might receive this error message if an application crashes while the assessment was running:

  "The computer stopped responding while the job was running. For more information, see the %systemdrive%\relax\guid\dumps folder."

  The dumps folder contains the application crash information and by default is stored on the test computer.

• [August 2012] Windows Assessment Services Status doesn't refresh

  When monitoring a job, you might notice that the status hasn't changed even though the required actions have been completed, or the warning icon is still visible after the status message is cleared.

  To work around this, refresh the computer inventory, or restart the Windows Assessment Services - Client.

• [August 2012] Streaming Media assessment sometimes fails because Internet Explorer is unable to autoplay

  There is a known issue with Internet Explorer which can occasionally cause Internet Explorer not to autoplay. This results in the Streaming Media assessment failing to run. In most cases, running the assessment again resolves the issue. While the assessment is running, do not interact with your computer and ensure that the computer is not locked during the assessment.

• [August 2012] Internet Explorer Browsing Performance Assessment only works with the desktop browser

  The Internet Explorer Browsing Performance Assessment currently only works with Internet Explorer for the desktop.

Help and Support Customization Known Issues

• [August 2012] Shortcut links cannot contain apostrophes

  Shortcut links are authored links in Help and Support content that point to resources installed on the computer. These links enable customers to open documents and support applications so that they can easily troubleshoot their computer-related problems. Shortcut links cannot point to paths that contain an apostrophe ('). For example, C:\OEM\Fabrikam's Docs\Docs\ is an invalid path, while C:\OEM\Fabrikam Documents\Docs\ is valid.

• [August 2012] Help content must be fully valid XHTML

  For customized pages to be properly loaded in Help and Support, the help content must be valid XHTML:

  • HTML tags must be self-closed or have a closing tag.

  • The opening tag must have the same name (case-sensitive) as the end tag. For example, <body></body> is valid, while <BODY></body> and <body></Body> is not.

  If the content is not valid XHTML, executable shortcut links in the topics will fail to load.

Application Compatibility Toolkit (ACT) Known Issues

Be aware of the following issues before using this release of ACT.

• [August 2012] Installing Inventory Collection Packages on computers without Unicode fonts

  On computers running Windows XP and Windows Server 2003 where Unicode fonts are not installed, the installer screen for an inventory collector package shows rectangles instead of text. The text that would normally appear is:

  Please wait while Windows configures Inventory Collection Package

  The lack of text does not interfere with the installer. You can install the inventory collector package successfully without Unicode support.

• [August 2012] Inventory collector packages do not run on Windows 2000

  There is no known workaround.

User State Migration Tool (USMT) Known Issues

• [August 2012] Incorrect manifest used in Windows 7 to Windows 7 offline migrations

  During an offline Windows 7 to Windows 7 migration using the /TargetWindows7 switch, USMT uses the Windows 8 manifests rather than the Windows 7 manifests. This might result in migrating incorrect operating system settings.

  Use one of the following options to mitigate this issue:

  • Use the previous version of USMT for the migration. You can download the previous version, USMT 4.0, as part of the Windows Automated Installation Kit available here.

  • Use the Windows 7 version of Windows PE in conjunction with USMT 5.0 rather than the Windows 8 version of Windows PE.

  • Move the DLManifests and ReplacementManifests folders outside of the User State Migration Tool\<arch> directory and rename the DLManifests7 and ReplacementManifests7 folders to DLManifests and ReplacementManifests, respectively.

Volume Activation Management Tool (VAMT) Known Issues

• [August 2012] Initialize a database with Windows PowerShell.

  After you run the Initialize-VamtData cmdlet on a database, you must connect to that database using the VAMT UI before the database is fully initialized and ready to use.

Windows ADK Fixes

The following issues have been fixed in the current release of Windows Assessment and Deployment Kit (Windows ADK):

• Fixed an issue with USMT where during a hardlink migration, error codes 26 and 72 occur when the migration fails with not enough storage space.

• Fixed an issue with WIMGAPI where in a small number of cases, image capture fails with not enough storage space.

• Fixed an issue with the Connected Standby Energy Efficiency assessment where the assessment fails to complete analysis on Windows RT devices.

• Fixed an issue in the Internet Explorer Startup Performance assessment where the startup duration was incorrectly reported on Windows 8.1 devices.

• Fixed an issue where assessment results would not load when two or more recorded processes have the same name but different casing.