@ murphy78 Could you tell me how to put the script from install.esd to install.wim? I don't have any problem from install.win to install.esd but on the other side I can't Many thanks in advance,
It's not advisable to go from esd to wim as you have to apply/re-capture. you can do it, but your wim file will be different every time. It's better to keep your wim source and just export to esd. If you really must know, though... basically the best way is to create a vhd with diskpart and then apply an index to it with dism, then re-capture the directory to a new wim file. You can pick apart the esd decryption and conversion script in my sig and just strip out the decryption parts if you wish, tho you don't really need to. The decryption won't modify the esd if it's not encrypted. EDIT: abbodi1406 figured out a way to export an esd to wim using the wimlib-imagex update utility and a nifty export/delete trick... You can pick apart his latest esd decrypter tool and just use the tid-bits that suit your needs.
Hmm although I experienced no crashes after limiting the ram that boot.wim uses, others are still reporting issues. I played with a lot of different options. I integrated a pre-ga boot.wim with all the updates and resetbase'd it, and subbed it in and copied over the newer date files from sources\ directory to the iso folder... That didn't help at all. First image I tried, failed. I then decided to re-export the coresl versions using abbodi's new trick, in the hopes that maybe there was some sort of datastream problem and that a non-captured version might help. On top of that I decided not to integrate things in the same manner. Basically my previous method add-package'd and resetbase'd the 3 non-pending updates. Then it would install the other 3 starting with 2934018... In this latest version I just start with 2934018, add all the rest, and don't bother with the resetbase stuff... My thinking is that maybe there's some sort of file length issue with a version that has had resetbase applied to it while offline. I also moved from a purely msu integration method to a purely cab method. There's really no need to use msu files on an offline image. My hope is that a combination of the three things I did here will fix the problem, and so far testing has proved successful. Of the 9 indexes I've tested so far in a vm, 9 passed... I'll flip it to uefi and test the other 10 after this next one... But, it looks promising... Anyway, just documenting the issue...
Well, x64 tested 20 for 20 with no fails and no memory limit. I've just gotta test a few of the x86 indexes to make sure that one is ok... It was never an x86 problem though...
1. Hooray for murphy78 and AIO! 2. Hooray for MDL and all contributors! 3. Hooray for Boobies (no pics)!
What about the Scratch space for your WinPE? I had issues last year with random failure & discovered I was running out of space on X:. Even when setting temp locations from x: to a hdd, I found that X: was still being used for temp files during wim/esd manipulation. Try increasing the size by using the dism /Set-ScratchSpace command on your winpe...
Tried that. It had no effect. Unfortunately that just increases the ram drive spce. It doesn't actually increase the available ram for the system to extract any images. Instead of the default 32megs you can up it to 512. I think the problem was in the filestream though, not necessarily any settings.
@murphy78 How you preActvate your integrated Win811 packages with KMS Activator? I have used AutoKMS file you provided to me, but FirstLogon.cmd and SetUpComplete.cmd don't work. With $oem$ insertion all files are on right places but commands are not executed.
I have tested that approach earlier, when you suggested it first time, but FirstLogonCommands was not executed?!
That would need either the second suggestion from my previous post or an ei.cfg file in the sources folder of the ISO. ei.cfg should look like this: Code: [Channel] Retail [VL] 0