I'm confused - does this ADK include the Windows 8.1 update 1 RTM release or not? as Wzor says:- 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.
Here's some pertinent information about wimboot I found from the chm. I had to use a custom program called fbreader to actually read the details but here's a good start about setting up the partitions and stuff: Spoiler Format the drive with the WIMBoot partition layout 1. Boot the reference PC into Windows PE 5.1. 2. Format the drive using the following partition layout: • System (EFI System Partition): Size: 100MB. If the primary drive is less than 16GB, you can use a minimum size of 32MB. If the primary drive is an Advanced Format 4K Native drive (4-KB-per-sector), the minimum size is 260 MB. • MSR (x86 and x64 only, not needed for ARM) • Windows. • Images. Set this partition with the following attributes: • Location: End of the disk • Type: de94bba4-06d1-4d40-a16a-bfd50179d6ac (PARTITION_MSFT_RECOVERY_GUID) • Attributes: 0x8000000000000001 (GPT_BASIC_DATA_ATTRIBUTE_NO_DRIVE_LETTER & GPT_ATTRIBUTE_PLATFORM_REQUIRED) • File system: NTFS • Drive Letter: Set a temporary drive letter, for example, M. • Size: Must be big enough to hold install.wim, winre.wim, and custom.wim files plus at least 50 MB of free space. Note If you plan to make changes on the factory floor in the custom.wim file, be sure to leave enough space for these additions. But try not to add too much free space, especially on devices with limited drive space, because this partition can’t be resized after you've added files to it. To work around this problem, you can set up this Images partition later. For more info, see Deploy WIMBoot Images: If you don't know the size of the images upfront. Sample Diskpart script The script temporarily assigns these drive letters: Windows=C and Images=M. If you’re deploying to PCs with unformatted hard drives, you might want to modify this script to use a drive letter that’s near the end of the alphabet, such as W, to avoid drive letter conflicts. Do not use X, because this drive letter is reserved for Windows PE. After the PC reboots, the Windows partition is assigned the letter C, and the other partitions don’t receive drive letters. We've added volume names to the partitions, but they aren’t required. Code: rem == Diskpart /s CreatePartitions-WIMBoot.txt == rem == These commands set up the hard drive partitions rem for WIMBoot. rem rem Adjust the partition sizes to fill the drive rem as necessary. == select disk 0 clean convert gpt rem == 1. System partition (ESP) =================== create partition efi size=100 format quick fs=fat32 label="System" rem == 2. Microsoft Reserved (MSR) partition ======= create partition msr size=128 rem == 3. Windows partition ======================== create partition primary shrink minimum=10000 format quick fs=ntfs label="Windows" assign letter=c rem === 4. Images partition ======================== create partition primary format quick fs=ntfs label="Images" assign letter=m set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac" gpt attributes=0x8000000000000001 list volume exit Add the Windows and recovery files 1. Create a folder called "Windows Images" on the Images partition. This folder name is required. Code: md "M:\Windows Images\" 2. Copy the Windows image from the USB or network drive (N) to the Windows Images folder. Rename the Windows image to install.wim if necessary. Code: copy N:\Images\install_update1.wim "M:\Windows Images\install.wim" 3. Apply the Windows image to the Windows partition (drive C), using the /WIMBoot option. Recommended: create a temporary scratch folder for DISM to avoid issues related to short file names. To prevent capturing the DISM logs in your image, choose a location that is in your DISM Exclusion list. For more info, see DISM Configuration List and WimScript.ini Files. When you use the DISM /Apply-Image command with the /WIMBoot option, the ImageFile location and ApplyDir partition must be on the same hard drive. Code: md C:\Recycler\Scratch DISM /Apply-Image /ImageFile:"M:\Windows Images\install.wim" /ApplyDir:C: /Index:1 /WIMBoot /ScratchDir:C:\Recycler\Scratch Note When you apply the Windows image using /WIMBoot, DISM adds pointer files from the Windows partition to the Images partition. These pointer files make the PC appear and function as if the Windows files were stored on the Windows partition. But they still primarily reside inside the install.wim file in the Images partition. Do not remove the install.wim file after applying the image. 4. Create boot files and set them to boot to the Windows partition. Code: C:\Windows\System32\bcdboot C:\Windows 5. Copy the Windows RE file to the Images folder. Note that Winre.wim may be a hidden file. Use robocopy or xcopy to copy the file. In this example, the "echo f" command suppresses the xcopy "File or Directory" prompt: Code: md M:\Recovery\WindowsRE echo f | xcopy N:\Images\winre.wim M:\Recovery\WindowsRE\winre.wim /h 6. Register the Windows RE partition. Code: C:\Windows\System32\Reagentc /SetREImage /Path M:\Recovery\WindowsRE /Target C:\Windows 7. If your partition configuration is different from the recommended configuration listed above, create a ResetConfig.xml file and include it in the M:\Windows Images\ folder to enable your users create bare metal recovery media. For more info, see ResetConfig XML Reference. Sample command-line script Code: @echo off echo == ApplyWIMBootImage.cmd == echo == These commands deploy a specified Windows echo image file to the Windows partition, and configure echo the system partition. rem Usage: ApplyWIMBootImage InstallWim WinREWim rem Example: ApplyWIMBootImage N:\Images\Install-WIMBoot.wim N:\Images\WinRE-WIMBoot.wim if "%2" equ "" ( echo == Error: Specify a Windows image and a Windows RE image file. echo Example: ApplyWIMBootImage N:\Images\Install-WIMBoot.wim N:\Images\WinRE-WIMBoot.wim exit /b 0 ) @echo on rem == Add the Windows image to the Images partition == md "M:\Windows Images\" copy %1 "M:\Windows Images\install.wim" rem == Create a scratch directory for DISM operations md "C:\Recycler\Scratch" rem == Apply the Windows image to the Windows partition == dism /Apply-Image /ImageFile:"M:\Windows Images\install.wim" /ApplyDir:C: /Index:1 /WIMBoot /ScratchDir:C:\Recycler\Scratch rem == Create boot files on the System partition == C:\Windows\System32\bcdboot C:\Windows :rem == Add the Windows RE image to the Images partition == md M:\Recovery\WindowsRE copy %2 M:\Recovery\WindowsRE\winre.wim :rem == Register the location of the recovery tools == C:\Windows\System32\Reagentc /SetREImage /Path M:\Recovery\WindowsRE /Target C:\Windows Optional: Test the PC, and then reset itTo test the PC: 1. Reboot the PC and log in as a user. 2. Install and run performance test software in the Windows environment. To reset the PC: 1. Reboot the PC into Windows PE 5.1. 2. Temporarily assign drive letters to the Windows and Images partitions. Code: Diskpart /s ResetWIMBootDriveLetters.txt ResetWimBootDriveLetters.txt: Code: rem == Diskpart /s ResetWIMBootDriveLetters.txt == select disk 0 select partition 1 assign letter s select partition 3 assign letter c select partition 4 assign letter m list volume exit 3. Reapply the Windows image to the Windows partition. Recommended: create a temporary scratch directory for DISM. Code: rem == ResetWIMBootImage.cmd == format C: /Q /FS:NTFS /v:"Windows" md C:\Recycler\Scratch DISM /Apply-Image /ImageFile:"M:\Windows Images\install.wim" /ApplyDir:C: /Index:1 /WIMBoot /ScratchDir:C:\Recycler\Scratch A lot of this stuff is going to take a while to play with... but get the fbreader program and search for wimboot in the chm file and you can read more...
Good job, murphy, suggest start a thread on it for further discussions - When the leak comes this good work might be lost in the flood of posts.
Hmm I'm not sure it warrants that much attention... I'm reading the create wimboot stuff and I'm getting a little confused as to its' actual usage. See if you can follow this: Spoiler Create WIMBoot Images Windows image file boot (WIMBoot) helps you save hard drive space by booting to a WIM file rather than a set of uncompressed Windows files. For more info about WIMBoot images, see Windows Image File Boot (WIMBoot) Overview. To save room on the images, separate the Windows Recovery Environment (Windows RE) image from the main Windows image. Otherwise, this image will take up 200 MB or more of extra drive space in your image and will otherwise never be used. This image is stored inside the main Windows image at \Windows\System32\Recovery\winre.wim, and might be a hidden file. This page focuses on a method to create WIMBoot images that use a minimum of drive space. It also discusses other methods to create WIMBoot images to reduce the total number of Windows images that you manage. Update your Windows image • Install Windows 8.1 Update to your Windows 8.1 and Windows RE images. For more info, see Install the Windows 8.1 Update. Install the Windows 8.1 Update version of the Windows ADK • On your technician PC, install the Windows 8.1 Update version of the Windows Assessment and Deployment Kit (Windows ADK). Recommended Method: Create a WIMBoot-optimized imageCreate a temporary copy of the install.wim image • Copy the install.wim to a new temporary file. You'll use this copy of the file to create your WIMBoot image. Code: Copy C:\Images\install_updated.wim C:\Images\install_temp.wim Separate the Windows RE image from the main Windows image 1. Create a mount directory for your install.wim files and mount the image. Code: md C:\mount\Windows Dism /Mount-Image /ImageFile:"C:\Images\install_temp.wim" /Index:1 /MountDir:C:\mount\Windows 2. Move the winre.wim file out of the image. Code: move C:\mount\Windows\Windows\System32\Recovery\winre.wim C:\images\winre.wim Optimize the Windows image for WIMBoot • Optimize the image for WIMBoot to gain free drive space in the final image. Note Don't optimize the image using the /WIMBoot option for traditional (flat-boot) PCs, or for images used in enterprise deployments. The optimization process removes features for on-demand installation that might be needed for these PC deployments. For more info, see To remove Windows features for on-demand installation. Code: Dism /Optimize-Image /Image:C:\mount\Windows /WIMBoot • Unmount the image and commit the changes. Code: Dism /Unmount-Image /MountDir:C:\mount\Windows /Commit Boot the image to apply the updates and to clean up the image 1. On your reference PC, boot to Windows PE 5.1, apply your Windows image, and then boot the PC again. For more info, see Samples: Applying Windows, System, and Recovery Partitions by using a Deployment Script. 2. Press CTRL+SHIFT+F3 at OOBE to enter audit mode. 3. Clean up the Windows image to gain additional free drive space in the final image. Use /StartComponentCleanup to clean up the superseded components and reduce the size of the component store. If you've already used the /ResetBase option when creating your base Windows 8.1 Update image, you don't need to run it again. To see the file size reduction, you'll need to either recapture or export the image. Code: Dism /Cleanup-Image /Online /StartComponentCleanup 4. Use Sysprep to generalize and shut down the PC. Code: C:\Windows\System32\Sysprep\sysprep /generalize /shutdown /oobe 5. Boot the PC to Windows PE 5.1. If the PC starts to reboot to Windows, you'll need to let it finish booting and then use Sysprep to generalize and shut down the PC again. 6. Recommended: Create a temporary scratch directory, for example, C:\Recycler\Scratch. Choose a location on a physical drive to avoid issues related to capturing files with long file names in the default Windows PE virtual scratch space. Choose a space that’s in the DISM Exclusion list to prevent capturing the DISM logs in your image. For more info, see DISM Configuration List and WimScript.ini Files. Code: md C:\Recycler\Scratch 7. Recapture the Windows image. This captures the applied updates and removes any files that were marked as superseded during DISM /Cleanup-Image. Use the /WIMBoot option to save the image as a WIMBoot image. Save the file to a location on a USB drive or your network (example: N:\Images), and give the image a name (example: Enterprise_x64 with 8.1 Updates). Code: DISM /Capture-Image /WIMBoot /ImageFile:"N:\Images\install_wimboot.wim" /CaptureDir:C: /Name:"WIMBoot Enterprise_x64 with 8.1 Updates" /ScratchDir:C:\Recycler\Scratch Method 2: Add WIMBoot support to a standard image • To quickly add WIMBoot support to a standard (flat-boot) image to a WIMBoot image, you can either capture or export the image. The final image size will be larger than if you had optimized the image using the instructions on this page. You’ll also need a separate, updated Windows RE (winre.wim) file. For more info, see Install the Windows 8.1 Update. Example: Code: Dism /Export-Image /WIMBoot /SourceImageFile:C:\Images\install.wim /SourceIndex:1 /DestinationImageFile:C:\Images\install_wimboot.wim Note If you don’t optimize the image (Dism /Optimize-Image /WIMBoot), you can use this image for both standard and WIMBoot PCs. This can help you manage fewer images in your deployment process. Additional notes • Don’t append images into an existing WIM file, because WIMBoot only supports using the first Windows image in the file (index value of 1). I'm seriously confused... If we are booting a wimboot system, why does it have both windows in the main partition and an install.wim with an dism wimboot optimized install.wim single index in a separate partition? Is this not exactly like the install.esd push-button reset images do on laptops already? edit: Yah yer right lets move this discussion to a new thread... it will help wrap our brains around things whilst this thread is getting spammed by "LEAK YET?" comments...
I've been following your exchanges on twitter. Thanks for the update - hopefully we'll have the MSUs soon!
why another lang packs ? so we need istall also lang pack with spring update ? hope that tomorrow will be all leaked
there is no problem for us to leak 17031 and to be honest everything is ready for it. Will take no time for to publish magnet urls. The main question is do we want to tell you that 17031 is a RTM? Do we want to be blamed for providing the wrong info to you? Once again we can leak 17031 right now but we cannot guarantee that 17031 is RTM. Wzor say that 17031 could not be rtm version
to be honest, who gives a sh*t, we are all in this for any leaks, same as what came before, it wasn't rtm, we just want to play with anything, that's the fun of leaks such as these, so this is just 1 big excuse, sorry