New
#510
Small point - when I uninstalled uupto iso, it did not remove all folders so I had to manually delete them afterwards.
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 has mentioned this before:
The uninstaller does not remove files created after the tool was installed. If you have new files in UUPs folder, then that folder will not be removed.
Maybe at some point we create an uninstall script that removes all files and folders from the install folder tree...!?
EDIT: aaah.. @Kari got to this just a split sec before me. Sry for double post. :-D
@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
InformationUUPtoISO 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.
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?