probably not, they usually upload Beta/Dev/Canary builds , 4 builds in an day would be chaos for their servers
hi, i ve found a strange problem with build 22631.2338/2359. it was actually build 22621 converted into 22631 with package enablement tool "windows11.0-kb5027397-x64.msu". anyway, the problem is when i do "chkdsk /scan /perf /f c:" via cmd or terminal as admin privileges it says normally "Would you like to schedule this volume to be checked the next time the system restarts?" after this check up completed in the next boot, everything activated via package enablement tool kb5027397 reversed. for example, file explorer returns 22h2 version and notification gong near time disappeared. Meanwhile in system about section it still says 23H2 and build 22631.2338/59.uninstalling and installing package enablement tool one more time doesnt fix this problem. Can you guys try it too? but i strongly advise creating a system restore point before doing this, thnx
23H2 will be the last of Win11 then next year fall 2024 Win12, Win11 will be a 2-year OS just like Vista, Win10 was around for many years likely Win12 will be for many years.
Sounds like feature set got corrupted and wasn't recovered, you will have to wait for the servers to refresh or you can do an inplace upgrade/repair if you dotn like waiting..bare in mind thr repair might not give all features back until server is refreshed also
Does anyone notice this bug ... in the latest Windows 11 Press the `end` move the sound bar to 100% while in Windows 10 it moves to 0% and kill all the sound like we saying ... it's not a bug - its feature
Just wondering Is there any point in waiting for the actual 23h2 ISO? I mean it's the same as 22621 anyway so enablement package should do the exact same thing? When it's out officially you should receive updates the normal way?