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

slicendice said:

I totally agree!

I have been planning on upgrading all these scripts to PowerShell modules and Scripts (because that is what MS want us to use in the future), and also create a GUI for those who does like more visual ways of doing things. Maybe even add some service that automates EVERYTHING regarding ISO creation from update files. Also planning on including a default configuration/settings file that could be easily modified, either by a PS script, manually or the GUI. This coding project would solve all the install/uninstall, missing upgrade files for proper ISO creation and other error, problems.

Sounds very promising to add a preferences pane to the installer! Will it be like "browse folder and select" for all install/ISO options?

Another (actually main) reason, is that when I code .cmd files in Visual Studio, I get no proper intellisense, no auto completion, no proper code map and code assistance. This easily creates a lot of coding errors, a lot of confusion and no references can be automatically verified anywhere. Also most Shell scripting commands are extremely cryptic and confusing, and I like to have code that is self explanatory and very well structured. Like writing a book with a good and easy to understand story.

Using the PS scripts would not change how the tools look and feel. (well maybe a little bit ) Installer would ask what files/folders to put where and the uninstaller would ask what to remove and what to not touch during removal of the application.

What do you guys think about that?

You have my up-vote, GREAT idea to make this great tool much more user customizable and thus user friendly! I like that. [emoji41]

Cheers

f14tomcat said:

@Kari , @slicendice Just a thought....

Maybe we can modify the UUP2ISO to offer an option of where to create the ISO. Then, it would be safer? Not privy to the design and development, so just thinking out loud.

TC

I like this idea. More below.

Kari said:

   Information

UUPtoISO should now be whitelisted in Windows Defender also when running it in build 15061 regardless of language version.

For those few of you geeks who had issues with it being falsely flagged as threat: I am sorry for the inconvenience.

Getting current version whitelisted as told above, I am reluctant to make any changes before being absolutely sure the same circus does not start all over again with a new version.

However, that is a good idea which I keep on my mind.

Ha. Out of curiosity, do you think this would have occurred at all if it was just the set of scripts (whether cmd-based batch or Powershell or even VBScript) versus being an actual executable? I'm not knocking the executable at all, mind you, I'm just curious - as long as the tool does what it is supposed to I am all for it.

slicendice said:

I totally agree!

I have been planning on upgrading all these scripts to PowerShell modules and Scripts (because that is what MS want us to use in the future), and also create a GUI for those who does like more visual ways of doing things. Maybe even add some service that automates EVERYTHING regarding ISO creation from update files. Also planning on including a default configuration/settings file that could be easily modified, either by a PS script, manually or the GUI. This coding project would solve all the install/uninstall, missing upgrade files for proper ISO creation and other error, problems.

Another (actually main) reason, is that when I code .cmd files in Visual Studio, I get no proper intellisense, no auto completion, no proper code map and code assistance. This easily creates a lot of coding errors, a lot of confusion and no references can be automatically verified anywhere. Also most Shell scripting commands are extremely cryptic and confusing, and I like to have code that is self explanatory and very well structured. Like writing a book with a good and easy to understand story.

Using the PS scripts would not change how the tools look and feel. (well maybe a little bit ) Installer would ask what files/folders to put where and the uninstaller would ask what to remove and what to not touch during removal of the application.

What do you guys think about that?

I like what you're thinking about here.

I've never had a problem with making batch files, but have not really delved into making PS scripts because, well, my batch files still work

Going in a new direction is something I keep saying that I need to start doing, but alas, there are only 25 hours in a day....(pun intended).

Some ideas from me below.

M4v3r1ck said:

Sounds very promising to add a preferences pane to the installer! Will it be like "browse folder and select" for all install/ISO options?



You have my up-vote, GREAT idea to make this great tool much more user customizable and thus user friendly! I like that. [emoji41]

Cheers

I agree, customization is great.

____________________________

My ideas, some may be right along with your thinking, and some may be considered out of this world, but here goes.

