error loading dll

Here you can find everything you need to know about Dll-Files. You can also share your knowledge regarding the topic.

Moderators: DllAdmin, DLLADMIN ONLY

Post Reply
doncee
Posts: 2
Joined: 14 Sep 2010, 23:00

error loading dll

Post by doncee »

Recently Avast antivirus located & quarantined some apparent malware or
trojan virus problems on my XP system. The workstation is working fine
with no problems however every time it gets rebooted I get the following
message "error loading c\Windows\kbdorx.dll" This is one of the files
that Avast put in the virus chest. Is there a way to eliminate the
missing dll message on boot up since I am assuming this file is
apparently part of the malware or trojan. Any help appreciated.
Thanks
dc

elmo
Posts: 47
Joined: 07 Mar 2009, 00:00

Re: error loading dll

Post by elmo »

On 9/15/2010 11:11 AM, doncee wrote:
> Recently Avast! antivirus located & quarantined some apparent malware
> problems on my XP system. The workstation is working fine
> with no problems however, every time it gets rebooted I get the following
> message: "error loading c:\Windows\kbdorx.dll". This is one of the files
> that Avast! put in the virus chest. Is there a way to eliminate the
> missing dll message on boot up since I am assuming this file is
> apparently part of the malware or Trojan? Any help appreciated.
> Thanks
> dc

The malware was deleted by your a/v software, 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. 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.

You could click Start, Run, type MSCONFIG, click OK, click the StartUp
tab, and deselect the item(s). When you restart the computer, you will
be warned that you're running in the Diagnostic mode; click to not alert
you again, and OK out. You won't see the message again. But I think
it's best to just remove the references from the registry.

--

Joe =o)

doncee
Posts: 2
Joined: 14 Sep 2010, 23:00

Re: error loading dll

Post by doncee »

Elmo <elmogeek@xxx.invalid> wrote in
news:8_qdnbKajIQLgQzRnZ2dnUVZ_sqdnZ2d@insightbb.com:

> On 9/15/2010 11:11 AM, doncee wrote:
>> Recently Avast! antivirus located & quarantined some apparent
malware
>> problems on my XP system. The workstation is working fine
>> with no problems however, every time it gets rebooted I get the
>> following message: "error loading c:\Windows\kbdorx.dll". This is
>> one of the files that Avast! put in the virus chest. Is there a way
>> to eliminate the missing dll message on boot up since I am assuming
>> this file is apparently part of the malware or Trojan? Any help
>> appreciated. Thanks
>> dc
>
> The malware was deleted by your a/v software, 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. 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.
>
> You could click Start, Run, type MSCONFIG, click OK, click the
StartUp
> tab, and deselect the item(s). When you restart the computer, you
> will be warned that you're running in the Diagnostic mode; click to
> not alert you again, and OK out. You won't see the message again.
> But I think it's best to just remove the references from the
registry.
>

Thanks for the advice. I ran msconfig & unchecked the references in the
startup section to the 2 dll files & that seems to have corrected the
issue. Once again thanks for the follow-up
dc

Post Reply