Jump to content

iam4iam

Members
  • Posts

    9
  • Joined

  • Last visited

Everything posted by iam4iam

  1. Here are the two check-results for comparison purposes (assuming that is a logical idea). CheckResults (with scan stuck in pre-scan operations).txt CheckResults (without scan in progress).txt
  2. The ticket on the help desk is concerning other issues. I wasn't expecting those to be "added" to this topic, but if it is not inappropriate to add them at this point, then I agree that would probably make more sense than corresponding via forum and email. I was going to attach the new check results without scan in progress (stuck in pre-scan operations) and the original check results (with scan in progress and stuck in pre-scan operations) for comparison purposes (perhaps a clue to why scan gets stuck), but I didn't realize the file overwrites each time mbam-check is run. I will try downloading the one I originally attached and renaming it so I can do this.
  3. I disabled "scan for rootkits" but the error persists. Requested logs are attached. (MBAM check log may not be helpful, because MBAM is "trying to" scan at the moment. The reason I say "trying to" is because it is stuck in "pre-scan operations," and I will have to reboot the system to correct this. (This a separate issue--which remains unsolved--that I reported via email.) I run mbam-check again after rebooting and attach it as well. Addition.txt CheckResults.txt FRST.txt
  4. Question 1: I have no idea. How do I determine this? Question 2: In theory, I would expect disabling the feature to resolve the issue, but it is only a "valid" resolution if the answer to question 1 is yes, Otherwise the issue is not resolved until the feature is working as it should.
  5. I am running MBAM 2.0.2.1012 (premium) and frequently get the error message "Malwarebytes was unable to load Anti-Rootkit DDA Driver." There is an image of the error message in another topic. I originally posted as a reply the topic linked in the previous sentence, but I was requested to start a new topic. Rebooting the computer apparently "fixes" the problem, but only for an arbitrary time, since the error message seems to appear almost every time a scan is run. I have not tried dis-enabling rootkit scanning, because that would not solve the issue. That would only mean I'm not getting to use a feature that I'm paying* to be able to use, and it's certainly not desirable to have to reboot in order to complete the scan process. Occasionally I choose "no" (if I am in the middle of another task on the computer when this occurs). Sometimes the error message reappears if I choose no. On one occasion, I had multiple error windows (with this message) at the same time. I am actually having other issues with MBAM (regarding the scheduling feature), but I reported those via email to support. I figured I would look in the forum for a resolution to this issue, since it didn't occur to me when I was reporting my issues with the scheduler. BTW, I'm running Windows 7 x64 on both of my computers and the same message occurs on both of them. *I'm not sure whether rootkit scanning is a feature on the free version, but regardless, it is a feature that I am supposed to have but which causes the scan process to not me to have to reboot the system frequently, and seemingly unnecessarily.
  6. i am running MBAM 2.0.2.1012 (premium) and frequently get the same error message regarding the Anti-rootkit DDA Driver. A resolution to this problem would please me greatly!
  7. Sorry for the poor forum etiquette. I guess I figured someone doing a search on this issue (which is what originally brought me here--and to the other topic where I posted updated links) would find the updated info useful.
  8. The first link in #2 above goes to a page that no longer exists. The second goes to a general MS help page. Here is the page that has the specific MS Fixit tool for this issue. (I had to search for it.) fix randomly changed desktop icon (it also does other stuff) URL (in case link doesn't work): http://support.microsoft.com/mats/windows_file_and_folder_diag/ I tried it and it worked!!! I hate that "generic" icon with a passion. It is (only) a cosmetic issue, but it's irritating!
  9. I was happy to see whatmeworry?s glitch fixed. I was going to try the same thing, but the page linked to MS Fixit no longer exists.
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.