Jump to content

Ried

Staff
  • Posts

    1,337
  • Joined

  • Last visited

Everything posted by Ried

  1. Hello PBB13, Do you still require assistance?
  2. Hello PBB13 and welcome to Malwarebytes. Windows Defender is usually pretty good at detecting and removing these, have you tried scanning with Defender? If Windows Defender did not take care of it, try clearing the browser cache: 1. Open Edge and in the upper right area, click the icon that looks like 3 horizontal lines 2. Next, click the 3rd icon from the right, that looks like a clock with a circle arrow. This will bring up the History 3. In the next panel, click the 'Clear all history' link 4. Now you can select which you want to clear. Place a check in the box next to 'Cached Data and files' 5. Press the Clear button Close Microsoft Edge, then re-open it. Are you still seeing IP blocks? Regards, Lisa
  3. Valinorum - please close this topic. I am assisting this customer on the HelpDesk - thanks.
  4. Hello and I'm sorry, I did not receive a notification that you had replied. Yes, but back up your important documents first.
  5. There is something wrong with the Operating System. Do you have the Windows 7 Professional install disc?
  6. That's good, registry cleaners are not recommended at all. All Registry Cleaners are prone to causing damage/corruption to the Registry. The Registry is the single most important component in your Operating System. Once corrupted, often times the best recourse is to perform a wipe of the machine. Unfortunately, the corruption is seldom evident immediately. They manifest themselves as inexplicable issues further down the road. Here are several good write ups about Registry Cleaners: http://ask-leo.com/why_do_registry_errors_keep_coming_back.html?awt_l=Dhx.J&awt_m=1aAVzHWMMZdfbL https://blog.malwarebytes.org/social-engineering/2015/06/digital-snake-oil/ https://support.microsoft.com/en-us/kb/2563254 Uninstall McAfee for now and do not reinstall it at all for the moment. After you uninstall McAfee, do the following in the order given: 1. Run mbam-clean.exe and reboot 2. Try again to install Malwarebytes Anti-Malware 3. Regardless of whether or not MBAM installs, try again to run mbam-check.exe and send me the CheckResults.txt
  7. Thanks, Kiyah. I'm seeing all sorts of errors with McAfee (look at the lower portion of the Addition.txt) You have WinPatrol loaded and running, as well as HitManPro. For now, Uninstall both of them so we can rule them out as interference. Reboot and try again to run mbam-check.exe. Right click it and select Run as Administrator. One more question, when is the last time you used Little Registry Cleaner? Do NOT use it, I just need to know if you've run it in the past month.
  8. Thanks, Kiyah. I'd like to see a new set of logs from FRST64.exe. You will have to direct the tool to create the Addition.txt this time: 1. Double click FRST64.exe to launch the tool 2. Place a check in the box next to 'Addition.txt' 3. Now click the Scan button. Please send me both the FRST.txt and the Addition.txt. Also, according to the previous Addition.txt you sent, you are almost out of room on the C:\ drive - you have less than 1 GB left. Are there any programs you can uninstall or can you move pictures or music or whatever is taking up all that space, to another drive? What is your D:\ drive?
  9. Hello Kiyah, It could also be McAfee interering. Disable McAfee and try again. Also, click Start>All programs>Accessories and right click Command Prompt. Select Run as Administrator. Type the following into the black box, exactly as you see it below: set>"%userprofile%\desktop\setlog.txt" Within seconds, a setlog.txt will have been saved on your desktop. Please attach that in your next reply.
  10. Kiyah - as soon as it's charged up again, would you please run mbam-check.exe - with MBAM installed as it is now, and send me the CheckResults.txt?
  11. Ah, I see now, thanks. I've downloaded it, really appreciate the upload. It may be several days, or even next week as tomorrow is Friday. I'll get back to you as soon as I hear something.
  12. I'm sorry for the delay, I was waiting for you to run Procmon and send me a link to the log. I still think you likely have OS issues, but please run Procmon as previously instructed and send me the link once you have it uploaded
  13. Hello baedric, I have replied to your HelpDesk ticket. As we'll be working via that venue, this topic shall be closed to avoid confusion.
  14. There is no reason you should have to use an older version. To me, this indicates some serious Operating System issues and you may want to consider performing a Repair install. Let's see what comes back with Process Monitor.
  15. Have you tried installing it in Safe Mode? If not, try that now - just reinstall it over itself. If it still gives the error message, would you mind collecting a special Process Monitor log for me to share with our QA department and see if they can spot where the problem lies? If so, here is the procedure. (It looks a lot more difficult than it really is) First, create a new folder on your desktop called Logs Next, download Process Monitor from here and save it to your desktop http://live.sysinternals.com/Procmon.exe Right click Procmon.exe and select Run as Administrator In Process Monitor, click on File at the top and select Backing Files… Click the circle to the left of 'Use file named:' and click the … button Browse to the Logs folder you just created and type MBAM Log in the File name: box and click Save Exit Process Monitor. The idea here is to capture the internal Windows activity but we don't want a huge logfile to wade through. Double click the mbam-setup.exe file to start the install again (no need for mbam-clean, just install over the top of itself again). Once you do that, Right click Procmon.exe and run as Administrator. You won't notice it, but It will begin logging at this point - continue with the installation of mbam - let Procmon keep running. Once you see that error message, close Process Monitor. The log will have been saved automatically to the Logs folder you created on your Desktop. Right-click on the Logs folder and select 'Send To' and select Compressed (zipped) Folder The zipped log will be too large to upload to attach here, so please upload it to wetransfer.com and send me the link to the download.
  16. Thanks. Do you see a desktop icon and if so, what happens if you double click it?
  17. At what point of the installation do you see this error?
  18. Thanks, Webroot left all the altered Policies. Let's set those back to default and see if that helps. Turn off McAfee completely so it does not interfere with this fix, nor the install of Malwarebytes. We also don't want McAfee kicking in during the reboot so make sure it is off. Download the attached Fixlist.txt and save it in the same location as FRST64.exe 1. Double click FRST64.exe to launch the tool 2. When the tool opens, click the FIX BUTTON. 3. Once it has finished, a Fixlog.txt will open and also have been saved in the same location the tool was run from. Attach the Fixlog.txt in your next reply so I can verify the corrections took place. Now please try again to install Malwarebytes. Run mbam-clean first, reboot, then install Malwarebytes. Any luck? Fixlist.txt
  19. You're welcome Kiyah, Since you had trouble uninstalling Webroot, I'd like to get a new FRST log to make sure all the policy changes were reversed. Double click FRST64.exe and click Scan. Please attach the new FRST.txt in your next reply.
  20. Hello Kiyah, I work the HelpDesk and also QA and to help save you more waiting time, I'll work with you in here. Webroot has changed a lot of policies on the machine and may be interfering with the installation. Uninstall Webroot, reboot, then try again to install Malwarebytes. Let me know how that goes.
  21. Donetao - Since this is the 2nd time you've brought this up - I will state clearly for all that you did not get into trouble for your views on that feature and your issues with TSF have nothing to do with this forum nor this topic. While you consider the build up of EventViewer logs on your machine to be a nuisance, please bear in mind that recent, past Event Viewer information is helpful to forum Helpers from a diagnostic standpoint - which is why thisisu changed JRT to no longer automatically clear them. The tool still has the ability to clear EventViewer logs, you just have to trigger it to do so. Also, as you mentioned, you have other programs at your disposal to clear them if you want them cleared. **edit** This post was in response to a member whose post had since been deleted
  22. We'll close this thread. Will send you another PM about what to do next.
  23. Hi Kim, It has nothing to do with us being buried nor changing systems. I have been replying to you and I've attached screenshots of my replies on Feb 8th, Feb 9th and Feb 11th. (I've truncated most of the content in the screenshots to preserve your privacy) I don't know why you have not been receiving them. Are they in your Junk or Spam folder? It could be that your email client is now blocking these due to the length. I'll be sending you a PM (Personal Message) with a link to the HelpDesk where you can create an account and sign in there to view the ticket in full.
  24. I've got his ticket, closing this thread.
  25. Hi Steve, As we are now working together in the HelpDesk, I'll close this thread.
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.