Why not first let the info sink in before another barrage of "answered many times" questions. On the tutorial here on mdl there are * which give some more info. I think the updates are specified good enough to see what they exactly are.
But some users like me may go directly to uupdump.ml instead of here first. Also, of which, how can I know if feature updates have the "additional updates" before downloading them and is UUP updated as soon as an update is released in one of the IP channels? Before I knew about the DU for sources (so, I wasn't integrating them) and when doing in-place upgrade installs, I was asked if I wanted to search for updates so were these updates actually DU for sources and Windows knows if the latest ones aren't integrated so it asks to download them? I haven't tried doing an in-place upgrade installs after integrating the latest DU for sources but if I'm right I guess I won't be asked to search for updates when doing it, right?
Then start to learn, by reading the provided info. By checking the updates, like i showed in the video before. Join the UUP dump discord server and you will see notifications when it's updated, or watch MDL for the announcements. You will always be asked if you want to download those updates, even when they are already pre-integrated.
I actually find out about that site not from here. Why is it called "UUP", by the way? Weird, as well as the fact I had problems when doing in-place upgrade installs after choosing to download files but not when ignoring them afterwards.
Windows 10 distribution is defined by servicing channels and deployment rings. The servicing channel (Insider, Semi-Annual, LTS) determines "how long" a Windows release is supported. The deployment ring determines "how fast" or the pace that updates are delivered. Insider Fast are weekly. Insider Slow are monthly. Release Preview are semi-annual. Technically, the word "channel" should not be used with Dev, Beta, or Release Preview because these are not "servicing channels". These are update audiences. But the expectation is that a developer receives updates from the Insider Fast ring. Beta Testers (or Insiders) receive updates from the Insider Slow ring. Public consumers receive updates from the Release Preview ring. It has caused me a bit of confusion to see terms like retail, regular user, etc. But I'll get over it. 'Hope this helps.
It's started by @whatever127 here on MDL. Because MSFT called it that, Unified Update Platform. Can't verify that, i never download any of them in my tests and when i do, no problems occured.
Please don't post superseded info, that all changed not so long ago. DEV (formerly known as FAST) = standalone test channel with weekly releases. Release Preview and Beta (formerly known as SLOW) offer updates after the sign off and have no fixed release frequency.
Thanks but this is confusing. Dev, Beta, Release Preview Channels, Insider, Semi-Annual, LTS channels, Inside Fast, Inside Slow Release Preview... Ok, but I went there for the first time not from here and I guess both should share the same information to not confuse users. What about Insider, Semi-Annual and LTS?
Nobody except some like you is confused. Just a bunch of words, unrelated to the UUP stuff. Insider = insider Semi-annual = twice a year LTS = Long Term Servicing
Do you know why some updates released on WU are called Preview like if they were still on IP channels? Does this mean they aren't final versions?
I have answered this last time too. Now MSFT calls the c updates (previously called non security updates, released in the third week of the month) Preview on catalog, just a name change, following win 7/8.1. https://forums.mydigitallife.net/threads/windows-10-hotfix-repository.57050/page-511#post-1610605
I believe these definitions were what the M$ gods originally intended for channels and rings to mean, but a lot has changed. For example, we were supposed to get 2 feature updates, one in March and one in September. Now we are lucky to get them in May and October. M$ recycles KB numbers. There's already been two EPs and various incremental CUs deploying the same KB numbers that sit in between official public releases. 'Seems a bit chaotic sometimes.
Oke but it is not 100% accurate it's today you know it is always the same around release date's people start shouting things as Today it is gonne be released as you can never tell if that the case with MS that is why I reacted with that pic @Enthousiast