There is no set timeline for the release of the store App updates, unlike patch Tuesdays.Each app update is released almost weekly and could be on different days.DO in 1511 build is used in about 50% of the downloads, and when DO isn’t used the download switches to BITS.From 1607 build onwards, it is the default downloader for Windows Update and Windows Store content.If it does, then you need to apply a rule to permit HTTP RANGE requests for the following URLs: *.download.**dl.Most of the customers may already have included the first two URLs but may not be aware of the 3rd URL, which is the CDN for Store App updates.In the absence byte-range inclusion, the store app update is not downloaded as delta and instead the entire payload is downloaded which, needless to say, it will be bigger in size.
It is important that we understand and identify them instead of brushing them under the same stroke.
We also recommend that you do not use these new settings with WSUS/SCCM.
If you are already using an on-prem solution to manage Windows updates/upgrades, using the new WUf B settings will enable your clients to also reach out to Microsoft Update online to fetch update bypassing your WSUS/SCCM end-point.
While system specific updates will still reach out to WSUS or SCCM, or against Microsoft Update if the machine is configured to use Microsoft Update instead of Windows Update, the Store App updates are not yet cached or supported on WSUS or SCCM yet.
So actually, the machine is going out to url- only to update the Windows Store Apps.