Really, in what mental condition do people have to be to complain 6 year after a build was released or leaked that it is not listed? Please look at the surrounding posts about the previous and next ones, not much content in them. The lists were maintained by @Tito and the threads by forum members up to the time that some started a new thread for every "expected" to be released build based on speculation and questionable tweets and such. That's when @Tito also took over the threads about released/leaked builds and over time made them a bit more informative/comprehensive, next i took over at build 14388, the index post i took over from build 18312. The index list is based on MDL forum threads started for the build, so no factual stuff to discuss, no thread, no listing.
Does anyone know which windows service or task is responsible for modifying changes made with vivetool? If I turn on a feature while disconnected from the internet, the change will persist (tabs, suggested actions). However, once I connect to the internet and restart the device, the changes revert. I'm just wanting to stop the windows task that changes those feature store values back. I used to have this happen with the "settings banner" in windows 10, and never did find what it was.
I do. So? EOS (because it's technically EndOfSupport, not EndOfLife) means frozen build, and automatic windows update jumping to next supported feature update (unless you block it). And while for most versions, editions and licensing is trivial to workaround (changing product key, update, revert product key), for others, not so much. Stay on your lane These hocus-pocus remote changes by microsoft happen via WNF, which is a passive kernel listener. The Windows Feature Experience Pack (CBS App) subscribes to such notifications and then switches features depending on whatever is set for your device / version / region / insider preview channel configuration, server-side. And don't even try messing with it, as you're gonna gimp your install (it goes deep into shell start, taskbar, search, explorer, input spyware helper). There's also another WNF-based parallel updating mechanism for quick fixes / reverting updates and even A/B tests, but it's less used.
Did a clean install using the techbench ISO and it updates fine and works great. I am staying away from UUPDUMP from now on. I understand it works for some and it doesn’t work for some and I am one of the ones where it does not work reliably for me. There is something buggy with the script that puts it all together into an ISO and I am done dealing with updates failing.
You still don't realize that every online update (except NDP) and upgrade you get offered by WU is done via the UUP system?
I never had a problem with UUP until Windows 11. I am just posting my findings and it is consistent with others here.
I also only blamed how the ISO is constructed with adding in the LCU updates to the image. Something goes wrong with that process with the Windows 11 base image which is different from using the techbench ISO and applying the LCU after.
We have seen this for a couple of years now with INSIDER PREVIEW stage updates, not all are 100% created with the needed files, they need some base files from the running install to be able to properly install, any kind of online cleaning up caused this in the past, now maybe the updates are even more dependent on that or just dodgy.
The techbench ISO is the same 22621.1 + updates as UUP dump creates, maybe MSFT does it the audit>install updates>badly sysprep>capture way (like they did with 19042+) but the base is the same.
I understand all of this. All I am saying is whatever stupid s**t Microsoft is doing with these latest updates do not work right being integrated into the image the way they are currently being done. This is not all on UUP and probably is Microsoft’s fault but something needs to change to avoid these errors because it is annoying at the end of the day.
Thanks for answering this! Do you know if there is a known way to block that app (CBS App) from making the changes? Like adding it to the firewall? The only thing I do that causes them to revert is connect to the internet. I realize this isn't the thread for this, it's something I'm interested in but can't find a whole lot of info on.
You can uninstall Feature Experience Pack altogether. But then, will the features you need work without it? I'm not that curious to find out (and then having to do a repair install). You're not supposed to neuter WNF. You can fake a notification broadcast - that's what Vivetool does among other things. But that does not stop the original callback in some dll to broadcast a different configuration at a later time. And Vivetool is already "bleeding-edge" for insider builds, you're probably asking too much - a persistence / resilience option can do more harm than good, and manually blocking stuff screams undefined behavior elsewhere. Why not use the 22622 beta builds that microsoft just made specifically for those craving the longer A/B testing stick? (plus using en-us language + us region since that's a very high factor)
Now updated (though WU) to 22622.290, and am still not seeing tabs in File Explorer. Also, according to the blog about this update, middle-clicking a folder in file explorer should open it in a new tab, but again nothing happens. Is the tab feature still only switched on for some users?
the new vivetool 3.1 is persistent through reboots, its sets a service much like microsoft does task scheduler microsoft/windows/flighting /feature config/disable reconcile features, dont delete.