adolescent wrote:
The fact that he couldn't stop/disable a service tells me he's not much of a Windows user at all.
To me, the fact that he uses MSCONFIG to do this work rather than as a reference, then actually do the work (properly) himself tells me this story. MSCONFIG does not display all of the potential hiding places -- ActiveX cache is one of them, the Shell registry is another, and so on.
Windows Defender or a combination of tools from SysInternals are much better suited for this kind of work.