Any chance we can get a few copies of this 'setuphost.exe' uploaded. Wondering if each copy is unique to each .esd it is packaged with. Either way, if it is the final stage before installation begins it must be able to mount the .esd format or call the procedure that does.
If I remember from before Windows 7 DVD was created from .exe, setup1.box & setup2.box Files... maybe is now X1897215.esd = setup1.box and WindowsStoreSetupBox.exe that .exe mystery
you need setup2.box... setup1.box was (2.04 GB) for win 7 setup2.box was (137.59 MB) for win7 and need .exe file to merge and extract them.
I would say that sounds roughly correct, so everyone sharing just the .esd file is missing a file and it won't help anyone to just have one file without the other (or many others) Edit: When you make the ISO with the download, it obviously has to complete the esd file. These iso versions would be the only versions worth tinkering with since they are essentially whole I wouldn't expect the decryption to be different in the iso version. If someone has a full setup iso from the 8.1 download I'd like to tinker with it and see if I can apply and capture the image. PM me if you can host a torrent or mega file of one...
But "install.esd" is not just a renamed download ESD file. The downloaded ESD file is still there and untouched. The 2 GB "install.esd" file is created new in folder "C:\$Windows.~BT\sources\" and this must take longer than 1 second (SATA HDD, not SSD).
Maybe it is created in one-second (i.e. appears in explorer) but still writing to disc in the background. Like when I copy a large file, I see the file the very first second I start copying it, but I cannot access the file until the copy process is completed. Check disk activity in resource monitor to confirm.
Yes. Yes. But I don't see when the command is finished. I only see the 2 GB "install.esd" is created in "C:\$Windows.~BT\sources\" in just 1 second. And I don't see any further disk usage in task manager.
That would be my prediction as well. I've noticed that win8.1 likes to do that instead of pausing at the end now
box1 is blabla.esd ~ install.esd ~ install.wim box2 is boot.wim all other files was generated from SetupBox... install.esd IS NOT untouched install.esd on It's end has: <WIM><TOTALBYTES>2580562214</TOTALBYTES><IMAGE INDEX="1"><DIRCOUNT>17613</DIRCOUNT><FILECOUNT>83076</FILECOUNT><TOTALBYTES>12619187822</TOTALBYTES>....</WIM> downloaded blabla.esd on It's end has exactly this crap i¤´ Êì8üÞø\$<&–Ö÷Ø™h0å Ñi¤´ AyõÜdx§8ÈÒVjgLN}é¼ Ùj¤´ ¶‘Yfóö§˜HUÕw¾ß4x •k¤´ 8—jÕPOÜHÕ6ð‹ONfuåü ™l¤´ 6íxÖ]øìòã9šîŸdÓn”ÿþ
But not only that. The command creates the folder "C:\$Windows.~BT\Sources" and these files: Code: install.esd 2.119.950.970 SetupCore.dll 765.784 SetupHost.exe 251.736 SetupMgr.dll 246.104 SetupUIMgr.dll 693.080 WinDlp.dll 876.888
You can find the log for operation in "C:\Windows\Logs\MoSetup\BlueBox.log" here is a sample i got (note the red): Code: 2013-10-18 22:26:20: CommandLine: [WindowsStoreSetupBox.exe /ClassId bd02c22b-1edf-476f-ab78-a72bdada6a47 /SessionId 1 /ReportId {3AB7C5F3-D1B0-4899-8FDD-565910F4D2F7}.1] 2013-10-18 22:26:20: Opening Box: [C:\M\WindowsStoreSetupBox.exe] 2013-10-18 22:26:20: Reading Box header... 2013-10-18 22:26:20: Opening Box container: [0]... 2013-10-18 22:26:20: Reading Box container header: [0]... 2013-10-18 22:26:20: Searching for ESD files... 2013-10-18 22:26:20: Found ESD file: [install.esd] [C:\M\WindowsBlue-ProESDwithApps-32bit-English-X1897212.esd] 2013-10-18 22:26:20: Attempt to remove staged Appx packages... 2013-10-18 22:26:20: Failed to remove staged Appx packages, Error: [0x8000FFFF] 2013-10-18 22:26:20: Creating path: [C:\$Windows.~BT\Sources]... 2013-10-18 22:26:20: Extracting files to: [C:\$Windows.~BT\Sources]... 2013-10-18 22:26:20: Verifying Box container: [0]... 2013-10-18 22:26:20: Reading Box container header: [0]... 2013-10-18 22:26:20: Extracting Box container: [0]... 2013-10-18 22:26:20: Successfully hardlinked: [C:\$Windows.~BT\Sources\install.esd] -> [C:\M\WindowsBlue-ProESDwithApps-32bit-English-X1897212.esd] 2013-10-18 22:26:20: Copying Dynamic Update files: [C:\M\DUDownload] -> [C:\$Windows.~BT\DUDownload]... 2013-10-18 22:26:25: Searching for ESD files... 2013-10-18 22:26:25: Found ESD file: [install.esd] [C:\M\WindowsBlue-ProESDwithApps-32bit-English-X1897212.esd] 2013-10-18 22:26:25: Launching process: [C:\$Windows.~BT\Sources\SetupHost.Exe] with command-line [/EditionId Professional /EsdFile "install.esd" /progressCLSID bd02c22b-1edf-476f-ab78-a72bdada6a47 /ReportId {3AB7C5F3-D1B0-4899-8FDD-565910F4D2F7}.1 /ProcessId 2464 /SuccessId 35594256-a4b1-4439-9004-361ca9b33578] in Session: [1] 2013-10-18 22:26:25: LaunchProcessInSession: Error = 0x80070522 2013-10-18 22:26:25: LaunchProcessInSession returned: [0x80070522] 2013-10-18 22:26:25: Checking cleanup registry value... 2013-10-18 22:26:25: Skipping cleanup. 2013-10-18 22:26:25: Path successfully cleaned! 2013-10-18 22:26:25: MainHr: Error = 0x80070522 the error 0x80070522 (usually mean permission access denied) may refer that the ClassId and ReportId are unique to each download also, WindowsStoreSetupBox.exe is the same (at least for x86 editions), this is the downloaded file from Store with Pro and ProWMC upgrades: Code: windowsstoresetupbox_422f9c316bdea76b4937cba044c7c08c680ce777.exe
A hardlink is what it sounds like. It doesn't actually contain the data, rather points the file to another file. This explains why it only took him a second to create a 2gb file.