Skip Ahead clean installation from ISO, the saga continues...

If the update works to me it sounds like there is an error in the program that builds the ISO.

Either it is configuring the data wrong or it is getting the wrong data.

It could also be the installation programming.

.

My updates to 17650.1001 went well on my 2 laptops.  One is from 2008.

If the update works to me it sounds like there is an error in the program that builds the ISO.

Either it is configuring the data wrong or it is getting the wrong data.

It could also be the installation programming.

Kari said that there's nothing wrong with UUPtoISO.

Making the ISO with uup-converter-wimlib-15 gives the same error.

Johnny tried every possible combination the last time and got the same results.

There must be something different about these last two builds that's causing the failure.

If there is something different about the builds then there may be a need to find out why the ISO making programs are not finding it.

Personally I have not made an ISO using the programs.  I have only used the updates or the ISO that were released by Microsoft.

If you can figure what it is it will help others.

If there is something different about the builds then there may be a need to find out why the ISO making programs are not finding it.

Personally I have not made an ISO using the programs.  I have only used the updates or the ISO that were released by Microsoft.

If you can figure what it is it will help others.

I wish I could but I don't have the knowledge to dig deeper. Only the makers of these utilities or somebody with programming experience may be able to help. 

Later today i have time to run tests with Different ways to create ISO's and test installations to blanco HDD. 

Is there some method you want especially be tested?

Did you use UEFI or legacy? I will run tests with same mode.

Later today i have time to run tests with Different ways to create ISO's and test installations to blanco HDD. 

Is there some method you want especially be tested?

Did you use UEFI or legacy? I will run tests with same mode.

ok thanks! I used legacy but Johnny already tried 17643 UEFI with same results.

Now I have made some test and here is my results.

HW: ASUS CM6330, i5-3350P @ 3.10 GHz, 8 GB, WD5000LPVT 500 GB

SW: Windows 10 Pro x64 en-US, Build 17650

I downloaded UUP's from different sources and converted with different methods to ISO

(UUP source + Converter)

1) SoftwareDistribution\Download + UUPtoISO,  4 220 497 920 Bytes
    Install.wim lightly different size than others

2) UUPDump Web page Download + Auto convert, 4 217 167 872 Bytes

    Boot.wim lightly different size than others

3) UUPDump Web page Download + UUPtoISO, 4 220 499 968 Bytes

4) UUPDump Web page Download + wimlib14, 4 220 499 968 Bytes

5) uupdl-master + wimlib14, 4 220 499 968  Bytes

From those I install 1, 2, and 3 (3, 4 and 5 are identical) and all succeeded perfectly.

HDD was completely erased with partition tool before each install.

It seems that reason for your problems can't be download source or used converter.

Time to chime in, I am getting the same result on my virtual machine in VMWare on Build 17650 along with 17643 on clean install. I did clean install build 17643 on my Toshiba laptop with no issue. That did work. I just upgraded the laptop this time to 17650 via ISO.

Like Pauli, I made 3 ISO's last night. Not sure if UUP Dump corrected their UUP files, as of last night, one could not make a successful ISO. I tried using both UUP Dump Web page Download Auto convert and UUP Dump Web page Download wimlib15. Another user on that site reported that the UUP files were short 2 files, as he compared them with the SoftwareDistribution\Download UUP files.

UUP Dump ISO                                     4,220,436,480

SoftwareDistribution\Download ISO    4,220,497,920

He posted the missing files and that allowed to make the ISO. I also made one with SoftwareDistribution\Download and UUPtoISO and I am still getting the same issue with VM. It upgrades just fine in VMware, just will not clean install.

Something has changed in these last 2 Skippy builds that VMWare does not accept on clean install. As a note, I had no issue clean installing Fast Ring 17134.1. Just maybe in my case, VMWare needs an update for the new code.

Hi Johnny, thanks for taking the time to keep testing.

Sorry, I forgot you did your previous testing on VMs, so I misspoke about hardware being different.

Still, when you said "I just upgraded the laptop this time to 17650 via ISO.", was that a clean install?