G
Guest
....now this is very very peculiar , if you don't ask me , because I found
this name while I browsed the registry driven by a smidgen of curiosity about
a searcher called WhenUSearch . I found 132.dll by double clicking on a
registry entry , the last kind of entry you could reach when looking through
the registry where you would open a Window , you know , the last instance
in the registry where you could open a window . Well , there were , what I
think you call Binary numbers on the left side of the window like 06 08 00
etc...and on the right side of the window , I had to scroll to get to the far
right side of the window , was a whole lot of the usual ditto marks or
commas or whatever you see would usually in there and as I scrolled down the
list I came across 132.dll . Now when I look for 132.dll using Google I find
132.dll is a Trojan .
My question is why would I find 132.dll in the registry when Avast and
Microsoft AntiSpyware did not see it . As far as I can tell 132.dll has been
around for quite a while .
this name while I browsed the registry driven by a smidgen of curiosity about
a searcher called WhenUSearch . I found 132.dll by double clicking on a
registry entry , the last kind of entry you could reach when looking through
the registry where you would open a Window , you know , the last instance
in the registry where you could open a window . Well , there were , what I
think you call Binary numbers on the left side of the window like 06 08 00
etc...and on the right side of the window , I had to scroll to get to the far
right side of the window , was a whole lot of the usual ditto marks or
commas or whatever you see would usually in there and as I scrolled down the
list I came across 132.dll . Now when I look for 132.dll using Google I find
132.dll is a Trojan .
My question is why would I find 132.dll in the registry when Avast and
Microsoft AntiSpyware did not see it . As far as I can tell 132.dll has been
around for quite a while .