Well, LuraAnne..
In this thread there is Ken's way and about 50 posts in I think someone from Canada posted a similar way using different WU updater files. I saw but cannot find again a MS tech thing that was SO TECHNICAL having you play around in the registry that I didn't look any deeper at it.
Then there is the way I did it.
BUT, I ended up having to wipe the machine and start from scratch because I didn't catch it in time and MS basically bricked the machine when they shoved a W10 upgrade on me and nothing seemed to actually work to roll it back.
So, once I got serious about getting the machine running again, I had a secondary goal which was to block all the W10 malware. Toward that end when I tried to do a re-installation I selected ASK LATER so I could control when and what updates were downloaded as suggested in many places in many tech articles about how to stop the W10 garbage, but as soon as I installed SP1, the update system froze up.
So I started looking for how to unfreeze it and Started my thread and someone posted there suggesting I look here.
I tried and failed using Ken's plan and the other one. I now understand that I failed because I didn't notice or understand that none of the suggested alternate WU update clients would load until SP1 was installed and that the internet connection MUST be disconnected before you do the restart after installing SP1.
If SP 1 is on the machine, and it is connected to the internet, it will get the bad updater.
Ken says that selecting ASK LATER during the initial installation will prevent that, but, as noted above, that was not my experience.
Regarding the "Roll up File". I have been watching the comment sections of tech articles on CNET, Computer world and such and so far, the comments sections seem to be a mixed bag. It works for some people and doesn't for others. At present I don't need it because i managed to get my machine fully up-to-date and I have a system image with bloatware removed,, except I have IE11 blocked because the latest version of it is tainted with W10 nagware. This is only a problem if you have a machine that is supposedly W10 capable as mine supposedly is but,,, for reasons unknown I ended up with a brick and had to start over.