Jump to content

FremontPC

Honorary Members
  • Posts

    88
  • Joined

  • Last visited

Everything posted by FremontPC

  1. Michael - If unchecking "Start malicious website blocking when protection module starts" doesn't survive a reboot, then you may have a problem with your boot drive. I would suggest making a complete image of your drive with Macrium Reflect or the like (if you haven't done so recently), then run Crystal Disk Info on the drive to see what the SMART attributes are reporting. If that looks ok, then run chkdsk (check disk) with "Automatically Fix File System Errors" selected. The reason I say this is that the options you select in MBAM are stored in the Windows Registry and the Registry gets written to frequently. Problems writing to or reading from the Registry might be a warning sign that there is a problem with the disk. Aside from that, unchecking the system may take some time to respond when you uncheck the Malicious Website Blocking options in MBAM. You may click the option again, thinking you missed it the first time. This might result in the option being reselected (which would turn M.W.B. back on).
  2. Memo - You can leave Filesystem Protection enabled, just make sure both the checkboxes for Malicious Website Blocking are unchecked for now. BTW, I haven't noticed any delays with MWB enabled after the initial boot delay.
  3. Yeah, MBAM has been a pretty easy sell for home users, with the lifetime license. The Website Blocking is a great feature and certainly helps to keep the drive-by and malvertising vectors sealed up (along with Chrome and Flash Control or the like). Looking forward to the fix on this one!
  4. FWIW, I haven't really noticed much of any issue with Website Blocking after the initial startup.
  5. Chappy - I noticed that there was quite a lag between my attempt to uncheck Website Blocking and the checkbox actually clearing. During that time the CPU usage was elevated. What kind of system did you try it on?
  6. Chappyware - I'm looking for the answer to this too, but perhaps try the MBAM/ Task Manager test (in my last post) on whatever boxes you have, just to see if the CPU usage stays elevated when turning Website Blocking on or off. If so, then this might repro across many systems rather than just a handful.
  7. Ron, give this a shot - Start MBAM and Task Manager and arrange them side by side. Click on TM's Performance tab and then MBAM's Protection tab. Turn off Website Blocking in MBAM and notice what happens in TM. Once again, watch TM when you turn Website Blocking back on.
  8. Ron - Here are the reports generated after uninstalling MBAM and restarting twice (Acer Aspire 5251-1005). Edit: Removing the Appcompat registry entry made no difference, so I put it back in. CheckResults.txt dds.txt attach.txt
  9. JerryIrons (et. al.) - The XP system that I wrote of before has actually had this going on for months. It seems to run ok after boot, so the fellow hasn't been too impatient about it, but I was surprised when I used msconfig to disable everything but MS stuff, then finally narrowed it down to MBAM. Like I said, I haven't tried disabling just Website Blocking on that system yet, but I'll see if I can get to it today.
  10. Ron - Thanks for checking into this. I don't have access to the XP system, but I noted it as it was having a similar problem (no MBAM, normal boot). Didn't check it with only Website Blocking disabled yet. As for the Acer (Win7 64, as you can see), I don't know why Registry Mechanic is getting flagged, that folder isn't present in the Program Files or Program Files(x86) nor is it in the list of installed programs. Agree with you on that, in any case. Chalk it up to user thrashing, but it wasn't on the system when I ran the reports. I will remove MBAM and reboot twice, then re-install.
  11. I'll jump in on this one. The first is an Acer Aspire 5251-1005 with 4GB RAM and a Samsung 840 series 120GB SSD. See attached files. Usable in 30 sec. without Website Blocking, 80 sec. with. Boot without Website Blocking, then enable it and the processor runs at 100% for 20 sec. or so. The other is an older XP system (dual core 2.8 GHZ, 2GB RAM). Don't have the MBAM Check or DDS for you, but with MBAM disabled it boots in a reasonable time (Avira A/V), with MBAM enabled it hangs after login at the background for about 30 sec. attach.txt dds.txt CheckResults.txt
  12. Also try a wired connection to the router. If that doesn't work either, might not be a bad idea to follow AdvancedSetup's advice.
  13. Victory for Furnace!!!! Congratulations!!!!! How's your browsing speed now? Have you reinstalled ZA yet? FPC
  14. Try downloading the newest driver listed for your laptop from Toshiba's website (even if it's the same driver you already have), then uninstall your existing driver and run Setup for the driver you downloaded. You'll probably need the exact model number from the bottom of your laptop to get the right driver. If still no go, then go in to Network Connections, right click on the icon for the wireless connection and choose "Status". Click the Details button on that screen and let's have a screenshot of the results.
  15. BTW, I know you're running Vista, but Win7 does have an outbound firewall. You have to turn it on and it doesn't have as many bells and whistles as the 3rd party ones. Just in case you were considering it....
  16. Some AV's to consider: Avira MSE Avast (has it's own outbound firewall). I'd run MBAM Pro with any of these, with the proper exclusions set. ZA uninstaller from ZA: http://download.zonealarm.com/bin/free/support/download/clean.exe
  17. If it were on my bench, I would uninstall it. You might want to bounce this off of ZA support, perhaps they can help you ensure ZA isn't getting in the way.
  18. Centrino means it's using an Intel chipset rather than AMD or Nvidia. Some of the Nvidia chipsets had big problems and the wireless being flakey was one of the first symptoms of a motherboard failure on those units. So, next up: It's entirely possible that ZA's firewall is blocking your wireless connection in some manner. I'd consider removing it from the system. Really. You can always reinstall it after you get the system sorted out.
  19. What Brand/Model of laptop is it anyway? Does it use an Nvidia chipset (Nvidia sticker on the palmrest)?
  20. Could be a problem with your wirless router. Can you test it with another computer, or perhaps a wifi connection on your cell phone?
  21. Try hooking the laptop right to the router with a Cat5 cable (make sure the wired network adapter is enabled).
  22. Sounds like you're clear on that count! Next up, run Checkdisk: Click Start (or hit the Windows key on your keyboard) and open "Computer" to see a list of your drives. Right-click on C: and select Properties. Click on the Tools tab. Under Error-checking click the Check Now... button. Mark the box next to Automatically fix file system errors. Click on the Start button. When the message box pops up, click the Schedule disk check button and restart your computer. Once your computer restarts it will check the drive, don't press any keys so that it is allowed to do so. Checkdisk will finish up and your computer will boot in to Windows. When the system starts back up after the checkdisk, go back in to the screen where you found "Show window contents while dragging". There will be some presets: Adjust for best appearance Adjust for best performance etc. Choose one of them, OK it, then close down everything and restart the system. After the system restarts, go back in and put the settings back to how you prefer them, OK it and restart again. Check to see if the setting in question survives hibernation this time. Regards - FPC
  23. Run it again and click on "Perform an in-depth online analysis of this hard disk". Check the " Raw " value of: Reallocated Sector Count Current Pending Sector count Uncorrectable Sector count Let me know what it tells you. Thanks - FPC
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.