Anything that is the registry run keys is in msconfig. Your own words:
"Almost all the posts in here about error messages on startup are caused by
orphaned run keys entries." These banal errors on startup saying that a
certain file is missing are all from entries in the run keys and *all* of
these run key entries are in msconfig. Your ignorance shows that you don't
know the difference between the run keys and startup locations. There is no
need for registry cleaners to cleanup these run key entries and only idiots
would use cleaners to cleanup malware.

The userinit value. There usually aren't any problems with the malware
affected value until registry cleaners come by and improperly remove the
value, then the computer doesn't start and the user can't properly edit the
key. This is well known and many users have posted of this problem with
cleaners improperly removing the value, yet as usual you conveniently forget
to mention this because you're in denial and you would go to any length to
defend these cleaners, that includes recommending them to novice users who
can't properly interpret the actions taken by these dangerous tools.
Experienced people who are competent and who understand Windows don't
recomend registry cleaners, none of the MVPs recomend them, only phony MVPs
and ignorant trolls advocate the use of these dangerous tools.

M

"The Real Truth MVP" wrote in message
...
Your ignorance is showing. It is not the registry cleaners that cause
problems with userinit key you idiot it's the malware that modifies it and
the cheap crappy malware removers that modify it and does not fix it. And
then there's that crap you said about what calls the run key. If it is an
orphaned key then why is it being read? Mike Hall said they are not read,
if they are not read then why is it reading it? You are also wrong about
using MSCONFIG. Have you ever used autoruns? probably not, how come all
those start up entries found in autoruns is not listed in msconfig?
sheeeesh my 3 year old is smarter than you. And MS did not take Giant
Antispyware and just put it out there as is, in fact Onecare has NOTHING
to do with Giant Antispyware. Windows Defender was built on the
restructured version of GIANT Antispyware.