I DID IT!
Manually created esd files from the package folders:
STEP1: Processed ActionList.XML:
STEP2: Created a bunch of commands:
STEP3: Ran the commands one by one (sry no screenshot)
STEP4: Ran uup2iso as usually
RESULTS:
Converted these
to this
Created ISO
Mounting ISO
Looking at the Wim-files
Everything looks normal! Now we have to automate this! :-D
Well don't just stand there, man. Automate, automate. :) :) :)I DID IT!
Manually created esd files from the package folders:
STEP1: Processed ActionList.XML:
STEP2: Created a bunch of commands:
STEP3: Ran the commands one by one (sry no screenshot)
STEP4: Ran uup2iso as usually
RESULTS:
Converted these
to this
Created ISO
Mounting ISO
Looking at the Wim-files
Everything looks normal! Now we have to automate this! :-D
need to assign a parameter to the package packagepath line in xml and then loop the parameter with win-lib command
or should I say %Result% in stead of parameter
I know exactly what has to be done, I just can't do it as a shell script. I don't know why, but shell scripting is confusing for me. :-(
Writing the thing in pure Assembly would be easier than in shell scripting, not that I am going to attempt that.
Just verified that my experimental uup2iso method actually works.
Clean installed from the created ISO in Hyper-V, and no problems at all.
Must be something in the Finnish drinking water....or a diet of reindeer burgers! :)
Good job!
Kari - just tried to create an .iso going from 15042 15046. You method appears to not work any longer. I followed your steps. Here is how it played out.
1. There is now just 1 .esd file (Professional_en-us.esd). No worries, right mouse and proceeded to that Hex directory
2. Copied all to the UUPs folder
3. Ran the UUPtoISO.cmd file - selected 2 (verified the description, etc) - all appeared good at this point
4. Selected 1 and it did the convert of the esd (as expected)
5. When it got to the Creating install.wim - Error: If this is a delta WIM, use the --ref argument to specify the WIM(s) on which it is based. arghhh
Any thoughts of how to resolve this?
Also, FYI - I also tried the registry hack - no joy on that either.
This is the reply I left to your comment on YouTube:
KariThere's a bug in 15046 upgrade upgrade, upgrading to 15046 works and is OK but making ISO is not possible. The same bug prevented making ISO in build 15025 upgrade.
All my videos contain links to respective tutorials on Ten Forums in video description. With Windows Insider builds anything is possible, I wholeheartedly recommend always checking the tutorial thread when a new build comes out.
This warning was posted in UUP to ISO tutorial when 15046 was released: UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files
I really don't think this is a bug. I have a feeling MS is experimenting with even better file compression for smaller delivery sizes. This is why I will continue to try to work out a long term solution for this.
As I mentioned earlier, instead of sending us a bunch of esd files we get a bunch of rng files. These files gets expanded into their proper folders during the preparation stage. These rng files contain exactly the same stuff the esd files contains. And it seems it is very easy to put the expanded folders back into esd.
Quote
