UUP to ISO - Create Bootable ISO from Windows 10 Build Upgrade Files  

Just a note. If it has been mentioned before, I apologize.
When installing from created iso on a blank hard drive, you need to run the setup.exe manually.
The ISO boots into a cmd mode and you have to change drives and run the setup.exe before it will install.
Caught me out the first time I needed to do this.
Of course, an in-place update requires you to do this anyway.
Thanks.

Would accept this, but once booted, it works fine. in both new installations and upgrades across a lot of machines.
I would suggest the iso to USB maker Rufus, but the same version works for creating all iso-USB attempts.
Thanks

johngalt said:

I suspect that Tomcat just never realized that because it probably scrolled off screen?

Also, re: UUP2ISO - the UUPDump site is now set up so you can select your version, edition, and download a small .ZIP file that downloads the file you need or else downloads and combines the files into an .ISO all at once, with (slightly) more up to date scripting.

I've been using the new AIO method with 0 problems for at least 6 months, IIRC, and I've already performed at least once clean install since then with 0 issues.

This is all I use anymore. I am on Windows Insider and anytime they have issues with updating, I just use this and install. Works perfectly for me

Not sure if this has been posted but here is a link for wimlib14.7zip https://androidhost.org/vKjH5

I downloaded feature update 17763.349 amd x64 (all editions)last night during my satellite IP's "freezone" (12 GB/mo cap) directly from the UUPDump.ml site using aria 2 with conversion to ISO. Downloaded the zip files to downloads and extracted to same location. Opened the command line and the file downloads started at 3:40am and finished at 7:45am. Used latest Rufus(UEFI/GPT) to create what I thought would be a bootable USB drive from the ISO created. Had Rufus check the drive for bad blocks/sectors first(0 found) and then create the drive. When Rufus was done I ran a dism get wiminfo command to check the usb drive and it came back with the usual info but says not bootable. Opened the sources on the USB drive and install.wim is just install. Ran the get wiminfo command again without the .wim and it would not return any results. The created ISO from UPDump and the usb drive have identical install files without the .wim extension. Both when highlighte with cursor show they are wim files. Under properties both are exactly the same size to the byte. 4.39gb. There is also an efi/efi boot file in the finished usb drive. Any thoughts!

gcwizard said:

When Rufus was done I ran a dism get wiminfo command to check the usb drive and it came back with the usual info but says not bootable.

It sounds as if you are just overlooking some detail. If DISM /Get-WimInfo "came back with the usual info", it required a reference to either a WIM or an ESD file. It sounds like File Manager is set not to display file extensions and you have some app associated with WIM or ESD files, causing the extension to be hidden. Also, I believe Rufus makes the USB bootable in its own way, which has nothing to do with the install.wim/install.esd file contents. /Get-WimInfo does not indicate bootable or not. If you reference an Index, it will indicate WIM Bootable: No, which is an entirely different thing and supposed to be that way.