Jump to content

FunnyMoney

Members
  • Posts

    4
  • Joined

  • Last visited

Everything posted by FunnyMoney

  1. Thanks to you, too, Wide Glide, although I noticed that the examples in those links didn't seem to be very up to date. They didn't match what I was seeing. But, I got through it.
  2. I downloaded and ran Malwarebytes Rootkit program. I got a pop-up that said: Registry value "AppInit_Dlls has been found, which may be caused by Rootkit. I answered "No" to fixing this because I checked and found that AppInit_Dlls is a valid Microsoft dll. MBAR continued to run and scanned my system. It found no rootkits. I ran this in Windows 7 home normal mode...not safe mode. I may try that next.
  3. When I run Malwarebytes in Windows Safe Mode sometimes I get Disabled.Cryptsvc. Registry Data Items Detected: 1HKLM\SYSTEM\CurrentControlSet\Services\CryptSvc|Start (Disabled.Cryptsvc) -> Bad: (4) Good: (2) -> Quarantined and repaired successfully. And if I run it again...it looks ok. I later ran it again in Windows Safe Mode and got another Disabled.Cryptsvc. I looked at my registry and validated that it was set to 4 before I let Malwarebytes correct it. And validated that it did change it to 2. (4 = disabled and 2= automatic). I wondered what could be changing this so I tried various things on my computer in Normal Windows mode and kept checking to see if my registry and my services.msc had changed. Nothing I did changed this value from 2. Even when I went to Windows Safe Mode, just before I ran Malwarebytes again, I checked my registry and services.msc and it showed it was set to the correct setting of 2. So when I run malwarebytes it pops up with the same thing..the Disable.Cryptsvc change to 4 again. One thing that happened one time..just after going to Safe mode...it did a chkdsk..I let it complete and then did Malwarebytes...it did not show a problem right after that...but when I went back to Windows Normal mode then back to Safe mode and ran Malwarebytes again...I got the problem again. I think this might be a false positive...but I guess it could be a rootkit that is setting this condition...??? I am running Windows 7 Home edition.mbam-log-2013-12-19 (19-51-41).txt mbam-log-2013-12-29 (23-21-53).txt mbam-log-2013-12-30 (13-27-34).txt mbam-log-2013-12-30 (19-44-44).txt mbam-log-2013-12-30 (19-52-34).txt mbam-log-2013-12-30 (20-00-37).txt mbam-log-2013-12-29 (23-12-41).txt
Back to top
×
×
  • Create New...

Important Information

This site uses cookies - We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.