Author Topic: 13. repair Winsock & DNS Cache  (Read 6936 times)

0 Members and 1 Guest are viewing this topic.

Offline gnube

  • Newbie
  • *
  • Join Date: May 2014
  • Posts: 3
  • Karma: 0
    • View Profile
13. repair Winsock & DNS Cache
« on: May 22, 2014, 09:25:48 pm »
I ran the default set of fixes on a computer that had been badly infected. Malwarebytes removed over 1100 items. After that, computer could not get on internet. Fixes seemed to run reasonbly quickly until #13, which started over an hour ago, so I clicked on the 'stop' button, but now it just says "stopping, waiting for current repair to finish"
Guess I might need to kill the program! Any other ideas?

Offline Willy2

  • Hero Member
  • *****
  • Join Date: Oct 2011
  • Posts: 1165
  • Karma: 18
    • View Profile
Re: 13. repair Winsock & DNS Cache
« Reply #1 on: May 22, 2014, 11:56:40 pm »
- Can you make a screenshot of where the program is stalling ? And what is the message in CMD.exe ?
- If the program stalls at one repair then abort the program and re-run the program starting with the next repair after the repair where the progfram stalled. If the program stalls again repeat this procedure.
- Rerun the program and see if you can finish it in a normal way. All repairs together should take anywhere between 20 to ~ 40 minutes maximum to complete. when not, something's wrong.

Offline gnube

  • Newbie
  • *
  • Join Date: May 2014
  • Posts: 3
  • Karma: 0
    • View Profile
Re: 13. repair Winsock & DNS Cache
« Reply #2 on: May 23, 2014, 08:46:12 am »
Thanks for reply.
I killed the program, restarted it and ran the rest of the tasks.
All is well now.

Offline Shane

  • Administrator
  • Hero Member
  • *****
  • Join Date: Sep 2011
  • Posts: 9281
  • Location: USA
  • Karma: 137
  • "Knowledge should be shared not hidden."
    • View Profile
Re: 13. repair Winsock & DNS Cache
« Reply #3 on: May 23, 2014, 08:59:20 am »
On the repair one of the Windows commands must have frozen up, when that happens you can just close that cmd.exe window and the rest of the repairs so continue on. If it ever happens again take a screen shot of the cmd.exe window so I can see what command Windows had trouble with :-)

Shane

Offline gnube

  • Newbie
  • *
  • Join Date: May 2014
  • Posts: 3
  • Karma: 0
    • View Profile
Re: 13. repair Winsock & DNS Cache
« Reply #4 on: May 23, 2014, 09:07:48 am »
Will do.
Thanks for your quick replies and suggestions.