Share via

Public Windows 11 ISO (_v2) contains build 26200.x and is missing identity components (WAM, WinRE, Store dependencies)

David K Hill 0 Reputation points
2026-03-21T16:53:15.9766667+00:00

Description: I encountered a significant issue with the Windows 11 ISO currently published on the official Microsoft “Download Windows 11 Disk Image (ISO)” page. The ISO labeled with the “_v2” suffix appears to contain a 26200.x build instead of the expected 26100.x retail 24H2 build. The ISO is checksum‑valid but appears to be a servicing build that is missing key identity components.

Details and Reproduction Steps:

  1. Downloaded the Windows 11 ISO from the official Microsoft public download page (not the Insider ISO page).
  2. The downloaded file name included the “_v2” suffix.
  3. Mounted the ISO and inspected sources\setuphost.exe and install.wim metadata.
  4. Both reported build 26200.x, not 26100.x.
  5. Performed a clean install from this ISO.
  6. After installation, the system was missing multiple identity‑related components:
    • WAM (Web Account Manager)
      • Identity provider stack
        • WinRE
          • Store sign‑in functionality
            • Store catalog population
            1. DISM could not restore these components because they were not present in the ISO source.
            2. Attempting a repair install using the same ISO failed because setup.exe immediately exited after elevation (version downgrade block).
            3. Reinstalling from an older, known‑good ISO (26100.1591) restored all components successfully.
            4. After reinstalling from the correct ISO, Windows Update upgraded the system to 26200.x again — but this time everything worked because the base image was complete.

Impact: The _v2 ISO published on the public download page appears to be a 26200.x servicing build missing identity components. This ISO is not suitable for clean installs and results in a system that cannot sign into the Store, cannot use WAM‑dependent features, and cannot be repaired using in‑place upgrade methods. This caused several hours of troubleshooting before determining the ISO itself was incomplete.

Expected Behavior: The public Windows 11 ISO download page should provide the stable retail 24H2 build (26100.x) with all required components present.

Actual Behavior: The ISO provided appears to be a 26200.x build missing identity components, leading to incomplete installations and broken system functionality.

Windows for home | Windows 11 | Install and upgrade
0 comments

4 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. ChrisSolomon 31 Reputation points
    2026-06-14T07:16:57.0566667+00:00

    I can confirm what the OP is reporting. after doing a repair install using the 'v2' 26200 iso, my system is royally screwed due to servicing mismatches. Not even an older 26100 (24H2) iso is able to fix the issue. i am trying to find the 26200.1 iso, or whatever the version that 25h2 was when they first had it for download of the iso, but it looks like MS pulled all the links to it.

    DO NOT USE the following windows 11 iso: Win11_25H2_English_x64_v2.iso.

    Was this answer helpful?

    0 comments
  2. CrazyKats 15,875 Reputation points Volunteer Moderator
    2026-03-31T21:11:04.85+00:00

    Hi David,

    ==partial quote==

    User's image

    Retail 25H2 has been released to the public,

    so the version 26200 that you are getting is

    correct.

    Was this answer helpful?

  3. Lucus-V 8,420 Reputation points Microsoft External Staff Moderator
    2026-03-31T20:55:18.3033333+00:00

    Hi David K Hill,

    I really wish I could assist you directly on this issue. However, the behavior you're experiencing is tied to back‑end systems and service functionality, and unfortunately, we don't have the authority or access required to investigate or make changes at that level.

    Please note that this is a user-to-user support forum. Moderators, contributors including external Microsoft employees cannot directly intervene in Microsoft product features or access back-end systems. Our role is limited to providing technical guidance on reported issues, requests, or ideas.

    Given these limitations, the most appropriate avenue for product changes or feature requests is to contact Microsoft Support.

    Thank you for your understanding, and I hope the support team can resolve this for you soon.

    Was this answer helpful?

    0 comments

  4. AI answer

    2026-03-21T16:53:30.4833333+00:00

    The described behavior matches a known class of issues where specific Windows 11 24H2/26200 builds have defects or regressions that are later corrected in newer builds or by reinstalling from a corrected image.

    From the available information:

    1. The stable, supported 24H2 retail images are 26100.x builds, as reflected in the published client image documentation. For example, the Pro images for August, September, and October 2025 are all 26100.x builds with cumulative updates such as KB5063878, KB5065426, and KB5066835 applied, and they include the expected servicing stack, SafeOS, and .NET components.
    2. When a system is installed from a known-good 26100.x base image and then updated to a 26200.x build via Windows Update, identity‑related functionality (including Store sign‑in and WinRE) works as expected, which aligns with the behavior described after reinstalling from the 26100.1591 ISO.
    3. For WinRE‑related defects specifically, there is a precedent where a regression existed in early 26200.x builds and was later fixed in a newer 26220.x build (the WinRE USB keyboard/mouse issue was fixed in build 26220.7262). This shows that some 26200/26220 builds have shipped with platform‑level issues that were subsequently corrected in later builds.

    Given this, the correct remediation path for affected systems is:

    1. Avoid using the problematic “_v2” ISO for further clean installs.
    2. Perform a clean install using a known-good 26100.x 24H2 image (for example, one of the documented 26100.x Pro images) that includes the full component set.
    3. After installation, allow Windows Update to move the system forward to newer builds (such as 26200.x or later) where identity and WinRE issues are resolved while preserving the complete base image.

    Because the public download pipeline and ISO composition are controlled by Microsoft, any issue where the public ISO carries an unintended 26200.x servicing build or is missing identity components must be corrected on the service side. The appropriate action is to report this through official support or feedback channels so that the public ISO offering can be replaced with the correct 26100.x retail image and any incomplete servicing image can be withdrawn.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.