Btw: Also others, that aren't practical or really problematic to even attempt to disable. ie: When you connect to M$ servers to get that ever present flood of updates, to fix bugs, patch sec holes that may've been around for 10yrs and M$ just never bothered getting around to, often updates bringing new bugs and borks in a viscious circle even bringing in new "features" or activated old "features", you've specifically disabled. All for your security and benefit of course, thanks M$ ! How much information about you, your OS ... and computer usage is likely to be exchanged in the process ?
Hmmm let's ask Catweasel, I'm sure he's an expert and has devoted 10's of hours to this and the gazillion other aspects of how window$ works on the most intimate levels. So no doubt will be able to tell everybody how to go about "fixing it".
btw2: I actually for a long time running window$ just disabled updates and decided to take my chances. You could also disable automatic updates, then manually trudge through only the one's designated as "critical" or whichever. Having to truly research each and what it actually does prior to installing them. Guess who get's to decide what's "critical" ... M$ does.
Have played with win10 on other people's boxes and this old second hand laptop came with it, so dorked around a bit with it briefly before doing the right thing imo = Overwriting it while installing gnu/Linux. Know going fully gnu/Linux just isn't practical for many who need it or use it for whatever reasons. Still though, think I won the game with M$, by knowing it's a headache inducing, time intensive and pointless one for ME. Checkmate M$, checkmate ole buddy, ole pal, lol.
Seems M$/window$ approach to operating system design, as new versions come out make them worse and worse, with so many still thinking they have no alternative. Whereas open source and gnu/Linux, just keeps getting better and better, with more and more options as time goes by.