One PC is a two minute fix. Forty PCs, each with the popup returning after feature updates, is a policy job. Here is the managed route, including the edition limits nobody mentions.
On a single PC, the Settings toggle or the one click script ends the Lets finish setting up your device popup. Across an office it keeps resurfacing: new user accounts start with it enabled, feature updates can reset plain values, and the one PC you missed generates the support call. This page gives the admin route honestly: the Cloud Content policy that suppresses the consumer suggestion layer, the edition limits that apply to it, and the Group Policy Preferences method that pushes the same per user values the video's script writes, to every account, every sign-in.
On a domain, the first tool is Group Policy. The setting Turn off Microsoft consumer experiences, under Computer Configuration, Administrative Templates, Windows Components, Cloud Content, suppresses the consumer suggestion layer: recommended apps, personalised suggestions and Microsoft account notifications of exactly the family the setup popup belongs to. Enabling it writes the policy value DisableWindowsConsumerFeatures set to 1 under HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\CloudContent. Because it is policy, Windows reapplies it continuously instead of trusting a value a feature update might reset.
Be straight with yourself about editions before you promise results. Several Cloud Content policies take full effect on Enterprise and Education editions; on Windows Pro the same policy exists and helps with suggested content, but Microsoft does not guarantee every consumer-experience surface obeys it there. That is not a reason to give up on Pro fleets. It is a reason to add the second layer below, which works per user on every edition, and to test on real machines in a pilot OU before announcing the popup dead across the company.
The switches behind the popup itself live per user, in HKEY_CURRENT_USER. Group Policy Preferences can write them for every user at sign-in:
ScoobeSystemSettingEnabled = 0 under Software\Microsoft\Windows\CurrentVersion\UserProfileEngagement (stops the finish setup screen)SubscribedContent-310093Enabled = 0 under Software\Microsoft\Windows\CurrentVersion\ContentDeliveryManager (stops the welcome experience screens)This is the same end state the video's one click script produces by hand; policy simply delivers it to everyone, including future user accounts, and keeps delivering it after feature updates.
No domain is not a dead end. Small offices can deploy the same script the video shows through whatever they already use: a logon script on the file server, their remote management tool, or a scheduled visit with the file on a pen drive. The discipline matters more than the tool: one standard script, run under each user account, verified after the next update. What to avoid is the artisanal approach, clicking Settings by hand on forty PCs, because account number three will be missed and that user will meet the popup alone.
While you are in policy, resist the temptation to silence everything. Restart warnings and update notifications are how users learn a reboot is coming; killing them to stop a suggestion screen trades a small annoyance for surprise restarts and unpatched machines. Target the suggestion and consumer-experience settings only, and leave the Windows Update notification policies at their defaults unless your update strategy genuinely manages them elsewhere.
The video shows the manual script route this policy setup is based on, useful for testing the end state on one PC before you deploy it to everyone.
Watch Full VideoStart with Turn off Microsoft consumer experiences under Computer Configuration, Administrative Templates, Windows Components, Cloud Content. Then add Group Policy Preferences writing ScoobeSystemSettingEnabled = 0 for each user, which targets the finish setup screen directly.
Partially, and Microsoft only guarantees several Cloud Content policies on Enterprise and Education editions. On Pro fleets, combine the policy with the per user registry values delivered by Preferences, and verify the result on pilot machines rather than assuming it.
Yes. Deploy the same script used in the video through a logon script, your remote management tool, or manually on each PC and user account. The method is less automatic than Group Policy, but the end state on each account is identical.