The subtree
HKCU\Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager — per user, a gang of DWORDs with names like ContentDeliveryAllowed, SubscribedContent-33839xEnabled variants, SystemPaneSuggestionsEnabled, SoftLandingEnabled. Build-to-build the GUID-flavored IDs shuffle a little; the structural idea doesn't.
The discipline that keeps tweaking safe
- Set individual named DWORDs, don't wholesale the entire key. Presence/absence of unknown future children on next builds is the risk of blanket configs.
- Log the name-as-written: flipping the “wrong variant for your build” fails harmlessly but leaves stale residue; audit the key listing after the app flips something (see snapshot diffing).
- Explorer reload reality: some of these read at Start render only — Restart Explorer before you conclude your value had no effect.
The bigger point: this subtree is a textbook example of “wide chosen surface with narrow knives” — twelve siblings doing one thing each is why per-value catalogs beat dan-the-tweaker scripts that claim a single “disable ads” checkbox.