x86 & x64 both are different arch & 26H1 has only x64 & arm64, no x86 for this branch (atleast as of now)
and soon ai hardware vs legacy non ai hardware and of course companies really want subscription based cloud hardware/software/services tiers
...after SFC and DISM /Online /Cleanup-Image (checking only queries in both cases) and new WU update check, the message has disapeared after 5 minutes. There are also the cases, which suggest, that this is connected to non-TPM Windows: https://forums.mydigitallife.net/th...windows-to-repair-files-and-components.88781/ WU Update clearly doesn't like non-TPM Windows. Any other hints, which other logs to check?
Well, according to MS, officially, non-TMP-Windows does not exist (except for Server and IoT versions).
Features-aside, is this build not superior to other builds for x64 architecture when it comes to security improvements and overall performance? It uses a newer hardware abstraction layer than 26x00 builds. Are there any gaming/non-gaming 26x00 vs 28000 benchmark results?
cleaner base, many things being updated on 25h2 are not very clean backports from bromine. you keep saying this, doesn't make it true. 28000 will supersede 26h2 as 27h2.
Read again. 26H1 can not be upgraded to 26H2, as 26H2 will be based on 26xxx, not 28xxx. Never said anything about 27H2.
26H2 is the normal continuing of the 24/25H2 branche, just the third year of the same base build. 26H1 is new core code and will be joined with 26H2 in probably 27H2, probably the other way around, 26H2 will be joined with what then still is 26H1 into a new major release in 27H2..
Honestly, looks like 26H1 is shaping up to be more of a platform/silicon-focused branch rather than something worth daily driving right now. From what I see, most changes are under-the-hood and not really user-facing. What I find interesting is: Still getting full app stack integration (Store, Edge, UWP packages, etc.) No major feature shifts compared to 25H2 Seems heavily aligned with upcoming ARM64 hardware rather than x64 users I’m more curious how this will transition into 26H2 — whether we’ll see a proper feature merge or if 26H1 remains kind of a “hidden base layer” for newer devices. Also wondering if anyone tested: Stability vs 25H2 as a daily driver Any performance differences (especially on older CPUs) Update behavior long-term (does it stay Canary-style unstable or smooth out later?) Running Canary builds like this on main machines is brave
No sh*t Sherlock. 26H1 is not a general release branch, it's a scoped release that only came out for the new ARM64 hardware. The x64 builds seem to be merely fallout and bring nothing new. MS recommends using 25H2 for non-ARM64 hardware. See above. 26H1 can not be upgraded to 26H2, as 26H2 will still be based on 26xxx branch builds. The merger will be 2027, with 27H2, eventually.
FWIW Been running/using this [26H1] since Dec25 from 2nd to 14th Gen (Intel) systems, w/out any issue, rather I'd say, better than 25xx branch IMO.