Both routes land in the same place: a small set of registry values switched off. The real differences are speed, repeatability, and how carefully you check the tool before you trust it.
People tend to pick a side in this argument on instinct: scripts feel risky, manual clicking feels safe. For this particular job the honest picture is calmer. The popup is controlled by documented settings and registry values. The Settings app changes them with checkboxes; the video's one click script changes them with registry automation. This page compares the two routes fairly, states what a script for this job writes, and repeats the one safety rule that matters more than the choice itself: read any script before you run it.
A script cannot reach inside Windows and remove the popup feature. What it can do, and what the script in the video is described as doing, is registry automation: writing the small set of values that control these screens, in one run, instead of you clicking through Settings and Registry Editor by hand. For this job those are the documented values shown above: ScoobeSystemSettingEnabled set to 0 for the finish setup screen, and SubscribedContent-310093Enabled set to 0 for the welcome experience. The video page lists the script's job plainly: disable the setup popup and disable the welcome experience. Same destination as the manual route, reached in seconds.
A registry or batch file is readable text, and that is your protection. Before running any script, from any creator, right-click it, choose to open it with Notepad, and read it. For this job you expect to see a handful of lines naming keys like UserProfileEngagement and ContentDeliveryManager. What should stop you: commands you cannot account for, downloads of further files, anything touching the Windows Update service, user accounts or network settings. Download scripts only from the creator's own link, in this case the one shared with the video, never from a random re-upload. This ten-second habit is the entire difference between automation and gambling.
The manual route has one real advantage: you see every change as you make it. The Settings toggles show their own descriptions, and Registry Editor shows the exact value before and after. For a single PC that you own, manual is perfectly reasonable and takes about two minutes. Its weakness is repetition and certainty: three toggles in one place, values in another, per user account, on every PC, after resets. Nothing about the manual route is safer in effect, because the end state is identical; it is only slower and easier to do half-finished.
The script wins when the job repeats: several PCs, several user accounts on one PC, or a machine you are preparing for someone else, which is the video's scenario. One run, one restart, the same verified end state everywhere. Undoing is equally simple in both routes. In Settings, tick the toggles back on. In Registry Editor, set ScoobeSystemSettingEnabled back to 1 or delete the values you added, and the screens are allowed again. Keep the script file and this knowledge together and the change is never a one-way door.
The video demonstrates its own script end to end, so you can see exactly what runs before you ever try it yourself.
Watch Full VideoNo. Both routes change the same underlying settings. The Settings toggles and the registry values are two doors into the same room, which is why either route can also undo the other.
Open it in Notepad before running and read every line. For this job you should see registry writes to UserProfileEngagement and ContentDeliveryManager and little else. If a script downloads other files, disables services or touches accounts, do not run it.
Yes, that is its main advantage. The values are per user account, so the script needs to run once under each account you want covered, or be deployed by an admin tool. Keep the same file so every machine ends in the identical state.