Run DLL Error message

  • Thread starter Thread starter Dayzed and cnofsude
  • Start date Start date
D

Dayzed and cnofsude

Hi when I boot up my vista home premium PC I receive this message

Run DLL
Error Loading C:\Windows\system32\awTmKdAr.dll
The specified module could not be found

There is an option to click on OK which I take and everything appears to run
normally.
Any ideas as to the why this is happening and/or a fix for the issue
gratefully received,
TIA
 
Hi,

Sounds like your antivirus/antispyware tool did about half the job. It
removed the malware file (awTmKdAr.dll), but not the reference that loaded
it. Click start, type regedit and hit <enter> to open the registry editor.
Check the strings in the right pane under these keys and remove (delete) it
if found:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
 
Rick Rogers said:
Hi,

Sounds like your antivirus/antispyware tool did about half the job. It
removed the malware file (awTmKdAr.dll), but not the reference that loaded
it. Click start, type regedit and hit <enter> to open the registry editor.
Check the strings in the right pane under these keys and remove (delete)
it if found:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Windows help - www.rickrogers.org
My thoughts http://rick-mvp.blogspot.com
Click to expand...

Hi Richard, thanks for such a speedy reply, have tried what you suggested
but the strings mentioned were not there (unfortunately !!) Any other ideas?
 
Hi,

Sounds like your antivirus/antispyware tool did about half the job. It
removed the malware file (awTmKdAr.dll), but not the reference that
loaded it. Click start, type regedit and hit <enter> to open the
registry editor. Check the strings in the right pane under these keys
and remove (delete) it if found:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run
Click to expand...

Wouldn't going through startup in msconfig be better and less prone to
error?
 
Wouldn't going through startup in msconfig be better and less prone to
error?
Click to expand...

No, Msconfig should only be used to turn on and off programs for
testing (see what's causing a problem) and a DLL most likely wouldn't
be shown.

The best way was already mentioned (if HiJackthis doesn't catch it):

"Materializing" <[email protected]>

just download autoruns and find that entry and uncheck it!

autoruns is now a microsoft tool, get it here

http://technet.microsoft.com/en-us/sysinternals/bb963902.aspx"
 
(e-mail address removed) wrote in
No, Msconfig should only be used to turn on and off programs for
testing (see what's causing a problem) and a DLL most likely wouldn't
be shown.

The best way was already mentioned (if HiJackthis doesn't catch it):
Click to expand...
Nope wrong there. The registry keys above *are* the non-disabled startup
lines full stop.
 
chuckcar said:
(e-mail address removed) wrote in
Click to expand...
Nope wrong there. The registry keys above *are* the non-disabled startup
lines full stop.
Click to expand...

I didn't post those reg keys

You didn't include Autoruns which was suggested and worked for the OP,

You either change your answer or omit pertinent info.
 
(e-mail address removed) wrote in
I didn't post those reg keys
Click to expand...
So *what*? You replied to my post *talking* about *just* that.
You didn't include Autoruns which was suggested and worked for the OP,
Click to expand...
Yet another add-on which does something windows already does. The google
stupidity complex - no thanks.
You either change your answer or omit pertinent info.
Click to expand...

I did neither, *you* did both.
 
chuckcar said:
(e-mail address removed) wrote in
Click to expand...
So *what*? You replied to my post *talking* about *just* that.
Click to expand...

Oh well, you don't know that Msconfig gets the startup info from those
reg keys, can't make you look dumber that way anymore.
Yet another add-on which does something windows already does. The google
stupidity complex - no thanks.
Click to expand...

I've used and advised the use of almost all of Sysinternals software.
I use Autoruns, Process Monitor as needed, and Process Explorer almost
daily.

Running Win98 you can't run most of their stuff and if so at a minimal
level. So I wouldn't expect you to know of some of the best utilities
available to the NT OS.
I did neither, *you* did both.
Click to expand...

Freaking grow/wise up.
 
(e-mail address removed) wrote in
Freaking grow/wise up.
Click to expand...
Look, I'll explain this once again as you obviously have somehow missed
the point: "Rick Rogers" <[email protected]> posted a suggestion that the OP
go into regedit and manually remove keys from the aforementioned part of
the registry, those keys are respectively the activated startup lines for
windows in general and the currently logged in user. I suggest that it would
be better to just uncheck them in startup. You then jump in and state:

No, Msconfig should only be used to turn on and off programs for
testing (see what's causing a problem) and a DLL most likely wouldn't
be shown.

Which has *no* bearing on what I said, showing you didn't understand
either post and hence shouldn't have posted at *all*. I then reply stating
that those registry keys are the same as the startup lines that are
checked. You then reply that you didn't post those registry lines. Of
course you didn't, you replied when I suggested that using regedit wasn't
a good way of doing it. You then suggest that I left something out, when
what was left out was your comprehension of what both I and "Rick Rogers"
<[email protected]> were talking about. Your foul, your misplaced post, your
mistake. Nobody elses.
 
Back
Top