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: Newest
  1. Anonymous
    2022-03-21T00:37:20+00:00

    btw: look how much bigger a 3rd party arm64 ISO is compared to amd64 but is still missing all apps and else.

    Image

    Something has changed on the files they download; they need to figure out how to get the whole new package that includes all the basic Apps. The same issue with the converter scripts for the files downloaded in SoftwareDistribution.

    Till then, I'll stick to W.U. or the MS ISO. 😉

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  2. Anonymous
    2022-03-21T00:02:36+00:00

    Hi fg,

    Upvoted!

    Ironically, I did an in-place update of .579 from Home Edition (installed with official ISO) to Pro using a 3rd party ISO, I refused the updates and didn't get the loop. I know this is a different situation but reflects the inconsistency of these .Ni builds.

    The reason was that I mounted the official ISO by mistake and ended up with Home, the original OS of this laptop. I like to use 3rd party ISOs with Pro Edition only so I don't have to upgrade via the Store which sometimes doesn't go well.

    Hi Sibro,

    Hope that helps.

    I did one 22579 to 22579 earlier with official ISO refusing the updates and that worked too, seems to have a mind of its own on different machines, also depending on previous updates.

    They sure have a bug, but not easy to isolate when it happens. 😎

    It just confirms the inconsistent behavior. 🤷‍♂️

    The one that failed earlier with ISO from 22572 to 22579, I just restored it and did it again with W.U. and everything is fine. No loop or error. 🙃🙃

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2022-03-20T23:57:51+00:00

    btw: look how much bigger a 3rd party arm64 ISO is compared to amd64 but is still missing all apps and else.

    Image

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2022-03-20T23:47:30+00:00

    Hi fg,

    Upvoted!

    Ironically, I did an in-place update of .579 from Home Edition (installed with official ISO) to Pro using a 3rd party ISO, I refused the updates and didn't get the loop. I know this is a different situation but reflects the inconsistency of these .Ni builds.

    The reason was that I mounted the official ISO by mistake and ended up with Home, the original OS of this laptop. I like to use 3rd party ISOs with Pro Edition only so I don't have to upgrade via the Store which sometimes doesn't go well.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2022-03-20T23:10:31+00:00

    Hi Sibro,

    Reproduced this error again using MS ISO to upgrade from 22572 to 22579, used the recommended way, letting it check for updates normally.

    It still ended up with the W.U. loop and error 0Xc1900401.

    I submitted a FBH report with recording.

    Needs upvotes. 😉

    https://aka.ms/AAgc8c2

    Build 22579+, W.U. gets error 0Xc1900401 after Upgrading from 22572 to 22579 using MS official ISO, the error keeps repeating on every retry.

    Was this answer helpful?

    0 comments No comments