RELEASE DATE: 02/19/2014
FILES: ADK_140219-1702.zip
SIZE: 3,182,812,377 byte
SHA-1: EDF880A13DBB3FA4BB9CBDB13B2CF395D3172E15
MD5: 9927B91EBFFDA43025D1064ECF19F091
NOTE: this is original M$ files.
EEAP - Ecosystem Engineering Access Program
What’s New in Windows 8.1 Update?
Windows image file boot (WIMBoot)
New for Windows 8.1 Update, devices can be configured to boot and run Windows directly from a .wim file.
This provides several benefits:
• Windows can run on smaller solid state drives
• Increases available disk space for end users
• Reduces OEM manufacturing time
To support WIMBoot, you will need updated versions of Windows PE and DISM. In addition, you will need to change some of your existing Windows customizations, recovery configurations and manufacturing workflows. This includes:
• Windows PE is updated to support WIMBoot. You will need to recreate your Windows PE images to support WIMBoot.
• DISM includes new command line parameter, such as /WIMBoot. When capturing and applying images, you must use this new parameter.
• You can use your WIM Boot image as a recovery image, saving disk space. You will have to update your recovery configuration and disk partition layout on the devices you build.
WIMBoot is only supported on Windows 8.1 Update images with the Windows 8.1 Update version of the Windows ADK.
For more information about WIMBoot, see the following topics in ADK_Online.chm file. Note that DISM PowerShell cmdlets are documented in DISM_Cmdlets.doc included in this documentation package.
Create and deploy WIMBoot images:
• WIMBoot: Windows image file boot (WIMBoot)
• Create WIMBoot Images
• Deploy WIMBoot Images
DISM Command line options:
• What's New in DISM
• DISM Image Management Command-Line Options
• DISM Windows Edition-Servicing Command-Line Options
Installing Windows 8.1 Update
In this EEAP release, Windows 8.1 Update is available as an MSU file. You can update your existing Windows 8.1 images by applying the update.
我要msu
难道这个不是最终的？
