New
#630
No issues running UUP-->ISO post install as my system downloaded and installed 16176 without me doing anything. I wasn't even aware a new build had been released, but the day it was released, my computer download it, and installed it, with 0 intervention by me.
Hence I had to try post install.
Kari, both 16170 and 16176 worked flawless for UUP2ISO in my VM's. No issues or false flags from Defender and or ESET!
Enjoy your Easter weekend.
Cheers
After a long & satisfying Easter weekend spent with my son, daughter, & daughter - in-law I finally got down today to downloading & installing build 16176. I got to the stage where the system says "Restart now" at which point I initiated the "uup to iso" program & succeeded in creating an x86 iso for build 16176. Having moved the iso to a safe location I pressed the "Restart now" button & the system started the upgrade process. I intend to re-create the iso file using the Windows old file. Let us see what happens.
Odd question...
I finally got the ISO created. If I boot the ISO, everything works great! THANK YOU ALL FOR YOUR HARD WORK ON THIS PROGRAM!!!!
My question is... I use Windows Deployment Service to import the WIM files from the Sources folder.
When I import the install.wim, everything is good.
When I import the boot.wim.. It shows the image is "Microsoft Windows Recovery Environment (x64)". If I use this to network boot, it just loads Windows PE instead of the actual setup. Any thoughts as to why this may be? This only happens since the UUP versions.
There's luckily an easy workaround for this:
- Download last official Insider ISO, at the moment build 15063 is available
- Copy the content of that ISO to a folder, in this example now let's say D:\ISO_Files
- Replace D:\ISO_Files\Sources\install.wim with the install.wim from your last UUPtoISO image
- Make new ISO with OSCDIMG, included in Deployment tools component in Windows 10 ADK:
Code:oscdimg.exe -m -o -u2 -udfver102 -bootdata:2#p0,e,bd:\iso_files\boot\etfsboot.com#pEF,e,bd:\iso_files\efi\microsoft\boot\efisys.bin d:\iso_files d:\MyISO.iso
Full instructions and ADK download link in Part Five of this tutorial: Create Windows 10 ISO image from Existing Installation - Windows 10 Installation Upgrade Tutorials
1- It is not a bug, it is how Microsoft build UUP files, they choose to deliver winre.wim only
because technically, boot.wim is not required for WU upgrade process
2- A workaround already had been implemented in the original uup-converter-wimlib script
you just need to cooperate with the subsequent releases
once more successful with build 16179 this time, both before restart and after with windows.old