Error Loading-ixybbaz.dll

  • Thread starter Thread starter Teri
  • Start date Start date
T

Teri

On startup I receive the message...Error loading
C:\windows\system32\ixybbaz.dll
The specified module could not be found..
How can I take care of this?
Teri
 
From: "Teri" <Teri@discussions.microsoft.com>

| On startup I receive the message...Error loading
| C:\windows\system32\ixybbaz.dll
| The specified module could not be found..
| How can I take care of this?
| Teri

Run; MSCONFIG.EXE

Go to the StartUp tab.

Find the line item that loads; C:\windows\system32\ixybbaz.dll

Uncheck the box and apply the change then reboot.

--
Dave
http://www.claymania.com/removal-trojan-adware.html
http://www.ik-cs.com/got-a-virus.htm
 
Teri wrote:
> On startup I receive the message...Error loading
> C:\windows\system32\ixybbaz.dll
> The specified module could not be found..
> How can I take care of this?
> Teri


A Google Groups search showed no mention of that file, other than your
post. That suggests that some malware was removed, but the reference to
the file was not removed from the registry.

Click Start, Run, type REGEDIT, click OK. Press the Home key, press F3,
type the name of the file into the search pane. Click "Find Next", and
when located, delete the reference to the file. Press F3 to continue
the search.

You can click File, Export, and save the entry to the Desktop, attach
the file to a post in this thread; someone might note whether it's safe
to delete first. If you remove it and there's a problem, double-click
the .reg file you exported to the Desktop and it'll be added to the
registry again. You can create a restore point before editing the
registry too.

--
Joe =o)
 
"Teri" <Teri@discussions.microsoft.com> wrote in message
news:CEBC16C4-BBA4-4ABD-9720-D781A18786D3@microsoft.com...
> On startup I receive the message...Error loading
> C:\windows\system32\ixybbaz.dll
> The specified module could not be found..
> How can I take care of this?
> Teri


Well, you're most likely seeing this message because your anti-virus or
anti-spyware app works.

Seemingly random filenames like that are a sure sign of malware infection.
And that message means that one of your protection utilities caught it, and
removed the file, but not the registry reference that launches it.

You may actually see another .exe file referenced in the registry, and you
can view it via msconfig.

The message means that you should do a little more system maintenance,
perhaps download and run ccleaner (www.ccleaner.com) and let it clear out
the temp and cache folders, which are prime entry points for malware; and
then go to Trend Micro's Housecall site and run the online virus scanner.
Do it in that order, as the temp and cache folders often have a lot of files
and each has to be scanned.

www.housecall.trendmicro.com

HTH
-pk
 
"Patrick Keenan" wrote:

> "Teri" <Teri@discussions.microsoft.com> wrote in message
> news:CEBC16C4-BBA4-4ABD-9720-D781A18786D3@microsoft.com...
> > On startup I receive the message...Error loading
> > C:\windows\system32\ixybbaz.dll
> > The specified module could not be found..
> > How can I take care of this?
> > Teri

>
> Well, you're most likely seeing this message because your anti-virus or
> anti-spyware app works.
>
> Seemingly random filenames like that are a sure sign of malware infection.
> And that message means that one of your protection utilities caught it, and
> removed the file, but not the registry reference that launches it.
>
> You may actually see another .exe file referenced in the registry, and you
> can view it via msconfig.
>
> The message means that you should do a little more system maintenance,
> perhaps download and run ccleaner (www.ccleaner.com) and let it clear out
> the temp and cache folders, which are prime entry points for malware; and
> then go to Trend Micro's Housecall site and run the online virus scanner.
> Do it in that order, as the temp and cache folders often have a lot of files
> and each has to be scanned.
>
> www.housecall.trendmicro.com
>
> HTH
> -pk
>
>
> Thank you so much, that solved the problem....
 
Back
Top