Author Topic: win32/siref & win64/siref  (Read 13013 times)

0 Members and 1 Guest are viewing this topic.

Yzed

  • Guest
Re: win32/siref & win64/siref
« Reply #30 on: October 11, 2013, 11:58:15 PM »
All done. Thank you for your help.

I am still having issues with windows. I created a new user profile, which returned all the normal functions, but then when I transfered my old profiles user data across, and it went back to the errors. It seems like it is limiting my admin access.

I am also getting a malawarebytes warning regarding an svchost file(log attached) and I checked in process explorer and I seem to have a lot of them running(svchost's). I also found there where a number of windows related processes that aren't running, with "[error opening process]" when i mouse over them. Except for one, which says something different(screenshot attached with mouse over the odd one out). The errored processes start from wininit.exe.

I'm hoping this is a settings or windows issue, and if that's the case, I will not waste your time with it. Just want to be sure it's not still related to any malware.

Offline magna86

  • Anti Malware Fighter
  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 4235
    • Ambulanta MyCity Forum - ASAP Member
Re: win32/siref & win64/siref
« Reply #31 on: October 12, 2013, 06:51:45 PM »
- Preform quick scan with Malwarebytes and post me created logs.
- Also, download FRST, check all boxes and run the tool by pressing Scan button. Post me created FRST logs as well.

Yzed

  • Guest
Re: win32/siref & win64/siref
« Reply #32 on: October 13, 2013, 01:31:14 PM »
Did a bit of research and found I had to open Process Explorer as administrator. That fixed the errors.

MalwareBytes found nothing. Log is posted

Offline magna86

  • Anti Malware Fighter
  • Avast Evangelist
  • Massive Poster
  • ***
  • Posts: 4235
    • Ambulanta MyCity Forum - ASAP Member
Re: win32/siref & win64/siref
« Reply #33 on: October 13, 2013, 05:34:57 PM »
Hi,

FRST log also doesn't show any malware activity. Posted log is clean.

You may just delete FRST and delete C:\FRST <= folder created by FRST tool.