ISO file size discussion

The install.wim in the MS ISO is too big to fit on a FAT32, so I will have to convert it to install.esd.

Above the FAT32 limit of 4,294,967,296 

Hi fg,

Obviously, for users like you with many devices it isn't practical to download the ISO multiple times.

In my case, with only two PCs my preference is to install or update directly from my second SSD without having to deal with USB drives, file systems or sizes.

Hi Sibro,

I understand how the upgrade/update can be done directly from the mounted ISO, but it is not clear how you do a clean install from the second SSD.

What am I missing?

4 out of 5 of my UEFI machines can only boot from FAT. (FAT32 is what MCT uses for Windows)

I use FAT32 also when I prepare the USB for the Windows installer.

I only have one older UEFI machine than can boot directly also from NTFS, but that is just one out of 5.

I understand how the upgrade/update can be done directly from the mounted ISO, but it is not clear how you do a clean install from the second SSD.

What am I missing?

Mount the ISO, copy all the files to a temp directory on the second disk (SSD or HDD), shift + restart, troubleshoot, advance options, command prompt, change to the second disk, then cd temp/sources and run setup.exe

I understand how the upgrade/update can be done directly from the mounted ISO, but it is not clear how you do a clean install from the second SSD.

What am I missing?

Mount the ISO, copy all the files to a temp directory on the second disk (SSD or HDD), shift + restart, troubleshoot, advance options, command prompt, change to the second disk, then cd temp/sources and run setup.exe

Looks like I learned a new one today. 😉

I already copy the files from the mounted ISO to a folder in my D:\myiso in case I want to modify something before I upgrade/update, I guess I'll try what you just suggested for a clean install.

I'll let you know how that goes.

Weird that you mentioned earlier that in one case you were trying to update/ugrade and ended up with the install setup. I haven't seen that one either. 😏

Right now, I'm trying repair/update 22579 to 22579 with MS ISO to see if I get that loop on W.U. after that.

I suspect it was s problem left over by previous Ni builds, because I have not seen it after 19044.1618 to 22579.1 with the same ISO.

We'll see how this goes.

Edit:

It just finished repair 22579 to 22579 with MS ISO, everything looks fine this time, no loop on W.U. on this one.

Looks like I learned a new one today. 😉

Right now, I'm trying repair/update 22579 to 22579 with MS ISO to see if I get that loop on W.U. after that.

I suspect it was s problem left over by previous Ni builds, because I have not seen it after 19044.1618 to 22579.1 with the same ISO.

We'll see how this goes.

We all learn new things from each other every day. 👍

Good luck! keep me posted.

Edit:

It just finished repair 22579 to 22579 with MS ISO, everything looks fine this time, no loop on W.U. on this one.

Did you refuse updates?