Another Dumb Question 2+2 = 4 ? DO we need some special program to discover its true or not??? its well known... What you discovered/mentioned is well known... Here we talking about .esd files... its new to us coz now we can create it & use it to bypass some limitations, without much complication.... what to choose a simple method to achieve same target or complicated to get more attention? many workaround floating around, some are complicated & some are simple....
Yes. But in this case I'd recommend just set up Windows Deployment Services server and netboot your systems to setup, in that case you don't need to modify winpe.
i just want to add that i use a 32 gig NTFS partition with a small 100 meg fat32 partition with the efi dir and bootmgr.efi. From Clover, i took the NTFS.efi driver, and added it to my "rEFInd" drivers in the fat32 efi dir. After it boots, it will search NTFS drives for an efi folder. From there, load the desired .efi from the NTFS drive and boot.wims and such from the NTFS drive will boot.
Is the /recovery parameter exclusive to the .esd format? Or can you export a .wim using /recovery compression?
How did you got the wim /info from the ESD? I tried DISM and Imagex but it's not supported (as I expected).
Maybe the secret to reading the insides of these .esd can be found inside the 'setuphost.exe'. But FYI to readers, looking at the page you linked those classid/reportid/sessionid change (see comments section on superuser.com)
If you open raw ESDs in a superb hex editor, you'll even see that they have the WIM header starting with MSWIM. But end of file that i have is without <WIM> .... </WIM> ... looks like someone cut off end of file...and that all you can do.to sit and cry . generally does not worth for someone trying to decrypt that crap.it is cheaper to buy, windows.
Correct. I find these two and don't know what "ClassId" and "ReportId" are for: WindowsStoreSetupBox.exe /ClassId bd02c22b-1edf-476f-ab78-a72bdada6a47 /SessionId 1 /ReportId {3AB7C5F3-D1B0-4899-8FDD-565910F4D2F7}.1 WindowsStoreSetupBox.exe /ClassId fbd36d9c-2444-4a8b-8506-99442f2b554f /SessionId 1 /ReportId {4F84CA36-99F8-49C9-9C7F-8CE80689FFD5}.1 Also I noticed: When the command runs then in just one second the 2 GB file "C:\$Windows.~BT\sources\install.esd" is created. I would expect that it will take longer to extract 2 GB install.esd from the ESD file. I started "WindowsStoreSetupBox.exe" - copied from a x64 installation - to a x86 installation and got the error: Wrong version ...
As i mentioned before, it looks like someone cut off end of downloaded esd file.If this is the case end of file is generated and merged (combined binary ) and renamed, in just one second into one single file named install.esd.But nobody knows how to unpack that install.esd also .