Hmmm, looks like it's not my input, x86 uptodate boot.wim just seems to work fine using standard setup. Can you confirm?
Sorry I can't confirm. All my hardware setup for making compilations (AIOs) is not plugged in. Poor man here.
I use wimlib which also lets you change date & time as well. I'm not at work so can't post/remember the exact command.
These are the steps i am doing: 1.Downloaded the CombinedSL ESD file from the thread - [DISCUSSION] Windows 10 (1703 RS2) "Creators Update" Final 15063 (PC).used abbodi's script - "esd-decrypter-wimlib-28.7z" , option - 1 to create a standard iso image. 2.Then did the W10UI(W10UI_1.8.zip) using the latest updates(kb4015583 & kb4018483) on all the respective four indexes. 3.Deleted the "Updated" boot.wim file and copied the "Clean" boot.wim file from the iso image i created in Step 1 in the sources directory. 4.Now, whenever i boot the system i keep getting the same error. NOTE: 1. I am proceeding using the standard setup and not using Murphy78's script.
That's what i said from the beginning. not updated boot.wim works always, uptodate x64 boot.wim doesn't work with standard setup, but works with murphy78's script, uptodate x86 boot.wim works fine with standard setup and script.
Install CU after enabling .net 35, the CU can have update components for .net 35. Best is to pre-enable dotnetfx on the mounted wim, and integrate the CU after that.
Sorry for the delay... been away for a few days Review - Updated (ALL) + Corrected some (KB) article links + added MFP for 1703(N) links
I used this for first time to integrate Windows Updates on to Windows 10 Creators Update x64 ISO which had 4 editions on it which was Home, Pro, Enterprise, and Education. It does better job by not increasing the WIM file size. Before I used MSMG for integrating updates but it always increased the WIM file size.