ISO file size discussion

Anonymous
2022-03-19T19:40:07+00:00

Split from this thread.

@Sibro,

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

Windows Insider program | Windows Insider preview | Install, activate, and Windows update

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

66 answers

Sort by: Most helpful
  1. Anonymous
    2022-03-20T01:20:49+00:00

    Hi Sibro,

    I tried the clean install as you suggested, it worked, but the Out of Box Experience process did not look like the latest one as I saw doing it from the normal installation media.

    It still looked the same as it always did in the past.

    When I set up the offline account it asked for the password and the 3 security questions as it always used to do.

    When I did it from the USB installation media it skipped asking for the password and the security questions and ended up setting up the offline account with no credentials.

    I'll have to try again to see if it is consistent.

    Changes in behavior make me suspicious. 🤔

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2022-03-20T00:59:32+00:00

    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?

    No, I let it do the normal check, but that was still failing when I tried 22572 to 22579 with this ISO.

    In this machine I did:

    A) 19044.1618 to 22579.1 with MS ISO with check for updates.

    B) 22579.1 to 22579.1 with the same ISO with check for updates.

    All completed fine and happy, no W.U. loops and no errors.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-03-20T00:40:48+00:00

    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?

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-03-20T00:15:20+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-03-20T00:07:28+00:00

    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.

    Was this answer helpful?

    0 comments No comments