I always get the following error message when starting up the computer:
"ERROR MESSAGE: C:\WINDOWS\system32\urkgupfj.dll, The specified module could
not be found". I could not find any definite answers as some people
recommend registry cleanings, others virus scans, other nothing. Any advice
will be greatly appreciated.
--
mp
error loadig messages
Moderators: DllAdmin, DLLADMIN ONLY
Re: error loadig messages
"malpez" <malpez@discussions.microsoft.com> wrote in message
news:10417DAE-3243-448A-8AA6-5BC59894F8B9@microsoft.com...
>I always get the following error message when starting up the computer:
> "ERROR MESSAGE: C:\WINDOWS\system32\urkgupfj.dll, The specified module
> could
> not be found". I could not find any definite answers as some people
> recommend registry cleanings, others virus scans, other nothing. Any
> advice
> will be greatly appreciated.
> --
> mp
Did you run an antivirus or antispyware scan recently on this computer? The
behavior you describe is usually what happens when an antivirus or
antispyware program identifies a file as malware, deletes the file, but
doesn't
clean up the mechanism that launches the malware at startup.
Here's a program from Microsoft that will help you stop the error messages.
AutoRuns for Windows v9.39
http://technet.microsoft.com/en-us/sysi ... 63902.aspx
Once you've downloaded and extracted the files, run autoruns.exe.
Look on the Everything tab for an entry that lists urkgupfj.dll in the Image
path
column.
Right click on that entry and select Search Online from the menu.
Odds are that you'll come up with an empty search. This pretty much confirms
that it was some type of malware that your scan deleted.
Uncheck the item.
Restart your computer. If you no longer see the error message, you can go
back
and delete the entry in Autoruns.
Just to be on the safe side, you might consider taking steps to make sure
the
system is malware free. Here's a site with general instructions on cleaning
a
computer.
http://www.elephantboycomputers.com/pag ... es_Malware
Good luck
Nepatsfan
news:10417DAE-3243-448A-8AA6-5BC59894F8B9@microsoft.com...
>I always get the following error message when starting up the computer:
> "ERROR MESSAGE: C:\WINDOWS\system32\urkgupfj.dll, The specified module
> could
> not be found". I could not find any definite answers as some people
> recommend registry cleanings, others virus scans, other nothing. Any
> advice
> will be greatly appreciated.
> --
> mp
Did you run an antivirus or antispyware scan recently on this computer? The
behavior you describe is usually what happens when an antivirus or
antispyware program identifies a file as malware, deletes the file, but
doesn't
clean up the mechanism that launches the malware at startup.
Here's a program from Microsoft that will help you stop the error messages.
AutoRuns for Windows v9.39
http://technet.microsoft.com/en-us/sysi ... 63902.aspx
Once you've downloaded and extracted the files, run autoruns.exe.
Look on the Everything tab for an entry that lists urkgupfj.dll in the Image
path
column.
Right click on that entry and select Search Online from the menu.
Odds are that you'll come up with an empty search. This pretty much confirms
that it was some type of malware that your scan deleted.
Uncheck the item.
Restart your computer. If you no longer see the error message, you can go
back
and delete the entry in Autoruns.
Just to be on the safe side, you might consider taking steps to make sure
the
system is malware free. Here's a site with general instructions on cleaning
a
computer.
http://www.elephantboycomputers.com/pag ... es_Malware
Good luck
Nepatsfan
Re: error loadig messages
malpez wrote:
> I always get the following error message when starting up the computer:
> "ERROR MESSAGE: C:\WINDOWS\system32\urkgupfj.dll, The specified module could
> not be found". I could not find any definite answers as some people
> recommend registry cleanings, others virus scans, other nothing. Any advice
> will be greatly appreciated.
It's possible some 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)
> I always get the following error message when starting up the computer:
> "ERROR MESSAGE: C:\WINDOWS\system32\urkgupfj.dll, The specified module could
> not be found". I could not find any definite answers as some people
> recommend registry cleanings, others virus scans, other nothing. Any advice
> will be greatly appreciated.
It's possible some 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)