They have a UI team, but they work with the rest of MS on Windows GDI, hardware team, CBS, etc. There is no de-coupling the OS. It is the OS. They can make drastic changes more quickly on an insider build because they know it isn't final like an RTM and they can issue a patch if something is buggy, which they have already done many times. Yes, this insider build will get pushed into the next support ring when the next insider build becomes available. That's how it works. They're not just going to patch this one buggy build forever with duct tape. If you know how the CBS system works, you will know how much extra system space these files take up over time. They could technically turn Windows 7 into a super modern operating system by patching it enough, but it would be extremely bloated and defeat the entire purpose of using Windows 7. Microsoft is not that sloppy. They can compile a new build with the new source code. They have the power. They do it all the time. They literally do it daily. We just don't see the builds.
22000.x is a perfectly fine build for daily usage. It's stable, fast and everything just works. Only UI/UX stuff is still a bit wonky, but they're quickly polishing and fixing it up every week, and they'll continue to do that until October. As stated, we'll see this more clearly very soon (when 22000.x will hit Beta/Slow and also RP channels).
I think I've made my point by now. This is an insider build. They are using the suggestions to further development. The files are not uniform and complete like an RTM build. The OS does not identify itself as Windows 11 except with graphical modifiers. It's still a heavily modified Windows 10 at this point. It even uses the Windows 10 product keys. It's not finished or complete in any way. If you want to believe it's the final build, guys, go ahead. I'm done arguing.
Same here, but sadly this is another tweak that has stopped working or doesn't work properly - see main post. It's an Insider Preview so I guess no point complaining about tweaks ceasing to work! A few nice useful ones have ceased to work in current 20000.71
the build 22000 will soon be released in the beta channel, microsoft never released something in the beta channel that wasn’t meant to be in the retail channel at some point. they also never released that many updates for a dev channel release.
I think that the RTM debate nowadays is practically pointless. They publish a forced CU each month, they publish updated ISO often, they are providing updates for 22000 at a good pace. They aren't ashamed in forcing new features and forcing the removal of long standing features even in 10 years old OSes (see EDGE/EDGIUM and the RFX vGPU) So, what practically changes if the build they start to sell in October will be 22000.927 or 24000.1? Perhaps, (just a stupid detail) 22000 is a round number starting with 22 being twice as 11, which may matter. Once they where used to go with meaningful build numbers see Win98SE=2222, maybe they started again.
Well I don't think any of us can argue with detailed, well thought out and well reasoned assertions like that. ...No I mean that literally. Because there is nothing to back up that claim, and just because you think a thing doesn't make it so.
True, but it's the same thing. You can clean install 22000.1 right now while not being an Insider and get all the retail CUs up to GA at October without needing a re-install nor a full build upgrade...
I already talked about that a few posts back. It makes the OS extremely bloated to patch it that much and it doesn't make sense when they can just compile a new build with the new source code. By the time you patch something that much, every single package will have been patched. The entire operating system will effectively be the patch. Nearly every file will be replaced, even the servicing stack. Even the kernel might be patched at that point. You ask what practically changes? Everything.
I'm not on either camp of this discussion. Just I don't care. But, just for the sake of discussion, one can reply to you that as long they use mostly automated processes, they likely don't care. After all they are still maintaining things like LTSB2016 with updates as big as 2GB (which means 6.5 GB uncompressed) + all other streams. Having one more bloated update is not a biggie.
Why did they make LTSB2016 instead of 2015? Why LTSC2019? Why not just use the same build forever? If the build never matters and they just patch everything anyway, what's the point?
If you want my opinion, because they did an half baked job when they copied the rolling release model from Archlinux and alike. They had just to make some LTS builds every 4/5 years and a single rolling release build since 2015, releasing updated "convenience ISOs" each 6/12 months or so, and using semi-cumulative updates that spans just 6/12.months back. If you have a not updated OS (say) 24 months old, you have to use the latest "convenience ISO" and do an in place upgrade. Is that simple.
They could just release a 22000.250 ISO (with all CUs integrated) and final installation would still be identical to whom clean installed 22000.1 right down and then just updated Windows weekly with all officially released CUs.
They're working very hard and fast, releasing a CU (with a lot of fixes and improvements) every week so far.
Again, you must ask yourself. Why would they, when they could just compile a new build with no patches? The patches already have the new source code and to recompile would remove all the bloat. It makes no sense to not recompile.
Because manufacturers are testing and creating old and new devices and drivers with 22000.x as we speak, so to have everything fully ready and thoroughly tested when 22000.x will arrive for everyone. Compiling and sharing a newer build 1-2 month before GA, with so many changes to Windows compared to Win10, probably wasn't enough this time around.
Has anyone noticed that a fresh installation is super duper buggy ?? I made an ISO of 22000.71 from uupdump and made a UEFI Bootable USB using rufus. On performing a fresh install, so many things are broken. I Cannot right click on start to access Power Options, Cannot change Display Settings by right clicking on desktop. Both these context menus throw me into settings app main page but not to that particular setting. Setting app crashes when launching Power Options for the first time too. Remote desktop toggle in settings app does not work. Have to enable from classic settings where you enable/disable system restore. I have enrolled for beta preview builds of Office 365 (UWP version) but it does not download the latest build with fancy new Office ribbon UI. Most of setting toggles disappear. I got random BSOD (Black screen of death) after launching firefox and it was related to display driver error. I did not face any of these issues when I was on same build which was upgraded from 22000.65 Just found this strange that's all. Feedback hub is near useless as MS cares zero about such fresh install scenario so I won't bother.