1. I like the idea of the installer. It makes for easy versioning, easy use, and a lot of other things. The uninstall routine checking for items that it did not install being present in the directory is a great feature too. Could that uninstall routine be flagged to throw up a warning during uninstallation in the event that the files it checks for are found to the user so they know why the folder was not deleted?
2. It would be great for more customization options - Such as the actual script color. I cannot stand white on blue backgrounds, it bothers my eyes, I prefer light script on very dark gray or black backgrounds. I currently use and RGB value of 150/190/255 for the font color on black for my default color choices for the cmd.exe.
3. If you want to make the option on where to create the .ISO / install.wim file, that is good and all, but the reason I like this setup in the first place is that I, ever since the first ESD2ISO script that Kari released (and that I modified on my own to name the .ISOs the particular way that I wanted to) I have been running these scripts off one of my SSDs for obvious reasons. So, I would suggest that the script be automated to copy completed files that were generated after no errors to any custom location, and then give the user the option to deleted the generated file or not, rather than creating it in another location entirely. My storage locations are all mechanical drives, and I've found the script takes 2-3 times longer when running the scripts previously off of one of those drives versus one of my SSDs. So, a compromise would be to include both methods, allow users to change where the files are generated and allow the user to copy generated files to any location that they choose.
4. Is there any way to combine the 2 line items, such as a person who wants to make both install.wim and .ISO? Having to exit out and then run again is a slight PITA, at the very least, it would be beneficial if the script asks if we want to exit, or if we want to go back and start from the beginning again....(this is the one that most of you might think is 'out there').

Addressing other questions later, this one I wanted to say as soon as I read Johngalt's post above:

The whole idea of an installer and an executable running the script is to make it automatically appear in Start (to remove from Start, delete UUPtoISO folder in %ProgramData%\Microsoft\Windows\Start menu\Programs), make it possible to pin it to Start and Taskbar, automatically create a desktop shortcut, and make uninstalling from Start > Apps possible.

That's why UUPtoISO will remain an executable.

The colours come from abbodil1406's and rgadguard's original script and are easy to change. Will see what would be a good neutral colour combination.

That's what I meant by "a lot of other things" lol. I couldn't find the post where you had said that before.

