Jump to content

siliconman01

Honorary Members
  • Posts

    394
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by siliconman01

  1. Attached are ns.exe,ccleaner.exe, and ccleaner64.exe ns.zip CCleaner64.zip CCleaner.zip
  2. Attached are hm.exe and superantispyware.exe zipped hm.zip SUPERAntiSpyware.zip
  3. This is from my MS Surface Pro tablet and should contain blocking info for Norton Security and CCleaner. Malwarebytes Anti-Ransomware.zip
  4. Here is the file. I didn't "Attach this File" on my previous post. Malwarebytes Anti-Ransomware.zip
  5. This is the requested files. It should contain info for when hm.exe was blocked and also Superantispyware.exe
  6. Using the latest SuperAntispyware V6.0.1212 but not running with real-time protection active. On initiating a full system scan by SAS, MBARW quarantined SuperAntispyware.exe as soon as it downloaded and installed the latest definitions and started to scan memory and the registry. Had to reboot to complete the quarantine process and then restore SuperAntispyware.exe.
  7. On running a system clean up with CCleaner V5.14.5493, MBARW attempts to quarantine CCleaner64.exe and locks up CCleaner.
  8. On running a full system scan using the latest version 22.5.5.15 of Norton Security, MBARW attempts to block NS.exe at the end of the full scan.
  9. When performing a HOSTS file update using HostsMan, MBARW quarantines hm.exe hm.zip
  10. Installed fine on Windows 10 x64 Professional Build 11102 along side MBAM and MBAE with Norton Security and Chrome as the default browser. Question is: Is there a benign test file that we can download and run which will trigger MBAR for testing ??
  11. Build 1043 does appear to have corrected the IE 11 fingerprinting issue on Windows 10 x64 Pro.
  12. I agree. It does not fix the IE 11 finger print issue on Windows 10 x64 Professional when attempting to download a program and selecting "Save As" to store the downloaded program to a different location instead of the default C:\Users\UserName\Download folder.
  13. This sounds like there will not be a fix incorporated within MBAE for this finger printing issue as I have described it using IE 11. Is that correct?
  14. For clarification of my explanation on post #189 -- My programs are typically installed at their default location such as C:\Program Files or C:\Program Files (x86). My D partition is for saving only the downloaded source of the various programs so that I have the various program installers readily available should something occur that requires me to have to uninstall/re-install a specific program. Malwarebytes Anti-Exploit is installed at C:\Program Files (x86)\Malwarebytes Anti-Exploit.
  15. I have a separate partition on my SSD Drive 0 where I save all of the most current downloaded program installers and updates. Each third party program download is saved to its own folder. This separate partition is labelled as the D partition. So, for example, when I download the latest MBAE version update, I would do a Save As to the D:\Common Updates All Computers\Malwarebytes Anti-Exploit folder. I save only the latest version update on the D partition for each of the programs installed on my systems.
  16. When 1031 was issued I updated to it and reported that it did not resolve the issue.
  17. Any luck on resolving this issue within MBAE? It is certainly annoying because it requires remembering to disable MBAE prior to any IE 11 downloads
  18. This applies to Windows 10 x64 Professional using IE 11. Found this MBAE-SVC crash event in EventLog Viewer this a.m.. Faulting application name: mbae-svc.exe, version: 1.8.1.1031, time stamp: 0x560592bd Faulting module name: mbae-svc.exe, version: 1.8.1.1031, time stamp: 0x560592bd Exception code: 0xc0000417 Fault offset: 0x0005e576 Faulting process id: 0x810 Faulting application start time: 0x01d0f9aaed2376ae Faulting application path: C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae-svc.exe Faulting module path: C:\Program Files (x86)\Malwarebytes Anti-Exploit\mbae-svc.exe Report Id: e4b76ac7-7761-4939-9358-69e23808c6ed Faulting package full name: Faulting package-relative application ID: It was followed by a second Error The Malwarebytes Anti-Exploit Service service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 120000 milliseconds: Restart the service. Data is attached. MBAESVCCrash.zip
  19. I sent the FRST64 logs via a PM to you. Thanks for your attention to this issue.
  20. Windows 10 and all software are the latest versions and up-to-date.
  21. Well, it's 100% repeatable on this machine.
  22. I am using IE 11, not Edge. The description of the steps are correct as you stated them. I just updated to Build 1031 and it is much worse. The finger printing exploit occurs just trying to attach the C:\ProgramData\Malwarebytes Anti-Exploit zipped folder to this post. As soon as I click on Browse to select the attachment, the exploit occurs. Malwarebytes Anti-Exploit.zip
  23. This applies to Windows 10 x64 Professional and using IE 11 as the browser. The finger printing exploit issue still occurs with build 1030. 1. Using IE 11, sign on to the MBAM forum and open the thread for the MBAE beta download. 2. Select to download MBAE Build 1030 3. Select "Save As" and start to navigate to where you want to save the download. 4. The fingerprint exploit will occur before you can "save as" A snapshot of the exploit window and the C:\Program Data\Malwarebytes Anti-Exploit folder is attached. ProgramData Folder.zip
  24. Thus far after 2 days of use, appears to be working fine on Windows 8.1.1 x64 Professional and Windows 10 x64 B10130 Tech Preview
  25. The version numbers on this website need to be updated. http://www.malwarebytes.org/downloads/ Also, please show the full version number instead of the clipped 2.1.4 (please show 2.1.6.1022). And also for the other programs displayed on this download page. TIA
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.