Now when im building the system i get the following stop error on vipre
RegWrite - Type: [0x4] Section [HKLMwb-hiveControlSet001ServicesSBRE] Key [Type]: 1
any ideas?
Just a guess: Change the lines 62 - 66 to
RegWrite,HKLM,0x4,"Tmp_Software\ControlSet001\Services\SBRE","Type",1
RegWrite,HKLM,0x4,"Tmp_Software\ControlSet001\Services\SBRE","ErrorControl",1
RegWrite,HKLM,0x4,"Tmp_Software\ControlSet001\Services\SBRE","Start",3
RegWrite,HKLM,0x2,"Tmp_Software\ControlSet001\Services\SBRE","ImagePath","system32\drivers\SBREdrv.sys"
RegWrite,HKLM,0x2,"Tmp_Software\ControlSet001\Services\SBRE","Group","Base"
and see if that helps.
@homes32:
I did tests with a new up to date desktop system here. Unfortunately there were several errors.
#1:
Whenever I launch the app like this
this will happen:
Simple workaround: Not choosing this very option.
#2:
If I choose Scan for Rootkits, VIPRERescue runs on x:\ (ramdisk) and, after 7 seconds or so a BSOD shows up.
The usual stuff there: STOP: 0x00000024 ... Ntfs.sys - Address 8BE28D1B base at 8BE13000, and so forth.
#2's a bummer. Any idea what might cause the BSOD?
Addendum:
I noticed that BSOD (always Ntfs.sys) also occurs running McAfee Stinger (executable out-of-box) just 2 seconds after the first "Scanning for rootkits" line is logged.
AVZ Toolkit and Emsisoft Emergency Kit both run without problems (i.e. no BSOD yet).
McAfee Stinger runs without RunScanner, as Emsisoft Emergency Kit does.
AVZ Toolkit and VIPRERescue rely on RunScanner (latest version 1.0.0.26).
So my first idea ("some RunScanner quirks") was wrong...