[DISCUSSION] Windows 11 Build 26x00 (PC) [24/25/26H2 Retail- GE-release]

Discussion in 'Windows 11' started by Enthousiast, Apr 3, 2024.

  1. Quazzi

    Quazzi MDL Novice

    Feb 18, 2010
    6
    5
    0
    To remove the watermark search control panel --under Ease of Access click Optimize visual display--under "Make things on the screen easier to see" put a checkmark on "Remove backround images (where available)"
     
  2. Quazzi

    Quazzi MDL Novice

    Feb 18, 2010
    6
    5
    0
    uwd2 stopped working for me some months ago on 26300 but the method I posted works (up to and including build 26300.9032)
     
  3. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    55,471
    128,271
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  4. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream
    Staff Member

    Dec 21, 2012
    8,192
    10,518
    270
    In this case... Have a nice weekend!
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  5. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,724
    100,772
    340
    It's test builds for a reason, it's only for testing and will never be production
    26H2 retail will also be 26100.1
     
  6. W_fantasma

    W_fantasma MDL Senior Member

    Apr 10, 2012
    339
    277
    10
    #6227 W_fantasma, Aug 8, 2026
    Last edited: Aug 8, 2026
    Boe something, its you? :rolleyes:

     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  7. boe323

    boe323 MDL Guru

    Jul 19, 2011
    2,004
    676
    90
    That's not me lol
     
  8. petok

    petok MDL Senior Member

    May 4, 2009
    364
    228
    10
    You misunderstood my question. I no speak for HAL and kernel.
    I just asked because I saw in the last checkpoint update that there was a change from 26100.2 to 26100.6. Others may notice that too. I know how these versions work, but it seemed strange to me. They started with .2 as the starting point and with the latest updates they changed the starting part from 10.0.26100.1742 to 10.0.26100.1743 and now to 10.0.26100.1746.
     
  9. zlpx9CXRTuseQ52it8dP

    Jul 8, 2026
    24
    3
    0
    Thank you for the correction. I just noticed that too. What I'd like is to know is whether they actually made changes to those lower layers of the OS or just changed some numbers around.
     
  10. steven4554

    steven4554 MDL Expert

    Jul 12, 2009
    1,855
    3,876
    60
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  11. zlpx9CXRTuseQ52it8dP

    Jul 8, 2026
    24
    3
    0
    Does it follow the same pattern? Previous, non-watermarked 26220 and 26300 builds did use 26100.1 base, but then they switched to 26100.2 and now 26100.6. I think MS will back-port that newer 26100.6 base onto public builds when such builds come out later this year.
     
  12. petok

    petok MDL Senior Member

    May 4, 2009
    364
    228
    10
    #6233 petok, Aug 8, 2026
    Last edited: Aug 8, 2026
    Here’s what I’m trying to point out regarding the latest test update, KB5122055 (26100.1746):
    When 26H2 is finalized, this update—or the next modified Checkpoint update based on it—will likely be required as a prerequisite for receiving subsequent system updates.
    This is similar to what happened with 24H2 and KB5043080 (26100.1742), which had to be installed first before the system could accept the following updates.
    In other words, KB5122055 (or its next modified Checkpoint revision) would serve as the required baseline before further 26H2 updates can be installed.

    Code:
    <assemblyIdentity name="Package_for_RollupFix" version="26100.1746.1.3" processorArchitecture="amd64" language="neutral" publicKeyToken="31bf3856ad364e35" />
      <package identifier="KB5122055" releaseType="Security Update" restart="possible">
        <mum2:customInformation Version="10.0.26100.1746" xmlns:mum2="urn:schemas-microsoft-com:asm.v3" PackageFormat="PSFX" PSFXVersion="2" PSFXDeltaFormat="ForwardOnly" ExpressType="Baseline" />
        <parent revisionCompare="GE" integrate="standalone" disposition="detect">
          <assemblyIdentity name="Microsoft-Windows-CoreCountrySpecificEdition" version="10.0.26100.6" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-CoreEdition" version="10.0.26100.6" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-CoreNEdition" version="10.0.26100.6" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-EnterpriseEvalEdition" version="10.0.26100.6" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-EnterpriseGEdition" version="10.0.26100.6" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-EnterpriseSEdition" version="10.0.26100.6" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-EnterpriseSEvalEdition" version="10.0.26100.6" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-EnterpriseSNEdition" version="10.0.26100.6" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-EnterpriseSNEvalEdition" version="10.0.26100.6" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
          <assemblyIdentity name="Microsoft-Windows-ProfessionalEdition" version="10.0.26100.6" processorArchitecture="amd64" language="neutral" buildType="release" publicKeyToken="31bf3856ad364e35" />
    


    24H2 (26100.1) → KB5043080 ( 26100.1742 ) → required baseline → next updates
    this short pattern:
    24H2 ( 26100.1 > 26100.6 ) → KB5122055 (26100.1746) → + Feature Update for Windows 11 26H2 via Enablement Package → required baseline → next updates
     
  13. abbodi1406

    abbodi1406 MDL KB0000001

    Feb 19, 2011
    18,724
    100,772
    340
    That's what testing branches/versions are for, eventually the changes is backported to retail/production branch, and make Win11 more miserable
     
  14. Mooniversal

    Mooniversal MDL Member

    Jul 9, 2020
    121
    69
    10
    > make Win11 more miserable.
    not really. it's only gotten better. 26100 at launch was crazy buggy. now? stable
     
  15. Carlos Detweiller

    Carlos Detweiller Emperor of Ice-Cream
    Staff Member

    Dec 21, 2012
    8,192
    10,518
    270
    It depends on what you expect from an OS. Personally, I want a solid, stable base for everything I run on it. What I don't want is AI, Cloud, excessive eye candy, loss of control of updates and settings, forced Telemetry, Store, and many more superfluous things. These additional features should all be optional.

    About stability: Why can't they do some more tests beforehand, and release a stable OS out of the box? Why does every new version have to be a buggy mess at first, and need multiple months to become usable?
    IMO, WaaS is utter bullcrap for a Desktop OS. Many problems arise exactly because of the many crammed-in features, and thus complexity. The KISS principle should apply here, a minimalist base OS that's easy to stabilize, with everything not essential coming as package to add. Don't they now have a fancy package manager exactly for that?
     
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  16. petok

    petok MDL Senior Member

    May 4, 2009
    364
    228
    10
    Respect, bro. You said it perfectly!

    I want this too—a clean Windows system without unnecessary nonsense. If someone wants add-ons or extra features, give them the option to choose what they want and install it. Keep the base system clean and let users decide what they need.
     
  17. EPRob

    EPRob MDL Expert

    Jul 23, 2009
    1,548
    768
    60
    Same with Server SKUs
     
  18. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    55,471
    128,271
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...
  19. Enthousiast

    Enthousiast MDL Tester

    Oct 30, 2009
    55,471
    128,271
    450
    Stop hovering to collapse... Click to collapse... Hover to expand... Click to expand...