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

M4v3r1ck said:

Agreed 100%, that was the core of my Q! Also adding a timestamp to it may be useful!

At least MS does that for their builds. [emoji108]

Cheers

Absolutely, there is so much more to just writing an application, compiling, packaging and releasing. A lot of extra meta data must be included so the user and the developer both can check what they are using.

slicendice said:

Absolutely, there is so much more to just writing an application, compiling, packaging and releasing. A lot of extra meta data must be included so the user and the developer both can check what they are using.

Top Notch! [emoji41]

Cheers

We must be blind or something. Both the installer and the application contains the current version number which is 2.2.0.1

:)

slicendice said:

We must be blind or something. Both the installer and the application contains the current version number which is 2.2.0.1

:)

So we both must have a blind spot in our frontal cortex! Oops... [emoji854]

Where is version tracking post, or am I missing something obvious here?

For example:
2.2.0.1 date/time - release/change notes
2.2.0 date/time - release/change notes
2.1.x date/time - release/change notes

Cheers

johngalt said:

Do we all need to make this change on our end, of have you updated the tool to have this fix in it now, Kari?

I will post updated tool later today

rogerwilco91 said:

Thanks for the detailed explanation. Looks like after upgrading, the ESD's disappear and isn't in the Windows.old folder.

I've tested and tested, I can't get it to fail! The correct update files are always in Windows.old in all my tests. One strange thing I can see in your screenshots is that you only have about 4 GB free scape on system drive after the upgrade, thinking if that might be the culprit.

rogerwilco91 said:

So, maybe Kari should update the beta guide or notes and make sure that it mentions that creating the ISO after upgrading is still not possible?

It is possible. Yes, you have an issue with it but reading the feedback and what my own tests show there's no issue in general.

johngalt said:

The ßeta tool worked on my laptop post-update from the Windows.Old folder.

It locked up at 78% on my desktop pre-install.

Please could you explain a bit more detailed? UUPtoISO from Windows.old fails on your desktop?

rogerwilco91 said:

Edit: Could those AMD64 be related to the specific hardware architecture you are running (IE running on an AMD CPU instead of Intel?)

Those files and folders are amd64 in all 64 bit Windows, regardless if Intel or AMD hardware, and x86 in 32 bit Windows.

Microsoft uses these two Processor Architecture values, amd64 and x86. For instance when customizing Windows deployment image with Sysprep, bit architecture in unattended answer files must be told as <ProcessorArchitecture=amd64> if customizing a 64 bit Windows regardless if Windows image will then be deployed to AMD or Intel hardware.

For reasons unknown to me amd64 is what Microsoft has chosen to use to specify a 64 bit Windows installation.

z1r said:

Hi Kari, I just built an ISO after build 15058 was already installed and everything worked perfectly. Thanks for this great tool.

Hi z1r, welcome to Ten Forums. Positive feedback is always welcome, especially nice when a new member's first post is to say thanks, indicating he / she might have registered just to do that :)

slicendice said:

Our latest Beta tool does some extra conversion steps that might not be required for the final ISO.

I use Windows Pro en-US but our tool also converts Express Packages from fi-FI. I don't think these files are even included in the final ISO, at least I could not find any fi-FI Packages/folders in the install.wim file from the ISO.

That's because you have Finnish input language installed in English Windows. I get the same with Finnish, Swedish, French and German because I have those language packs and input languages installed.

slicendice said:

You are not using the latest tool we are testing. The current download contains files that are not signed and are not installed, thus requires you to unblock each and every file from the download before proceeding with the conversion process.

Only the installer is digitally signed, the app and uninstaller not, but there's no need to unblock anything.

M4v3r1ck said:

Where is version tracking post, or am I missing something obvious here?

Let me think how to do this.

To start with, here's a short changelog:
Version 2 > first that was delivered as application instead of batch file
Version 2.2 > Updated license and installer, shortened code by removing unnecessary elements, corrected some spelling in prompts shown to end user
Version 2.2.0.1 > Current version, only change was to replace a very pixelated low res Ten Forums logo in installer's last prompt with a high res image


Kari

Kari said:

Let me think how to do this.

To start with, here's a short changelog:
Version 2 > first that was delivered as application instead of batch file
Version 2.2 > Updated license and installer, shortened code by removing unnecessary elements, corrected some spelling in prompts shown to end user
Version 2.2.0.1 > Current version, only change was to replace a very pixelated low res Ten Forums logo in installer's last prompt with a high res image

Kari

Thanks!

Cheers

Just a general reminder geeks, a fact that I have tried to make very clear in titles and included Quick Start PDF:

The original decrypter script comes from fellow geeks at MDL forums. My part is and has only been to put things together.

Kudos where kudos belongs!

I'll start rewriting tutorial now. After some serious thinking I decided that this warning that has been in tutorial since the day it was written will remain:

   Warning

Notice please: When Windows Update has finished downloading the UUP upgrade, the files needed to make the ISO are stored in subfolders of C:\Windows\SoftwareDistribution\Download.

These files will be removed when upgrade is done. If you want to make an ISO for future needs, you have to do it before starting the upgrade process itself, after downloading the upgrade files but before clicking Restart now button!

It's then up to end user to decide if he / she wants to bite the bullet and try his / her luck, upgrade first and then when done check if ISO can still be made from Windows.old

Kari

Kari said:

I'll start rewriting tutorial now. After some serious thinking I decided that this warning that has been in tutorial since the day it was written will remain:

   Warning

Notice please: When Windows Update has finished downloading the UUP upgrade, the files needed to make the ISO are stored in subfolders of C:\Windows\SoftwareDistribution\Download.

These files will be removed when upgrade is done. If you want to make an ISO for future needs, you have to do it before starting the upgrade process itself, after downloading the upgrade files but before clicking Restart now button!

It's then up to end user to decide if he / she wants to bite the bullet and try his / her luck, upgrade first and then when done check if ISO can still be made from Windows.old

Kari

Managed to make an ISO and installed it in Hyper-V.

Only issue was that I had to run the executable as Administrator.

fjk61011 said:

Managed to make an ISO and installed it in Hyper-V.

Only issue was that I had to run the executable as Administrator.

Strange. It's made to run elevated, it should be elevated automatically. I'll check that.