Has anyone seen this ? I was on 22531.3668. (23H2) I got an update thru Windows Update and now I'm on 26100.712. (24H2)
so? patch 22531.3668 is from RP channel, and 26100.712 was released on that RP channel, so you got an upgrade
Im 3668 but no option to update to 26100.712-why? is there any reasons or have to choose to particular language in list?
As @Paul Mercer said before: He was enrolled in the RP channel on 23H2, 24H2 is available in the RP channel, so WU offered 26100 and it installed.
also if the system requirements are not met, it won't be offered in WU and it could be anything like disabled TPM, enabled csm mode in bios and so on, anyway there is always an option to upgrade from ISO
Aren't the currently released IP TB ISOs any good? Public release will just be with another update integrated in 26100.1
I also noticed that when I installed it in a VM earlier today (LTSC 2024 26100.1), strange, never seen Windows leave a Windows.old folder when clean installing.
It seems that the new installer has the problem. The traditional installer installs without defaultuser0 and window.old.
Yes, now that you mention it, I recall seeing an option for the traditional installer but I never clicked it. Will try that next time. Loving every minute of the new Windows 11 24H2 LTSC 2024, yummy yummy!
Why requesting ISOs you can simply find here: https://forums.mydigitallife.net/th...4h2-dev-ge-release.88220/page-32#post-1837190 If it isn't listed there, it doesn't exist, IP ISOs are released in just 24 languages instead of the MVS ISOs in 38, for missing languages use UUP dump or integrate language files or change language after install.
They jumped from 22631 to 26xxx and skipped builds such as 22635? Is this another case where security updates from 22631.3668 are not in 26100.712? I think 24H2 is the first Windows release with parts of kernel coded in Rust. It should be a security improvement overall... 26100 ISO is also much smaller in size comapred to 22631.
There is currently an issue impacting visibility of the upgrade offering through WU for those on the RP Channel on 23H2. Microsoft is aware of the issue, but you can also upgrade via ISO in the meantime. Official release of 24H2 is in ~June for new ARM64 devices and ~September for most of the world/general release I have noticed that as well. It shouldn't have any negative impact however. 22635 is just 22631, which is just 22621. These are just different variations of feature enablement, but are essentially the same thing. You will get security updates for both 23H2 (226xx) and 24H2 (261xx) from now until years to come. The ISO is smaller because of the way KIR (known issue rollbacks) work, which gets reset whenever a new major Windows release happens. Don't worry about it.