On Jan 12, 4:57 am, Dustin <
bughunter.dus...@gmail.com> wrote:
> Dustin <
bughunter.dus...@gmail.com> wrote innews:Xns9FD79EE7895D0HHI2948AJD832@no:
>
> > "David H. Lipman" <DLipman~nosp...@Verizon.Net> wrote in
> >
news:jekqm...@news2.newsguy.com:
>
> >> From: "Dustin" <
bughunter.dus...@gmail.com>
>
> >>>> Once a system is infected, review my reply to you in a recent post
> >>>> to you.
>
> >>> infected=virus. Trojan<>infected. One a system is trojanized, it's
> >>> easy enough to repair. Depending on the virus, it can also be
> >>> repaired. That's the lack of knowledge you have on this field
> >>> rearing it's ugly head on you again.
>
> >> I wouldn't agree there. Once malware is resident and acting upon a
> >> host that host is infected.
> >> In animal hosts they can be infected by; yeasts/molds, parasites,
> >> bacteria and viruses. It is no different than with a computer host.
>
> > No. It's a resident trojan. Still, not infected. Unless said trojan
> > is patching files to continue it's own existance. If not, then it's
> > not actually "infecting" anything. Creating an exe and a registry key
> > to load it later isn't infecting a machine.
>
> >> So I don't think; infected=virus Trojan<>infected is apropos.
>
> > Well, I hail from the virus/trojan terminology. Although I'm retired,
> > I still prefer to use the correct terminology when discussing them.
>
> I've got to retract this. I spoke with David via IM and I was unclear on
> what he meant by host. My bad. Should have read then replied. :)
>
> if we're discussing a host as a whole, then it's infected via a trojan
> which overwhelmes the systems defences and takes hold via a load point or
> residency. While it's not infecting files, it does have the system.
>
> Sorry for any confusion I've caused.
>
> --
> Character is doing the right thing when nobody's looking. There are too
> many people who think that the only thing that's right is to get by,
> and the only thing that's wrong is to get caught. - J.C. Watts
Hello,
Would you like to try this , I am not sure you have eradicate the
consrv.dll virus ?
I got banned from
bleepingcomputer.com when I post this article
regarding the simplest method of removal which I have successfully
help so many of them infected with consrv.dll virus .
The article below is taking sophos antivirus as example , you can try
others , even microsoft security essential is able to kill them , to
fully recover you need to do some extra job on the registry after
removal.
I would like to share how I manage to resolve consrv.dll virus found
on windows 7 which hijack the browser .
The sophos found the following
User: NT AUTHORITY\SYSTEM
Scan: On-access
File "C:\Windows\System32\consrv.dll" belongs to virus/spyware 'Troj/
ZAccess-L'.
User: NT AUTHORITY\SYSTEM
Scan: On-access
File "C:\Windows\assembly\GAC_32\Desktop.ini" belongs to virus/spyware
'Mal/Generic-L'.
For those using windows 7 you can try your luck by using system
restore point to earlier recovery before the infection .
If you can not recover using the above method I would suggest the
following method that I have tried.
0. let the antivirus programme kill whatever consrv.dll virus that
found , or using miscrosoft Security essential to kill the trojan ,
once this is done AND after you execute the reboot you will never be
able to boot the windows because the registry still need to repair .
1. To be safe , Go to control panel, select backup and restore.
2. choose Create a system repair disc to create a cd or dvd window
recovery disc
3.Do a clean bootup using the system repair disc which is bootable .
4. Select the command prompt offer by the window recovery .
5 Once in command prompt , usually drive X:, type regedit to call up
registry editor.
6 Navigate to web site
http://4sysops.com/archives/regedit-as-offline-registry-editor
to have clear understading how to do so would greatly help.
7 the %windir% usually refer to D:\windows\ or where is your physical
disk that contain the windows operating system
Use regedit as offline Registry editor
1.Launch regedit on the command prompt.
2.Click HKEY_LOCAL_MACHINE.
3.In the File menu, click “Load Hive.”
4.Open the database file that contains the Registry hive you need:
HKEY_LOCAL_MACHINE \SYSTEM = %windir%\system32\config\SYSTEM
%windir%\system32\config\SYSTEM= D:\windows\system32\config\SYSTEM
Some other portion of the registry that you may need are located
under :
HKEY_LOCAL_MACHINE \SAM = %windir%\system32\config\SAM
HKEY_LOCAL_MACHINE \SYSTEM = %windir%\system32\config\SYSTEM
HKEY_LOCAL_MACHINE \SOFTWARE = %windir%\system32\config\SOFTWARE
HKEY_USERS \.Default = %windir%\system32\config\DEFAULT
HKEY_CURRENT_USER = %userprofile%\ntuser.dat
5.Enter an arbitrary key name when prompted , example test .
A new node with your key name appears under
HKEY_LOCAL_MACHINE \SYSTEM
8. To carry out with the registry repair
select the note load hive under test
navigate to HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session
Manager\Subsystems
and also
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager
\Subsystems
select Name "Windows" and edit .
Replace whatever consrv to winsrv
original
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,20480,768 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=consrv:ConServerDllInitialization,2 ServerDll=sxssrv,4
ProfileControl=Off MaxRequestThreads=16
to
%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows
SharedSection=1024,20480,768 Windows=On SubSystemType=Windows
ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3
ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4
ProfileControl=Off MaxRequestThreads=16
9 Once the above two steps are done , unload the hive to write back
the offline windows registry.
10 you should be able to reboot after this , remember to do a full
scan to confirm again.
Thanks ,