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.
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
- WIMBoot is available for client editions of Windows 8.1 with Windows 8.1 Update only (not server versions). All architectures are supported, including amd64, x86, and ARM. Some enterprise deployment tools do not yet support WIMBoot.
- WIMBoot is available only for UEFI-based PCs running in UEFI mode (legacy BIOS-compatibility mode isn't supported).
- WIMBoot is supported for solid-state drives and eMMC (Windows HCK compliant) drives. WIMBoot isn't supported on traditional drives that contain rotational components, or on hybrid drives that contain both solid-state and rotational drive components. WIMBoot works by taking advantage of the capability of solid-state drives to access different areas of the hard drive quickly.
- It's OK to have a secondary drive attached to the PC, and the secondary drive can contain rotational components. But the WIMBoot image and pointer files must all be located on the primary solid-state or eMMC drive.
- Some backup, antivirus, and encryption tools aren’t compatible with WIMBoot images.
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.
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
- WIMBoot is available for client editions of Windows 8.1 with Windows 8.1 Update only (not server versions). All architectures are supported, including amd64, x86, and ARM. Some enterprise deployment tools do not yet support WIMBoot.
- WIMBoot is available only for UEFI-based PCs running in UEFI mode (legacy BIOS-compatibility mode isn't supported).
- WIMBoot is supported for solid-state drives and eMMC (Windows HCK compliant) drives. WIMBoot isn't supported on traditional drives that contain rotational components, or on hybrid drives that contain both solid-state and rotational drive components. WIMBoot works by taking advantage of the capability of solid-state drives to access different areas of the hard drive quickly.
- It's OK to have a secondary drive attached to the PC, and the secondary drive can contain rotational components. But the WIMBoot image and pointer files must all be located on the primary solid-state or eMMC drive.
- Some backup, antivirus, and encryption tools aren’t compatible with WIMBoot images.
google翻译：
有什么新的ADK的Windows 8.1更新？
The spring update for Windows 8.1 will also allow OEMs to lower their specifications for devices. Belfiore says PC makers will be able to use just 1GB of RAM and 16GB of storage in future Windows 8.1 devices, a change that will help bring lower price points. It's likely that these updates to Windows 8.1 are linked to recent OEM changes to lower license costs.
