New
#330
It works perfect even with Japanese versions and I did successfully upgrade my 15048 to 15055 without any problem.
Kari, SlicEnDice and other active people are very much appreciated for this great job.
Two small things that I noticed:
- "ISOFOLDER" is left behind after a job done and the UUPtoISO.exe was closed if it is installed somewhere other than the default folder "c:\UUPtoISO".
- If an explicit distinction between x64 and x86 was included in the ISO file name it will be helpful.
Again, thank you everyone here for the great product.
You are so nice that I cannot find good English words to express it.
Kintokki
True.
There's nothing I can do for this, the decrypter script does as good work as possible but due the nature of UUP upgrade and method used to create ISO from upgrade files, the repair option is be missing in selfmade ISO images.
Here's a screenshot of the last officially released Insider ISO, original from Microsoft. Repair option is there, on bottom left corner:
The same screen when booting with a selfmade UUPtoISO image:
However, the selfmade ISO will be fully functional in every other aspect. If you really need to use recovery / repair option at boot, download the latest official Insider ISO from Microsoft and boot PC with that, or when booting from your selfmade ISO and getting to above screen, press SHIFT + F10 to open Command Prompt. Recovery / repair tools will be available.
I will fix this in next release of UUPtoISO.exe. I noticed that the bit version was still included in file name in my tests on Saturday, and no longer there in further tests on Sunday:
I just have to trace the change to something I made between Saturday and Sunday.
Kari
As @Kari already stated, this is one of the tiny differences of a self-made ISO and an official Microsoft made ISO.
The difference is in how the boot.wim and install.wim are layed out. Our self made ISO has only one "image" in each, while the official ISO has 2 "images" contained in each.
The official boot.wim contains Microsoft Windows PE at index 1 and Microsoft Windows Setup at index 2.
The official install.wim contains full Windows (Pro, Home or whatever edition you have) at index 1 and a Core version at index 2, which I suspect is for the repair option (no GUI).
As far as I am aware, Windows 10 can not be installed as a Core edition though I can see how that could be useful too, while Windows Server 2016 can. I could be very wrong though.
I also noticed that some SxS packages and some fonts are left out from the official Windows ISO when compared to our home-made ones.
Okay, I think I figure out the why the ISO name is missing "X64" part:
Just change the code (if you're using the original one) from:
if /i %arch%==x86_64 set arch=x64&set archl=X64
To:
if /i %arch%==x86_64 set arch=x64
if /i %arch%==x64 set archl=X64
I did and the problem went away.
Please forgive me if I am in the wrong place!