Jump to content

Klinker

Honorary Members
  • Posts

    46
  • Joined

  • Last visited

Reputation

0 Neutral
  1. I also noticed a decrease of roughly 20K less files scanned (Quick scan). Can somebody confirm that this is now the new "normal" ?. Thanks.
  2. It looks like this is fixed. A "detection change to correct an installation error" is what I read they have done, so it doesn't appear like there is anything to do on the user end of this. To test, I reinstalled the updates (again) and no new (or repeated) updates came up this time. I manually tried Windows Updates and none of the repeated updates are there anymore. Tried this on two different XP's....hope it works out for everybody else.
  3. I have the same problem, but with different KB updates on .NET. The updates are in computer, but for some reason, it keeps wanting to update the same updates over and over again. The file(s) it keeps updating are in some cases 0 kb big, so there is something really screwed up, Over on the Microsoft website, there are tons of posts that show XP machines are experiencing this same problem and I would suspect that as people fire up their machines across the time zones, we'll see more and more problems. Apparently Microsoft is aware (according to people posting over there) but a fix is not yet ready. There are several "Fixits" and workarounds available for the normal update issues over the years, however, they didn't work for me. In fact these fixes and workarounds are NOT working for most people due to the nature of this "latest problem", so I would recommend waiting until the fix comes out from Microsoft. You may get lucky and maybe one of these fixes will work for you, but for most people it's going to take a special fix from Microsoft.
  4. Running McAfee Total Protection..... they just updated their Security Center component to version 11.654 to "fix" some problems this week . Maybe something different in their "fix" that is blocking access that is too new for anybody else to see yet? Specifically I'm running the same firewall and real time scanning settings with McAfee as before when I've successfully accessed the clean utility. Also run Spywareblaster, but I wouldn't think that would matter. I tried the link a couple of more times and I can see the box which would allow the download in the background, but the IE error message pops up saying "IE cannot download....would not open/not available". I'm not sure my skills are advanced enough to provide any better reasons for why the link is getting blocked, sorry. Like I said earlier, it looks like the beta version downloaded and works o.k. without running the clean utility like I had to with the December upgrade so it's good from that standpoint.
  5. Thanks. I tried again, but I got the same IE error message that the website would not open/is not available. Perhaps my AV settings are blocking this somehow? Not sure why it isn't working for me because I had to use it back in Dec with most recent upgrade issues and it worked then. The whole reason I wanted to use the clean utility was because my new AV software install required that I uninstall MBAM first and since I am one of the XP users that had a problem with the new 1.6 version, I wanted to avoid any of those previous issues. As a work around to not being able to access the clean utility, I simply ran the regular uninstall through control panel and downloaded the beta version 1.6.1 since it was supposed to fix all the various issues. I successfully installed the beta version and ran a quick scan without any of the issues (crossing fingers) that I experienced with the 1.6 upgrade a few weeks ago so I think I'm o.k. without the clean utility. Still wondering why I couldn't access the utility link you provided, but if the beta version works, I guess it wasn't necessary to run the clean utility at this time.
  6. The mbam-clean.exe link seems to be broken. I even tried a few different posts in which the link is provided by different staff members/mods on this forum just to see if there was a mistake, but none of them are working. Is there an alternate link for mbam-clean.exe or another way to access this for a clean install? Thanks.
  7. Updated to 2012.01.03.04 database, closed, reopened and ran quick scan per your instructions. Ignore List was recognized and seemed to function normally. Will continue to close after database updates and run quick scans to check for Ignore List deletion. I'll try running two or three scans per day for greater sample size this week. Will update you as necessary to verify if closing/reopening before scanning resolves issue. Thanks.
  8. Ignore List deleting again after Quick Scan. Ignore List deleted using databases 2012.01.01.03 the other day and this morning using 2012.01.03.03. Everything else still seems to be functioning o.k. Seems to be random occurrence not impacted by every database update or restarting the computer each day, etc.
  9. Problem with Ignore List has come back. I checked the Ignore List after updating to 2011.12.30.02 database and the two items were in there, but after running Quick Scan, "Registry Value HKLM\Software\Microsoft\Security Center\FirewallDisableNotify" and "Registry Value HKLM\Software\Microsoft\Security Center\AntivirusDisableNotify" were identified again. Is it possible that there is an error in the database updates that are causing problems with the Ignore List? Yesterday (12/29)I didn't have the problem (database 12.29.03 and 12.29.04), but with today's above referenced database update it has come back. I see that there are other posts on here with the same issue. I really don't want to go through the clean install process again, because as an XP user, I'd rather deal with this nuisance than risk the program not working at all. Everything else seems to be working fine. One other possibility: I'm running McAfee Total Protection which of course disables the Security Center Firewall and Antivirus that Malwarebytes identifies. Is it possible that when McAfee updates or when there is a McAfeeServiceHost disruption (an ongoing and well known McAfee problem they're supposedly working on) that McAfee is resetting the Security Center Firewall/Antivirus and somehow your program is detecting that even if it's in the Ignore List? The McAfeeServiceHost issue acts almost like a flipping a light switch on/off briefly freezing McAfee, and then McAfee kind of resets itself as the ServiceHost error corrects itself. Don't know about the McAfee angle, just trying to think of what it could be that makes Malwarebytes think there is something going on even if it's in the Ignore List.
  10. That wasn't it. I'm going to assume that the files were corrupted on download or something......I just ended up doing a clean uninstall/install so everything seems to functioning fine now. Consider this issue resolved and close. Thanks.
  11. So if I understand this correctly, the "chameleon technology" eliminates the need to rename Malwarebytes (like is suggested in the Self Help Guide section)in certain circumstances on infected machines and also to work around active processes that might otherwise interfere (thus eliminating need for Rkill for example). It's basically a built-in work around on already infected machines so that users don't have to go through additional steps to begin cleaning their computer, is this correct? Also, I know there is no such thing as "100% effective" and things can change rapidly as new malware is developed constantly, but will this chameleon technology address the vast majority of the malware that currently interferes with running this product on infected machines?
  12. Haven't seen this issue yet, so I thought I would start a new topic. Subsequent to the the latest update 1.6, it seems that the ignore list is getting deleted after starting the computer each time and after database update through version 2011.12.28.02 . Ignore list items are: "Registry Value HKLM\Software\Microsoft\Security Center\FirewallDisableNotify" and "Registry Value HKLM\Software\Microsoft\Security Center\AntivirusDisableNotify" so it's not big deal, just a nuisance. When the ignore list deletes, it also won't save a log after running a quickscan. If I rerun a quickscan without shutting down or updating database then everything seems to function normally including a log. I haven't updated past 12.28.02 database, but will report back if this problem occurs with additional updates. This is an XP SP3 with McAfee Total Protection. Just like a lot of other people have mentioned, I couldn't update over top of the old version so I had to go the clean uninstall/reinstall route which eliminated the problems other XP users have already reported. The clean install process appears to be working o.k. with the exception of the deleted ignore list.
  13. Count me in too. Kaspersky, McAfee and ESET scans found nothing so wondering if it's a false positive. A second Malwarebytes scan was clean. Like the OP, could not find any other reference to this as malware.
  14. Error Message When Starting: Program Error Load Database (2,2, Create SDK) Error Message said to report error code to support team so I am. I was just going to uninstall and reinstall program, but maybe there is something else I am supposed to do?
  15. Update....I contacted an IT friend for more technical assistance on this issue. He said he was unaware of any conflicts as described (although he would be dealing with corporate licensing/products) and suggested I contact McAfee for clarification, but this time asking if it was just an installer conflict issue. I asked McAfee for clarification of conflicts and was told this time that in fact there is a conflict with their installer not only with MBAM but any other AV programs and that to successfully install McAfee any other AV programs would have to be deleted first. However, there is NO known conflict with MBAM as a stand alone scanner (which is how I use it). MBAM is still listed as a compatible program on their website, so obviously I was just given bad info from the techs. Therefore, based on this additional feedback from McAfee, it is my opinion that since there is a known conflict with the McAfee installer that the techs don't stray from their script and make the faulty conclusion that there is a conflict beyond the initial installation process with McAfee and other AV programs. Also of note, when I contacted the companies of other "compatible" AV programs as previously listed by McAfee, they also said that there is no known conflicts other than with the McAfee installer itself. After installation of McAfee, it would be safe to reinstall their products and they would work with McAfee. To summarize, it looks like any conflicts of MBAM (and other compatible programs) with McAfee is restricted to the installer ONLY. Whether McAfee has recently changed something in their installer that makes this more of a critical issue than before, I don't know, but it's pretty clear that the techs I spoke to at first improperly expanded this conflict beyond what they should have. Additionally, if there was truly a conflict outside of the installer I imagine you would have seen a large influx of issues or something would have shown up in your in-house testing. I will reinstall MBAM and re post in this thread should I experience any "real" conflicts. It's not like this is the first time that McAfee has given out bad information.
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.