Jump to content

Dymium

Members
  • Content Count

    34
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Dymium

  • Rank
    New Member
  1. I get the same error as before ---------------------------Malwarebytes Anti-Malware---------------------------SDKDatabaseLoadDefaults failed with code: 1812---------------------------OK ---------------------------
  2. checkdisk log: Checking file system on C:The type of the file system is NTFS.A disk check has been scheduled.Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 197632 file records processed. File verification completed. 339 large file records processed. 0 bad file records processed. 0 EA records processed. 10 reparse records processed. CHKDSK is v
  3. Hello, sorry for the delay, I've been pretty busy. I ran the clean install process exactly as described but I still get the "1812" error. I doubt it's related to a possibly-failing hard disk, since this same error occurs when MBAM is installed only to my primary SSD.
  4. Chkdisk log: Checking file system on C: The type of the file system is NTFS. A disk check has been scheduled. Windows will now check the disk. CHKDSK is verifying files (stage 1 of 5)... 172544 file records processed. File verification completed. 339 large file records processed. 0 bad file records processed. 0 EA records processed. 10 reparse records processed. CHKDSK is verifying indexes (stage 2 of 5)... 215208 index entries processed. Index verification completed. 0 unindexed files scanned. 0 unindexed files recovered. CHKDSK is verifying security descriptors (stage 3 of 5)... 172544 file
  5. I tried renaming mbam.exe to every one of your suggestions, but each time I ran it, I still got the strange error that I've been getting before.
  6. MBAM still does not run. I have attached the log. I'm not sure at all what is causing MBAM to have this error, since it doesn't give any hints,but I don't think it's likely to be malware, especially after all the scans I've done. _Windows_Repair_Log.txt
  7. I tried to run a scan, but I still get an error, even when enabling 'scan for rootkit'.
  8. Winrar was probably detected as malicious because I had modified its executable to change up a menu in its interface, which would have changed its MD5 hash. I got Winrar from its official website. Unfortunately, during Norton's scan, the executable was corrupted, and I uninstalled Winrar before getting your message. I've redownloaded and installed Winrar again (From the official site) and scanned its executable. Here's the results: https://www.virustotal.com/en/file/c5b0b3639aa04b4b43136d9b6dd79f45cbc25b2b9483d7969cbe27feb29e6dcc/analysis/ I have also attached the ComboFix log. ComboFix.txt
  9. Okay, I have run the scan. It didn't find anything major. For some reason it detected Winrar as having a malicious startup key, which was odd, considering that Winrar is a well-known program.
  10. MBAM once again fails to run the scan, this time with a similar (but different) error than the one I normally get: There's also more information about the error in the terminal window that appears when running Chameleon.
  11. Okay, restarted completely clean, and ran Malwarebytes. I get the same error: SDKDatabaseLoadDefaults failed with code: 1812
  12. MBAM runs, but when I try to run a scan, it produces the same error as it has been doing.
  13. I had no "0" folder so I exported the codeidentifiers folder instead.
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.