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.
Just created 26100.1 ISO from UUP, and noticed there's a new extra '__chunk_data' file without any extension inside the ISO Never seen this file in any other version of Win10/11 ISO earlier for example, this is the ISO files from Win11 23H2 Retail
When I enable ACM, animations get stuttering and slow. Is anyone else experiencing this? GPU drivers are up to date.
alright, so I am not the only one seeing this, that's what I wanna confirm. @abbodi1406 just a thought, could it be something related to the uup_converter process, creating this file?
dont even know where that setting is lol ill be moving back to beta shortly ...this build is so bland in comparison to features
I don't get why you people are so into creating your own custom ISOs with 3rd party tooling but you do you. FWIW, the __chunk_data file is present in Microsoft's official Windows Insider 24H2 ISO, it has nothing to do with whatever tools you use. ACM is Auto Color Management, which was introduced in 22H2 but is expanded to SDR displays in 24H2.
haven't downloaded any officially published MSFT ISO for the last 4/5 years, & been creating custom ISOs from UUPD for so long. So, not aware of this. If that file existed there too in the official MSFT ISO, then it has nothing to do with uup converter. I redacted my statement regarding that. Once you'll get used to the Custom ISO, you'd not ask this same Q again. It's about convenience & preferences.
.712 is essentially the Releae Preview equivalent of the (Retail) Preview/optional monthly updates for May 2024. We won't get another round of bugfixes in the RP Channel until around June 13th or later, at which point we will get the RP version of the June 2024 optional monthly update. I am building custom ISOs all the time, both for work and for some personal uses, e.g.. I have build a variant of last night's official 26100 ISO injected with the driver packages for my Surface Laptop Studio for both Windows and WinRE, so I can clean install with the same amount of integration work that the official recovery images provide. But that doesn't require 3rd party tooling and scripts, it's mostly just using DISM What I don't get is doing custom work for DIY (desktop) systems or just to integrate some Windows update that WU would catch after installation anyway. But I don't want to derail this thread, if that makes you happy that is great.
If you're building 'custom ISOs all the time' this what're you talking about? Your earlier statement contradicting here. & where did I say anything about any '3rd party tooling and scripts' like you said? I created the 24H2 ISO today for the first time, noticed the file for the first time, so asked, That's all. & didn't I already say that I have withdrawn my statement about the UUP converter that I mentioned in my earlier comment?
I hope that's not the case, it would be weird for Microsoft to not give Release Preview users bug fixes for multiple weeks
There is actually a subtle difference between installed edition and changed edition language after installation. Even the installed edition can be switched over in the registry but doing so is asking for trouble if not done very clean. I would always install the en-us as base for maximum compatibility and change languages as required after installation especially during upgrades.