It's called "selective reading". I don't have time to read every post, so posts are quickly prioritized, and some posts remain unread. But I am curious about what servicing channel is attached to installing a UUPDump ISO by default, since some of the UUPDump components seem to come from the release-preview channel. Is it the general availability channel or the release-preview channel that is configured by default for the 21H2 components?
Nonsense. Blindness has nothing to do with it. It's a waste of time for me to read EVERY post. It's not a sin to re-discuss some issues, even if you are the only one that remembers something being discussed in the past. On the issue of which servicing channel is configured by default, it's the release-preview channel. Note: 19044.1862 was never offered in the GA channel. Of course an immediate retail install or release-preview install would be 19044.1865 NOW, because it's NOW offered to the GA channel. But before 1865 was offered, there was no install of 1862 in the GA channel.
Seriously? Your request is unreasonable. This issue occurs once after an install, and you want Nosirrahx to completely reinstall Windows 10 from a UUPDump ISO, and then run Windows Update and then video capture the redundant install of the latest LCU and then waste MDL bandwidth by posting it here. The irony is that you want him to do this after making the following statement: "This has been discussed many times." If it has been discussed many times, then the issue has already occurred many times. This makes your request unreasonable.
How come i can document the scenarios over and over and others who claim all kinds of stuff never can? The re-offering of the LCU is occurring because something is changed after the integration of the LCU, not because it was an uup dump or mvs or techbench iso. And yet "selective reading" managed to miss all reports and replies.
Actually, you don't do a very good job of documenting scenarios. If you did, issues would not continue to come up after you think you've completely documented them. When an an in-place upgrade is performed with an ISO that's configured for the rp update channel as default, right over the top of an online image that's set for the ga channel, I suspect that this causes the update server to reinstall the last LCU. But it could also be something else, as well. As long as Windows 10 operates correctly, it's not a huge issue. But UUPDump doesn't do a very good job of identifying the update channel that's going to be configured by default. One can easily click on 21H2 and end up with a list of builds that don't clearly identify what update channel you'll be in.
Of course i don't, i showed you 2 videos but as usual you don't acknowledge them. Maybe next time i will draw a cartoon of it. ISOs are not preset for RP channels. UUP dump doesn't set ISOs to any channels.
It looks like in the "ps" to the following link that you're saying that you did an inplace upgrade and enrolled in the RP channel. So what do you mean by enrolled in this context? https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-696#post-1747862 There has been no time that I've installed Windows 10 from any source that I have not been automatically enrolled in some default update channel.
I said I've enrolled into the RP channel to see if any LCU would get offered in there because in the retail channel nothing got re-offered.
Why would anything get re-offered at this point? The GA and RP channels are both on 19044.1865. Wow, what a surprise, no re-offering!
W10UI currently handles 22H2 EP on Windows 10 LTSC (19044), which occurs error 0x800f081e. needs fix?
No, a LTSC release is meant to stay on the major build it was released on, 19044.xxxx, it doesn't get feature updates no real ones nor fake ones like by EP.
It definitely doesn't cause any problems because it can't. Every time I look into this the one and only change to my system is the creation of a new folder in the LCU folder.
Yeah I can grab some screen shots. I did some testing of Windows 11 the other day on a system that is going back to Windows 10. When I install I'll grab the before and after screen shots before and after checking WU. Unrelated but the testing was for a Intel network driver update that seems to break on Windows 10 but works on 11. I confirmed the bug so will be reverting back.
The only time there's been a "re-offering" (as you call it) of the LCU is when a UUPDump ISO is used for the installation. For me, when other ISOs are used for the install, there's never been a "re-offering" of the LCU. This is just one of the reasons that I haven't used a UUPDump ISO for an install, in a long time. Further discussion ends here...
Same problem here too! It is a bit frustrating and seems somewhat counterproductive, you being very careful to build an ISO with all the latest updates available. Whatever the reason: to save time and/or reduce the consumption of Internet traffic. And in the end, you will be "surprised" that the WU (just check the WU logs or monitor its activity via resmon) "re-offered" the LCU again. Thanks to the help obtained here, I was able to understand that this problem can be "triggered" by: After manually cleaning the LCU folder (Thanks to @Enthousiast and @nosirrahx comments); Pending flags after ISO handling (dism) and integration (CABs) updates; FoD enabled or modified (Language Pack, updated Edge version, dotNET Framework 3.5); Windows Update Delivery Optimization (WUDO). Just like the MDL colleagues, I would like to find an elegant solution to this issue! Until then, at least I can be conformed.