It is tempting to silence everything Windows says after an update. Resist it. The warnings and the sales pitch come from different systems, and only one of them deserves switching off.
Every fix has a blast radius, and this topic attracts fixes with a huge one. Because the Lets finish setting up your device screen appears after updates, plenty of advice treats it as an update problem and reaches for the biggest hammer available: the update service and its notifications. This page draws the line clearly. The popup is a suggestion, update notifications are warnings, and the two are controlled in completely different places. Switch off the suggestion, keep every warning, and the PC becomes quieter and stays patched.
The Lets finish setting up your device popup arrives after updates, so it is natural to file it mentally under update notifications. It does not belong there. It is produced by the suggestion and consumer-experience layer of Windows, the same family as tips and recommended content. Update notifications are produced by the update system itself, and they carry operational information: an update is ready, a restart is required, a deadline is approaching. Different source, different settings, different value to you. Conflating them is how people end up fixing the wrong thing, sometimes dangerously.
Search for this popup and you will find aggressive recipes: disable the Windows Update service, block update notifications entirely, strip out system components with debloat tools. They do stop the popup, the way removing the engine stops a car horn. The costs arrive later: security patches silently not installing, feature updates failing half-applied, restarts happening without the warnings that let users save work first. In the video's world, where one IT person answers for many users' PCs, an unpatched machine is a far worse phone call than a blue suggestion screen ever was.
Keep the restart-required warnings, the update attention notices and the restart countdown behaviour exactly as Windows ships them. On office PCs, if anything, strengthen them through policy with clear active hours and deadlines, so updates complete predictably instead of being postponed forever. A user who is warned, restarts at lunch and stays patched is the system working. Your quarrel is only with a sales checklist borrowing the update's moment, and that checklist has its own switch, which is all you need to touch.
For the record, the complete target list for a quiet but healthy PC is short. Off: the finish setup suggestion toggle, or ScoobeSystemSettingEnabled set to 0. Off, if you dislike them: the welcome experience toggle, or SubscribedContent-310093Enabled set to 0, and the tips and suggestions toggle. On, untouched: Windows Update service, update notifications, restart warnings and every security alert. If a tool or a guide proposes more than this list for this problem, it is solving a different problem than yours, at your PC's expense.
The video's script is a good example of correct scoping: it targets the popup and the welcome experience and leaves the update system completely alone.
Watch Full VideoProbably, along with your security updates, driver updates and feature updates. It is the most expensive way to solve a two-setting problem, and it leaves the PC exposed. The popup has its own dedicated toggle and registry value; use those.
No. Restart warnings come from the update system and exist so you can save work before a reboot. The setup popup comes from the suggestion system. Keep the warnings on and switch off only the suggestion settings.
Two, optionally three, per user settings: the finish setup suggestion toggle, the welcome experience toggle, and if you like, the tips and suggestions toggle. Everything related to updates themselves stays exactly as it was.