- error loading a dll file
- Posted by beedubs666 on November 11th, 2007
I downloaded a Kim Comando virus killer and it worked, but when it discovered
a corrupt dll file, I deleted it (probably stupid); now when I boot up I get
an error loading message window that I just click okay on and continue
working; but how can I reload c: WINDOWS system32\jbgvikft.dll ?
THREE USERS CAME BACK WITH A POOR ANSWER, WHICH WAS A PATH TO A RUN PROGRAM
THAT HAD ALL DLL FILES EXCEPT MINE
--
Bill W
- Posted by Mark L. Ferguson on November 11th, 2007
This key probably has a Value that is trying to run that deleted file.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run
--
helpful? click "Yes" button. Voting helps the web interface.
http://www.microsoft.com/windowsxp/e..._and _support
Mark L. Ferguson
"beedubs666" wrote:
- Posted by Mark L. Ferguson on November 11th, 2007
This key probably has a Value that is trying to run that deleted file.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run
--
helpful? click "Yes" button. Voting helps the web interface.
http://www.microsoft.com/windowsxp/e..._and _support
Mark L. Ferguson
"beedubs666" wrote:
- Posted by Patrick Keenan on November 11th, 2007
"beedubs666" <beedubs666@discussions.microsoft.com> wrote in message
news:5E304DE5-90CE-4454-B7F7-E5FE9103EEC7@microsoft.com...
In this case, actually not stupid, but exactly the correct action.
You do *not* reload this. That is a component of the virus.
Reloading it means re-installing and re-enabling the malware.
What's happened is that you identified and removed an infected file - note
the almost random name.
What you haven't removed is the reference to its loader. Locate that via
MSCONFIG, and just delete ther reference.
Again, that file isn't yours, it's a virus or trojan or other malware
component.
HTH
-pk
- Posted by Patrick Keenan on November 11th, 2007
"beedubs666" <beedubs666@discussions.microsoft.com> wrote in message
news:5E304DE5-90CE-4454-B7F7-E5FE9103EEC7@microsoft.com...
In this case, actually not stupid, but exactly the correct action.
You do *not* reload this. That is a component of the virus.
Reloading it means re-installing and re-enabling the malware.
What's happened is that you identified and removed an infected file - note
the almost random name.
What you haven't removed is the reference to its loader. Locate that via
MSCONFIG, and just delete ther reference.
Again, that file isn't yours, it's a virus or trojan or other malware
component.
HTH
-pk
- Posted by DL on November 11th, 2007
The answer to your previous post was correct, its just that you did'nt
follow the instructions, and your now shouting
"beedubs666" <beedubs666@discussions.microsoft.com> wrote in message
news:5E304DE5-90CE-4454-B7F7-E5FE9103EEC7@microsoft.com...
- Posted by DL on November 11th, 2007
The answer to your previous post was correct, its just that you did'nt
follow the instructions, and your now shouting
"beedubs666" <beedubs666@discussions.microsoft.com> wrote in message
news:5E304DE5-90CE-4454-B7F7-E5FE9103EEC7@microsoft.com...
- Posted by Nepatsfan on November 11th, 2007
In news:5E304DE5-90CE-4454-B7F7-E5FE9103EEC7@microsoft.com,
beedubs666 <beedubs666@discussions.microsoft.com> wrote:
Since I'm one of the persons who provided you with what you
describe as a "POOR" answer, here's a little advice. If you
want to resolve this issue, you need to tell the people who
offer help what happens when the suggestions they provide fail
to fix the problem. None of us can see what's on your computer
screen. Unless you provide some feedback you will probably find
yourself asking the same question over and over with no
resolution.
Oh, and getting po'd and posting in all caps won't get you a
better answer. As a matter of fact it will probably have the
opposite result.
Nepatsfan
- Posted by Nepatsfan on November 11th, 2007
In news:5E304DE5-90CE-4454-B7F7-E5FE9103EEC7@microsoft.com,
beedubs666 <beedubs666@discussions.microsoft.com> wrote:
Since I'm one of the persons who provided you with what you
describe as a "POOR" answer, here's a little advice. If you
want to resolve this issue, you need to tell the people who
offer help what happens when the suggestions they provide fail
to fix the problem. None of us can see what's on your computer
screen. Unless you provide some feedback you will probably find
yourself asking the same question over and over with no
resolution.
Oh, and getting po'd and posting in all caps won't get you a
better answer. As a matter of fact it will probably have the
opposite result.
Nepatsfan
- Posted by beedubs666 on November 13th, 2007
what do i do with that url
--
Bill W
"Mark L. Ferguson" wrote:
- Posted by beedubs666 on November 13th, 2007
what do i do with that url
--
Bill W
"Mark L. Ferguson" wrote:
- Posted by beedubs666 on November 13th, 2007
PatK,
Thanks, but how do I do that? (locate it?)
--
Bill W
"Patrick Keenan" wrote:
- Posted by beedubs666 on November 13th, 2007
PatK,
Thanks, but how do I do that? (locate it?)
--
Bill W
"Patrick Keenan" wrote:
- Posted by Elmo on November 13th, 2007
beedubs666 wrote:
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.
--
Joe =o)
- Posted by Elmo on November 13th, 2007
beedubs666 wrote:
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.
--
Joe =o)
