Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Two system roots at boot time?


  • This topic is locked This topic is locked
6 replies to this topic

#1 dianasaur

dianasaur

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Wofford Heights, California
  • Local time:02:21 AM

Posted 26 May 2011 - 06:45 AM

Hello :busy:

I work with a bunch of networked computers that have been acting very strange for the past few months. Some are periodically unable to read CD/DVD-ROM drives, and won't boot from them unless I pull and replace their CMOS batts & RAM. Printers and scanners keep disappearing, sometimes coming back on their own and other times requiring reinstallation. Microsoft Word & Excel crash a lot, and always want to recover files that don't exist.

System Event logs have a few entries in common--winlogon.exe events ("The shell stopped unexpectedly and Explorer.exe was restarted", HHCTRL events (description unknown), and periodic disk events (timeouts, bad blocks).

Two machines have hard drives that can't be examined from any other system--they're either not seen or cause an immediate BSOD. I was able to access one drive from a linux system, but afterward that system was unable to display file system type and disk usage information for any of its volumes.

Most have lots of file corruption--chkdsk has to be run frequently to avoid BSODs. Sometimes scheduling chkdsk at startup fails--the system is unable to access volume for the chkdsk, but the OS still loads fine. Even weirder, if I keep trying the disk check will eventually run.

Malware scans usually come up clean. RootRepeal and Radix sometimes show hidden processes or handles; RootRepeal showed an mbr rootkit on two of them, but I was unable to remove it and had to rebuild them; Norman Malware Cleaner sometimes shows a process infected with W32/Delf.FFWG

There is one thing that they all seem to have in common. Enabling boot logging in Sysinternals' ProcMon shows what appear to be two system roots during startup, (C:\) and (C:C:\). (C:\) looks normal, and (C:C:\) always looks like this:

C:C:
C:C:\WINDOWS
C:C:\WINDOWS\system32
C:C:\WINDOWS\system32\autochk.exe.Local
C:C:\WINDOWS\system32\csrss.exe.Local
C:C:\WINDOWS\system32\winlogon.exe.Local
C:C:\WINDOWS\system32\winlogon.exe.Local\

The system files with the .Local extension always result in PATH NOT FOUND or NAME INVALID in the boot log. All logs show autorun.inf, HVDVD_TS, and video_TS entries in C:\ that I can't see from within Windows. There are a growing number of other files that only show up in the procmon logs, but they seem to be different for each machine.

I don't know very much about ProcMon, and am not sure what to make of the results. It seems like there are two roots on the affected machines, and that's why there's so much confusion with the drives. I don't see the C:C: root when I run the utility on other computers.

Are the ProcMon results normal? If so, do any of the other symptoms sound familiar?

Thanks for all your help,
DianaM

BC AdBot (Login to Remove)

 


#2 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:10:21 AM

Posted 02 June 2011 - 07:07 AM

Hello,

And welcome to BleepingComputer.com, before we can assist you with your question of: Am I infected? You will need to perform the following tasks and post the logs of each if you can.

Malwarebytes Anti-Malware

Please download Malwarebytes Anti-Malware and save it to your desktop.
Download Link 1
Download Link 2MBAM may "make changes to your registry" as part of its disinfection routine. If using other security programs that detect registry changes (ie Spybot's Teatimer), they may interfere or alert you. Temporarily disable such programs or permit them to allow the changes.

  • Make sure you are connected to the Internet.
  • Double-click on mbam-setup.exe to install the application.
    For instructions with screenshots, please refer to the How to use Malwarebytes' Anti-Malware Guide.
  • When the installation begins, follow the prompts and do not make any changes to default settings.
  • When installation has finished, make sure you leave both of these checked:
    • Update Malwarebytes' Anti-Malware
    • Launch Malwarebytes' Anti-Malware
  • Then click Finish.
MBAM will automatically start and you will be asked to update the program before performing a scan.
  • If an update is found, the program will automatically update itself. Press the OK button to close that box and continue.
  • If you encounter any problems while downloading the definition updates, manually download them from here and just double-click on mbam-rules.exe to install.
On the Scanner tab:
  • Make sure the "Perform Full Scan" option is selected.
  • Then click on the Scan button.
  • If asked to select the drives to scan, leave all the drives selected and click on the Start Scan button.
  • The scan will begin and "Scan in progress" will show at the top. It may take some time to complete so please be patient.
  • When the scan is finished, a message box will say "The scan completed successfully. Click 'Show Results' to display all objects found".
  • Click OK to close the message box and continue with the removal process.
Back at the main Scanner screen:
  • Click on the Show Results button to see a list of any malware that was found.
  • Make sure that everything is checked, and click Remove Selected.
  • When removal is completed, a log report will open in Notepad.
  • The log is automatically saved and can be viewed by clicking the Logs tab in MBAM.
  • Copy and paste the contents of that report in your next reply. Be sure to post the complete log to include the top portion which shows MBAM's database version and your operating system.
  • Exit MBAM when done.
Note: If MBAM encounters a file that is difficult to remove, you will be asked to reboot your computer so MBAM can proceed with the disinfection process. If asked to restart the computer, please do so immediately. Failure to reboot normally (not into safe mode) will prevent MBAM from removing all the malware.


SUPERAntiSpyware:

Please download and scan with SUPERAntiSpyware Free

  • Double-click SUPERAntiSypware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If it will not start, go to Start > All Prgrams > SUPERAntiSpyware and click on Alternate Start.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the "General and Startup" tab, and under Start-up Options, make sure "Start SUPERAntiSpyware when Windows starts" box is unchecked.
  • Click the "Scanning Control" tab, and under Scanner Options, make sure the following are checked (leave all others unchecked):
    • Close browsers before scanning.
    • Scan for tracking cookies.
    • Terminate memory threats before quarantining.
  • Click the "Close" button to leave the control center screen and exit the program.
  • Do not run a scan just yet.
Reboot your computer in "Safe Mode" using the F8 method. To do this, restart your computer and after hearing your computer beep once during startup (but before the Windows icon appears) press the F8 key repeatedly. A menu will appear with several options. Use the arrow keys to navigate and select the option to run Windows in "Safe Mode".

Scan with SUPERAntiSpyware as follows:
  • Launch the program and back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan and click "Next".
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • If asked if you want to reboot, click "Yes" and reboot normally.
  • To retrieve the removal information after reboot, launch SUPERAntispyware again.
    • Click Preferences, then click the Statistics/Logs tab.
    • Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
    • If there are several logs, click the current dated log and press View log. A text file will open in your default text editor.
    • Please copy and paste the Scan Log results in your next reply.
  • Click Close to exit the program.
If you have a problem downloading, installing or getting SAS to run, try downloading and using the SUPERAntiSpyware Portable Scanner instead. Save the randomly named file (i.e. SAS_1710895.COM) to a usb drive or CD and transfer to the infected computer. Then double-click on it to launch and scan. The file is randomly named to help keep malware from blocking the scanner.

Instructions:

Download and scan with SUPERAntiSpyware Free for Home Users
  • Double-click SUPERAntiSpyware.exe and use the default settings for installation.
  • An icon will be created on your desktop. Double-click that icon to launch the program.
  • If asked to update the program definitions, click "Yes". If not, update the definitions before scanning by selecting "Check for Updates". (If you encounter any problems while downloading the updates, manually download them from here. Double-click on the hyperlink for Download Installer and save SASDEFINITIONS.EXE to your desktop. Then double-click on SASDEFINITIONS.EXE to install the definitions.)
  • In the Main Menu, click the Preferences... button.
  • Click the Scanning Control tab.
  • Under Scanner Options make sure the following are checked (leave all others unchecked):
    • Close browsers before scanning.
    • Scan for tracking cookies.
    • Terminate memory threats before quarantining.
  • Click the "Close" button to leave the control center screen.
  • Back on the main screen, under "Scan for Harmful Software" click Scan your computer.
  • On the left, make sure you check C:\Fixed Drive.
  • On the right, under "Complete Scan", choose Perform Complete Scan.
  • Click "Next" to start the scan. Please be patient while it scans your computer.
  • After the scan is complete, a Scan Summary box will appear with potentially harmful items that were detected. Click "OK".
  • Make sure everything has a checkmark next to it and click "Next".
  • A notification will appear that "Quarantine and Removal is Complete". Click "OK" and then click the "Finish" button to return to the main menu.
  • If asked if you want to reboot, click "Yes".
  • To retrieve the removal information after reboot, launch SUPERAntispyware again.
    • Click Preferences, then click the Statistics/Logs tab.
    • Under Scanner Logs, double-click SUPERAntiSpyware Scan Log.
    • If there are several logs, click the current dated log and press View log. A text file will open in your default text editor.
    • Please copy and paste the Scan Log results in your next reply.
  • Click Close to exit the program.
If you have a problem downloading, installing or getting SAS to run, try downloading and using the SUPERAntiSpyware Portable Scanner instead. Save the randomly named file (i.e. SAS_1710895.COM) to a usb drive or CD and transfer to the infected computer. Then double-click on it to launch and scan. The file is randomly named to help keep malware from blocking the scanner.


Now GMER

GMER does not work in 64bit Mode!!!!!!

Please download GMER from one of the following locations and save it to your desktop:

  • Main Mirror
    This version will download a randomly named file (Recommended)
  • Zipped Mirror
    This version will download a zip file you will need to extract first. If you use this mirror, please extract the zip file to your desktop.
  • Disconnect from the Internet and close all running programs.
  • Temporarily disable any real-time active protection so your security programs will not conflict with gmer's driver.
  • Double-click on the randomly named GMER file (i.e. n7gmo46c.exe) and allow the gmer.sys driver to load if asked.
  • Note: If you downloaded the zipped version, extract the file to its own folder such as C:\gmer and then double-click on gmer.exe.

    Posted Image
  • GMER will open to the Rootkit/Malware tab and perform an automatic Full Scan when first run. (do not use the computer while the scan is in progress)
  • If you receive a WARNING!!! about rootkit activity and are asked to fully scan your system...click NO.
  • Now click the Scan button. If you see a rootkit warning window, click OK.
  • When the scan is finished, click the Save... button to save the scan results to your Desktop. Save the file as gmer.log.
  • Click the Copy button and paste the results into your next reply.
  • Exit GMER and be sure to re-enable your anti-virus, Firewall and any other security programs you had disabled.
-- If you encounter any problems, try running GMER in safe mode.
-- If GMER crashes or keeps resulting in a BSODs, uncheck Devices on the right side before scanning
.



#3 dianasaur

dianasaur
  • Topic Starter

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Wofford Heights, California
  • Local time:02:21 AM

Posted 03 June 2011 - 01:53 PM

Hello, cryptodan! :busy:

Thank you sooooo much for your time...this has been plaguing me for months and I really appreciate what you guys are doing. :inlove:

The MalwareBytes & SuperAntiSpyware logs are below; the GMER log was completely empty (the scan completed but GMER found no system modifications).




Malwarebytes' Anti-Malware 1.50.1.1100
www.malwarebytes.org

Database version: 6763

Windows 5.1.2600 Service Pack 3
Internet Explorer 8.0.6001.18702

6/3/2011 7:53:37 AM
mbam-log-2011-06-03 (07-53-37).txt

Scan type: Full scan (C:\|)
Objects scanned: 184404
Time elapsed: 13 minute(s), 17 second(s)

Memory Processes Infected: 0
Memory Modules Infected: 0
Registry Keys Infected: 0
Registry Values Infected: 0
Registry Data Items Infected: 0
Folders Infected: 0
Files Infected: 0

Memory Processes Infected:
(No malicious items detected)

Memory Modules Infected:
(No malicious items detected)

Registry Keys Infected:
(No malicious items detected)

Registry Values Infected:
(No malicious items detected)

Registry Data Items Infected:
(No malicious items detected)

Folders Infected:
(No malicious items detected)

Files Infected:
(No malicious items detected)

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

SUPERAntiSpyware Scan Log
http://www.superantispyware.com

Generated 06/03/2011 at 08:57 AM

Application Version : 4.53.1000

Core Rules Database Version : 7191
Trace Rules Database Version: 5003

Scan type : Complete Scan
Total Scan Time : 01:00:05

Memory items scanned : 217
Memory threats detected : 0
Registry items scanned : 5338
Registry threats detected : 0
File items scanned : 23153
File threats detected : 39

Adware.Tracking Cookie
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@www.clickmanage[2].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@www.googleadservices[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@legolas-media[2].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@ad.wsod[2].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@apmebf[2].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@statcounter[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@advertising[2].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@pointroll[2].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@cgi-bin[2].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@insightexpressai[2].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@collective-media[1].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@ads.pointroll[2].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@invitemedia[1].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@adinterax[1].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@adbrite[1].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@t3.trackalyzer[2].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@trafficmp[2].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@fastclick[2].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@ads.undertone[2].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@ads.bleepingcomputer[1].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@yieldmanager[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@atdmt[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@questionmarket[2].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@statse.webtrendslive[2].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@doubleclick[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@microsoftsto.112.2o7[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@content.yieldmanager[1].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@segment-pixel.invitemedia[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@ads.neudesicmediagroup[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@ad.yieldmanager[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@a1.interclick[1].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@adxpose[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@serving-sys[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@interclick[2].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@trackalyzer[1].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@kontera[2].txt
C:\Documents and Settings\John & Diana\Cookies\john_&_diana@mediaplex[2].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@revsci[2].txt
C:\Documents and Settings\John & Diana\Cookies\john & diana@ak[2].txt

#4 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:10:21 AM

Posted 03 June 2011 - 01:59 PM

Can you bring up a Elevarted Command Prompt by going to Start > All Programs > Accessories and right clicking on Command Prompt and select Run As Administrator.

I want you to type in the big black box the following:

path >> c:\my_path.txt

Navigate to C: via My Computer and open the text document with Notepad and Copy and Paste the results here.

Should look something like this:

C:\Users\cryptodan>path
PATH=C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell\v1.0\;c:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\Intel\WiFi\bin\;C:\Program Files\Common Files\Intel\WirelessCommon\;c:\Program Files (x86)\Common Files\Roxio Shared\DLLShared\;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\WinSCP\;C:\Program Files (x86)\QuickTime\QTSystem\


#5 dianasaur

dianasaur
  • Topic Starter

  • Members
  • 77 posts
  • OFFLINE
  •  
  • Gender:Female
  • Location:Wofford Heights, California
  • Local time:02:21 AM

Posted 04 June 2011 - 01:54 PM

Here's what I got from the elevated prompt:


path >> c:\my_path.txt -->
PATH=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\system32\wbem


@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

The new file showed up in the the last procmon log like this:


Name File Time Total Events Opens Closes Reads Writes Read Bytes Write Bytes Get ACL Set ACL Other

C:\my_path.txt 0.0007094 51 10 9 2 1 48 62 0 0 <bad>
C:\my_path.txt:BnhqlkugBim0elg1M1pt2tjdZe 0.0000429 4 4 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:CpdjxwbhN2qzewcmQpca1lvyXc 0.0000430 4 4 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:DocumentSummaryInformation 0.0000997 2 2 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Epgykx0vJecku24w1vbvh5k2Nh 0.0000215 2 2 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:OzngklrtOwudrp0bAayojd1qWh 0.0002949 10 10 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:PebiesnrMkudrfcoIaamtykdDa 0.0000642 6 6 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:QebiesnrMkudrfcoIaamtykdDa 0.0001069 10 10 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Raec25ph4sudbf0hAaq5ehw3Nf 0.0000319 2 2 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:SebiesnrMkudrfcoIaamtykdDa 0.0000220 2 2 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:SummaryInformation 0.0001426 13 13 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Docf_BnhqlkugBim0elg1M1pt2tjdZe 0.0000424 4 4 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Docf_CpdjxwbhN2qzewcmQpca1lvyXc 0.0000424 4 4 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Docf_DocumentSummaryInformation 0.0000221 2 2 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Docf_Epgykx0vJecku24w1vbvh5k2Nh 0.0000213 2 2 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Docf_OzngklrtOwudrp0bAayojd1qWh 0.0001090 10 10 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Docf_PebiesnrMkudrfcoIaamtykdDa 0.0000636 6 6 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Docf_QebiesnrMkudrfcoIaamtykdDa 0.0001071 10 10 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Docf_SebiesnrMkudrfcoIaamtykdDa 0.0000224 2 2 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:Docf_SummaryInformation 0.0007294 13 13 0 0 0 0 0 0 0 <bad>
C:\my_path.txt:{4c8cc155-6c1e-11d1-8e41-00c04fb9386d} 0.0000120 1 1 0 0 0 0 0 0 0 <bad>

I've been seeing this a lot lately...what does all the text after the colon mean?


Also, not sure if this helps, but I was poking around other bootlogs today and found some more filenames that seem to always appear in the logs but are never visible from Windows:

C:\Documents and Settings\<username>\ntuser.man (one of these wherever there's an ntuser.ini file)
C:\Documents and Settings\<username>\d
C:\Documents and Settings\<username>\explorer.exe
C:\Documents and Settings\<username>\framedyn.dll
C:\Documents and Settings\<username>\fxsst.dll
C:\Documents and Settings\<username>\moricons.dll
C:\Documents and Settings\<username>\netshellicon
C:\Documents and Settings\<username>\ntshared.chm
C:\Documents and Settings\<username>\rsaenh.dll
C:\Documents and Settings\<username>\services.msc
C:\Documents and Settings\<username>\shell32.dll

bootme.ini (found on at least three of the machines in various locations)


Thanks again :)

#6 cryptodan

cryptodan

    Bleepin Madman


  • Members
  • 21,868 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Catonsville, Md
  • Local time:10:21 AM

Posted 04 June 2011 - 02:54 PM

Please follow the instructions in ==>This Guide<==.

Once the proper logs are created, then make a NEW TOPIC and post it ==>HERE<== Please include the link to this topic in your new topic and a description of your computer issues and what you have done to resolve them.

If you can produce at least some of the logs, then please create the new topic and explain what happens when you try to create the log(s) that you couldn't get. If you cannot produce any of the logs, then still post the topic and explain that you followed the Prep. Guide, were unable to create the logs, and describe what happens when you try to create the logs.

Once you have created the new topic, please reply back here with a link to the new topic.

#7 Budapest

Budapest

    Bleepin' Cynic


  • Moderator
  • 23,579 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:21 PM

Posted 05 June 2011 - 06:02 PM

Malware topic here: http://www.bleepingcomputer.com/forums/topic401963.html

Now that your log is properly posted, you should NOT make further changes to your computer (install/uninstall programs, use special fix tools, delete files, edit the registry, etc) unless advised by a Malware Removal Team member, nor should you continue to ask for help elsewhere. Doing so can result in system changes which may not show it the log you already posted. Further, any modifications you make on your own may cause confusion for the helper assisting you and could complicate the malware removal process which would extend the time it takes to clean your computer.

From this point on the Malware Removal Team should be the only members that you take advice from, until they have verified your log as clean.

Please be patient. It may take a while to get a response because the Malware Removal Team members are very busy working logs posted before yours. They are volunteers who will help you out as soon as possible. Once you have made your post and are waiting, please DO NOT make another reply until it has been responded to by a member of the Malware Removal Team. Generally the staff checks the forum for postings that have 0 replies as this makes it easier for them to identify those who have not been helped. If you post another response there will be 1 reply. A team member, looking for a new log to work may assume another MR Team member is already assisting you and not open the thread to respond.

To avoid confusion, I am closing this topic.
The power of accurate observation is commonly called cynicism by those who haven't got it.

—George Bernard Shaw




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users