Has anyone got Windows Recovery to work on a WIMBoot installation of Windows 10? Here's the problem. In a WIMBoot setup the WinRE file is moved out of the file system and put in the recovery partition and its new location is registered with reagentc. However the Windows 10 version of reagentc doesn't allow me to register a new location for WinRE.
Is there any official word from MS that WIMBoot is no longer supported? And is there and technical information about OS compression (and how to make recovery work without a dedicated partition)? All I'm seeing so far is marketing speak.
I was able to install with WIMBoot on my WinBook TW801 from MicroCenter by first installing it the "normal" way and then using DISM to create a Win10 WIMBoot image with this command "DISM /Capture-Image /WIMBoot /ImageFile:{driveletter}:\Images\install.wim /CaptureDir:C: /Name:"WIMBoot Windows 10 Technical Preview" /ScratchDir:C:\Recycler\Scratch" from WinPE and then applying it with this command "DISM /Apply-image /ImageFile:{driveletter}:\Images\install.wim /ApplyDir:C: /Index:1 /WIMBoot /ScractchDir:C:\Recycler\Scratch"
Quick question here. For the WinHEC lab a flash drive was distributed with install scripts and tools, are the contents of that drive available? Without detailed scripts the best I can do is create the "WinRE" partition using the same parameters I use with 8.1's "Images" partition.
Don't think so (if there are even scripts that aren't in the lab paper printed anyway), what else do you need to know? Just apply your image with dism and the /compact switch.
In 8.1 I have the following in my diskpart script: Code: format quick fs=ntfs label="Images" assign letter=m set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac" gpt attributes=0x8000000000000001 Are the same values used in Windows 10?
That doesn't tell me what you want to actually know, but i can give you this. Code: select disk 0 clean convert gpt rem == 1. System partition ========================= create partition efi size=100 rem ** NOTE: For 4KB-per-sector drives, change this rem value to 260 ** format quick fs=fat32 label="System" assign letter=S rem == 2. Microsoft Reserved (MSR) partition ======= create partition msr size=128 rem == 3. Windows partition ======================== rem == a. Create the Windows partition. ========== create partition primary rem == b. Create space for the recovery image. === shrink minimum=500 rem == c. Prepare the Windows partition. ========= format quick fs=ntfs label="Windows" assign letter=W rem == 4. Windows RE tools partition =============== create partition primary format quick fs=ntfs label="Recovery" assign letter=R set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac" gpt attributes=0x8000000000000001 Here one without the comments Code: select disk 0 clean convert gpt create partition efi size=100 format quick fs=fat32 label="System" assign letter=S create partition msr size=128 create partition primary shrink minimum=500 format quick fs=ntfs label="Windows" assign letter=W create partition primary format quick fs=ntfs label="Recovery" assign letter=R set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac" gpt attributes=0x8000000000000001 This is what the new format is supposed to look like.
You don't hide Recovery partition anymore because there is NO recovery partition in w10. Hence the script you posted is redundant. Edit: The IMAGES partition that is. There still is a partition for Winre.wim but it MUST be after OS partition (hard requrement) Edit2: Also I wonder how many of us MDLers where in Prague last week
The script is correct. The Recovery Partition here is only 500mb big (adjust to fit custom sizes), it's only for WinRE not a recovery image and the script clearly creates it last. Code: set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac" Sets it so that it shows up as Recovery Partition, this has the effect that novice users can't delete it inside the Disk Management GUI. Code: gpt attributes=0x8000000000000001 Flags the partition to hide (additional security measure against s**tty novice users) so it doesn't show up in Disk Management GUI to begin with. It's has pretty much just one purpose: Don't make it show so people don't try to delete it. The WinRE Partition also needs to be bigger than normal as it appears to be updateable now.
I was refering to this script: format quick fs=ntfs label="Images" assign letter=m set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac" gpt attributes=0x8000000000000001 Yours is following the new guide lines. Should have been more specific. Also according to MS Recovery partition will be recreated with winre.wim updates through Windows Update. That's why it has to be right after OS partition. I still can't see how they can modify this partition with others after it and MS tech guy didn't realy know too. We will have to wait for a build supporting new Recovery to find out i guess.
The whole Recovery idea is to rebuild your system from a components catalog on your disk and customization contained in .pckg file. That's a risky maneuver already. I'd love a diskpart with gparted functionality tho and i think with stuff you showed that's how it's going to be done. Edit: TUTORIAL: As soon as W10 builds support new recovery there's going to be one I am sure.
I own a Pipo X7 with Windows 8 (BING edition), factory installed in Wimboot mode... Does that mean I won't be able to upgrate to Windows 10??? I bought that box hoping to upgrade it to Win 10 when it goes RTM
No need to worry. MS said they will support all upgrade scenarios including WIMBoot. That's what this auto-repartitioning is about partialy.
As Reefer says, MS has promised to cover this. But, as with Windows Phone upgrades on phones with limited storage (4/8GB) , you will probably have to move or backup your data to an external drive to give the OS room to upgrade.