Something else I have also stated before: anyone is free to download the original uup-converter-wimlib-5 script used in our tool or any other decrypter available on the InterWebs and do whatever changes they desire (scroll down to end of tut to Changelog, you'll find download link there). These scripts are not copyrighted intellectual property although you should give credits to fellow geeks on MDL if you share your modified script based on their work.

Those using UUPtoISO tool offered in this tutorial just have to take it as it is.

@johngalt - the console colours (font, size, layout, etc.,) are editable -



or Alt+spacebar, p from the keyboard:



If you plan on spending a lot of time looking at the UUPtoISO console - you can change many features this way.

regarding point 3:

The ISO file is created in the UUPtoISO installation folder - the location of which is user-chosen during the installation of the program.

Point 4 is also redundant since the ISO that is created contains the Install.wim file and it can readily be copied out of the ISO in File Explorer by mounting the ISO image - double-click in Windows 10 - and in the virtual DVD drive created, go to \sources\install.wim, and drag to the place you want to copy and save the install.wim imagefile to - the original ISO file will not be changed.

If you are impatient, once the install.wim has had the Winre.wim added, and as the ISO file is being created and checked, before pressing <enter> on "done" ,

UUPtoISO\ISOFOLDER\sources\install.wim may be copied to the place of your choice.

Fafhrd said:

@johngalt - the console colours (font, size, layout, etc.,) are editable -



or Alt+spacebar, p from the keyboard:



If you plan on spending a lot of time looking at the UUPtoISO console - you can change many features this way.

regarding point 3:

The ISO file is created in the UUPtoISO installation folder - the location of which is user-chosen during the installation of the program.

Point 4 is also redundant since the ISO that is created contains the Install.wim file and it can readily be copied out of the ISO in File Explorer by mounting the ISO image - double-click in Windows 10 - and in the virtual DVD drive created, go to \sources\install.wim, and drag to the place you want to copy and save the install.wim imagefile to - the original ISO file will not be changed.

If you are impatient, once the install.wim has had the Winre.wim added, and as the ISO file is being created and checked, before pressing <enter> on "done" ,

UUPtoISO\ISOFOLDER\sources\install.wim may be copied to the place of your choice.

Re: color - I already have my default colors set, but both ESD2ISO and UUP2ISO override my preferences for the colors, so I have to change them manually every time. I would like to be able to set it through the installation program as a permanent setting.

Re: user setting - I don't store my .ISOs in any script I have used to generate them since I joined the Insider Preview program. In addition, I store the .ISOs that I generate on mechanical drives because I don't use them all that often. Working folders for most of my apps, including UUP2ISO, aye on my much faster SSDs. I have previously modified the batch files to accomplish my own things like this copying / moving of completed generated .ISOs / files. A little harder to do that with the executable, so I asked for the option. If so, great, if not, I will write my own script for post-processing.

Fafhrd said:

@johngalt - the console colours (font, size, layout, etc.,) are editable -



or Alt+spacebar, p from the keyboard:



If you plan on spending a lot of time looking at the UUPtoISO console - you can change many features this way.

regarding point 3:

The ISO file is created in the UUPtoISO installation folder - the location of which is user-chosen during the installation of the program.

Point 4 is also redundant since the ISO that is created contains the Install.wim file and it can readily be copied out of the ISO in File Explorer by mounting the ISO image - double-click in Windows 10 - and in the virtual DVD drive created, go to \sources\install.wim, and drag to the place you want to copy and save the install.wim imagefile to - the original ISO file will not be changed.

If you are impatient, once the install.wim has had the Winre.wim added, and as the ISO file is being created and checked, before pressing <enter> on "done" ,

UUPtoISO\ISOFOLDER\sources\install.wim may be copied to the place of your choice.

Regarding your point #3 on the point #3........

User chosen or not, the Uninstall currently will delete the chosen or otherwise folder, ISO and all..... as it is currently written. My suggestion was to have a chosen destination for the ISO creation to avoid that possibility happening accidentally. Kari apparently understood what I meant. Maybe I misread his reply.

f14tomcat said:

User chosen or not, the Uninstall currently will delete the chosen or otherwise folder, ISO and all..... as it is currently written. My suggestion was to have a chosen destination for the ISO creation to avoid that possibility happening accidentally. Kari apparently understood what I meant. Maybe I misread his reply.

The uninstaller does not delete your ISO or install.wim. If they are in UUPtoISO folder when you uninstall, everything else will be removed but folder itself is left behind with ISO or install.wim.

This is to make it sure you do not accidentally delete ISO or install.wim.

I tried to explain it earlier, might be me not being native English speaker that the explanation is not clear enough:

Kari said:

The uninstaller is like that half-wit cousin most of us have: it only does what it is told to do having no brain to improvise. Uninstaller removes what was installed. If UUPtoISO folder contains anything not installed like an ISO or install.wim file you made, it removes everything else but leaves those files intact. Otherwise, when there are no additional files in UUPtoISO folder it removes everything, including the main folder.

This is to make it sure you do not accidentally delete your ISO before copying it to a safe location. Rather safe than sorry.

Kari said:

The uninstaller does not delete your ISO or install.wim. If they are in UUPtoISO folder when you uninstall, everything else will be removed but folder itself is left behind with ISO or install.wim.

This is to make it sure you do not accidentally delete ISO or install.wim.

I tried to explain it earlier, might be me not being native English speaker that the explanation is not clear enough:

My mistake. There are so many posts going back and forth from so many different people about so many different aspects of this, I simply missed that part.

All I really care about is that it works. And works well. Which it does.