Jump to content

Recommended Posts

Hello gkarasik and welcome to Malwarebytes,

Download Farbar Recovery Scan Tool and save it to your desktop.

Note: You need to run the version compatible with your system (32 bit or 64 bit). If you are not sure which version applies to your system download both of them and try to run them. Only one of them will run on your system, that will be the right version.

If your security alerts to FRST either, accept the alert or turn your security off to allow FRST to run. It is not malicious or infected in any way...
 
  • Double-click to run it. When the tool opens click Yes to disclaimer.(Windows 8/10 users will be prompted about Windows SmartScreen protection - click More information and Run.)
  • Make sure Addition.txt is checkmarked under "Optional scans"
  • Press Scan button to run the tool....
  • It will make a log (FRST.txt) in the same directory the tool is run. Please copy and paste it to your reply.
  • The tool will also make a log named (Addition.txt) Please attach those logs to your reply.


Let me see those logs in your reply...

Thank you,

Kevin...
Link to post
Share on other sites

Ok, run the following:

Please download MBAM-clean and save it to your desktop.
 
  • Right-click on mbam-clean.exe icon and select user posted image Run as Administrator to start the tool.
  • It will ask you to reboot the machine - please do so.
  • Run the cleaner tool again, re-boot when complete. <<<---do not miss this step


Download & install the newset MBAM version.

Please download user posted imageMalwarebytes Anti-Malware
 
  • Install the progam and select update.
  • Once updated, click the Settings tab, in the left panel choose Detctions & protection and tick Scan for rootkits.
  • In the same tab, under PUP and PUM detections make sure it is set to Treat detections as malware.
  • Click the Scan tab, choose Threat Scan is checked and click Scan Now.
  • If threats are detected, click the Apply Actions button. You will now be prompted to reboot. Click Yes.
  • Upon completion of the scan (or after the reboot), click the History tab.
  • Click Application Logs and double-click the Scan Log.
  • At the bottom click Export and choose Text file.



Save the file to your desktop and include its content in your next reply.

If you have lost the activation licence key information it can be located here: http://www.cleverbridge.com/342/?scope=cusecolp

Let me know the outcome..

 

Link to post
Share on other sites

Please create an mbam-check log:

  • Download mbam-check.exe from here and save it to your desktop
  • Double-click on mbam-check.exe to run it, it should then open a log file
  • Please do not copy and paste the entire contents of the log into your next post, instead, please attach the log CheckResults.txt file which should now be located on your desktop to your next post.
  • Click on the Drag files here to attach, or choose files... below, to Attach the logs to your post
Link to post
Share on other sites

Problem solved. I removed a pair of user profiles I had created just prior to running MBAM. (I also went into C:\Users and deleted some leftover files and those user directories.) After that MBAM ran fine. It didn't find any malware.

 

So it appears that in its pre-operation phase MBAM ran across something in one or both of those new profiles that it didn't like and simply aborted, throwing the SDK/1812 error.

 

Might I suggest that it would improve the software if it could recover from this--perhaps throw a more-helpful informational dialog that told the user that MBAM had a problem with a particular user profile?

 

Thanks for your help.

GaryK

Link to post
Share on other sites

  • Root Admin

Unfortunately, there are a few issues that can cause this. The program attempts to read the profiles and looks for a couple of valid folder structures. When not found it can cause issues. In your case, my guess is that with that many accounts one or more of them have have been corrupted and caused the installer to fail.

I'm glad you were able to get it resolved and the program is now working for you.

Thank you

Ron

 

 

Link to post
Share on other sites

Thanks for all your reponses. MBAM is a great product, and I'm grateful it exists. You all do good work, and when there's a problem we MBAM-blessed users appreciate your willingness to help people.

Still, I want to propose an improvement: This particular error--SDKDatabaseLoadDefaults...1812--has existed since MBAM went to v2, and as it appears to be simply an error-handling problem, it seems that it wouldn't be that hard to improve the product in this regard. Exactly how MBAM reacts when it finds this particular structural anomaly-- something unexpected in a profile--is a choice made by the programmers.

Googling this error turns up a long history; many others have gotten the same error, and the response nearly always involves an arduous call-and-response where MBAM techs and users go back and forth running various anti-malware programs and turning in logs without finding any malware. In fact, reading through the reports of others who've reported this error, I don't find any instances where the cause seems to have actually been malware. I could be wrong.

In this particular instance though--a profile anomaly--the program certainly knows what's causing the error. Can't the error dialog say that? The error dialog could list several of the known causes of this error (since MBAM seem to know them), something like "Several things can cause this error, including an irregular profile structure. Please check any recently created user profiles. Also this error can be cause by (... .)." This might save everybody a lot of time and angst.

Just thinking out loud.

Thanks again..

GaryK

Link to post
Share on other sites

  • Root Admin

Hi Gary,

Yes, you're correct that "often" this is due to a folder structure issue and there is a routine in the program to try to check and correct. However, it would appear that in your case it was unable to correct it on its own. What caused that is unknown and would probably take a lot of analysis to determine why. We are currently working on the next 3.x version so it's very unlikely we'll be updating the program structure of the 2.x version at this time. The 3.x version is quite a bit different and I would not expect it to have this same issue.

Thank you again for the kind words and using the product.

Ron

 

Link to post
Share on other sites

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
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.