Jump to content

Welcome to Geeks to Go - Register now for FREE

Geeks To Go is a helpful hub, where thousands of volunteer geeks quickly serve friendly answers and support. Check out the forums and get free advice from the experts. Register now to gain access to all of our features, it's FREE and only takes one minute. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more.

Create Account How it Works

Problems with dnsapi and others

  • Please log in to reply



    New Member

  • Member
  • Pip
  • 6 posts

Hola, bueno, he estado notando cosas extrañas en la computadora, te he dado una exploración de Frs. Hitman pro detecta dnsapi pero no lo borro, ya que sale de nuevo.




Hitman pro detecta dnsapi pero no lo elimina

Attached Files

Edited by selohu, 25 July 2017 - 11:12 AM.

  • 0




    Malware Expert

  • Expert
  • 23,727 posts
  • MVP
Download the attached fixlist.txt to the same location as FRST
Run FRST and press Fix
A fix log will be generated please post that 
Open an elevated command prompt:
If you open an elevated command prompt it will by default open in c:\Windows\system32
Once you have an elevated command prompt:
 DISM  /Online  /Cleanup-Image  /RestoreHealth
 (I use two spaces so you can be sure to see where one space goes.)
Hit Enter.  This will take a while (10-20 minutes) to complete.  Once the prompt returns:
Reboot.  Open an elevated Command Prompt again and type (with an Enter after the line):
sfc  /scannow
This will also take a few minutes.  
When it finishes it will say one of the following:
Windows did not find any integrity violations (a good thing)
Windows Resource Protection found corrupt files and repaired them (a good thing)
Windows Resource Protection found corrupt files but was unable to fix some (or all) of them (not a good thing)
If you get the last result then type:
findstr  /c:"[SR]"  \windows\logs\cbs\cbs.log  >  \junk.txt 
Hit Enter.  Then type::
notepad  \junk.txt 
Hit Enter. 
 Copy the text from notepad and paste it into a reply.
After you finish SFC, regardless of the result:
1. Please download the Event Viewer Tool by Vino Rosso
and save it to your Desktop:
2. Right-click VEW.exe and Run AS Administrator
3. Under 'Select log to query', select:
* System
4. Under 'Select type to list', select:
* Error
* Warning
Then use the 'Number of events' as follows:
1. Click the radio button for 'Number of events'
Type 20 in the 1 to 20 box
Then click the Run button.
Notepad will open with the output log.
Please post the Output log in your next reply then repeat but select Application.  (Each time you run VEW it overwrites the log so copy the first one to a Reply or rename it before running it a second time.)
Run FRST again as before.  Make sure Addition.txt is checked and hit Scan.  Post both logs.
Run FRST again as before.  Make sure Addition.txt is checked and hit Scan.  Post both logs.

  • 0

Similar Topics

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users

As Featured On:

Microsoft Yahoo BBC MSN PC Magazine Washington Post HP