Jump to content

smf61

Honorary Members
  • Posts

    28
  • Joined

Everything posted by smf61

  1. Just to show...screenshot attached
  2. UK site only still blocked for me, there is another thread about this in the Website Clocking forum here.
  3. Its blocking amazon.co.uk for me as well, amazon.com is OK though
  4. Oops, don't know how I missed that post. Did try the suggestions but no luck. Also don't see how Avira or MBAM can be blocking it and if so how to fix it
  5. I have found that a fresh install of 1.09 (no MBAE installed before) does not create the necessary autorun entry. On a reboot the service starts OK but there is no icon or flyout. Installing as an upgrade 1.08 is fine as well. Uninstalling 1.08 first and then installing 1.09 is also OK but hat is because the MBAE uninstaller never removes the autorun entry anyway. Running 64bit W10 with Avira free and MBAM.
  6. Seeing this as well (for the last few days) with a scheduled scan. If it helps this earlier thread seems to also cover the same issue https://forums.malwarebytes.org/index.php?/topic/170098-mbam-2181057-premium-launching-ui-at-first-scan-of-the-day/
  7. This has been reported several times before here and solved with setting an option in Trusteer. E.G. see this post https://forums.malwarebytes.org/index.php?/topic/167926-solved-trusteer-rapport-blocking-mbae-was-mbae-crashing-chrome/#entry958985
  8. Odd, in case it helps I am running MBAE with Chrome x64, MBAM & Avira on W8.1 and have not seen any crashes.
  9. In case it helps I had these products running fine together for some time on W8.1 x64. Webroot WSA MBAM premium (with realtime enabled) MBAE Chrome 32 & 64bit Make sure that the MBAE components are not showing as monitored (if so change to allowed) in WSA (click cog in PC Security menu). The latest version of MBAE usually takes a week or so before it is whitelisted by Webroot.
  10. Bit of confusion, I was not the original poster in that thread. I had this separate issue in this thread that was also with Chrome 64-bit so just wanted to be clear that is in the stable channel now. Thanks
  11. pbust, you just posted in this, now locked, thread that Chrome 64-bit was still in beta. It actually went in to the stable channel (as an optional install) in August with Chrome 37 so any issues are important. https://forums.malwarebytes.org/index.php?/topic/161952-solved-64bit-chrome-will-run-for-a-few-minutes-and-then-crashes/?p=918047
  12. Done a bit of testing with the settings in the Trusteer Rapport console. If I change the following setting from the default "always" to "never" then the Chrome starts fine. Hopefully there is a way that MBAE can be whitelisted. Block Browser Process Alteration: Trusteer Endpoint Protection blocks attempts to alter the browser's process. Altering the browser's process (AKA function patching) is a technique that allows taking over the browser and getting access to your sensitive information. This technique is used by malware but also by some legitimate software. Trusteer Endpoint Protection analyzes each process alteration attempts and blocks those that look suspicious.
  13. As you probably expected, still not working, same symptoms.
  14. Continuing a problem seen with the experimental build, 64-bit Chrome won't start with 1.05.1.1014 if Trusteer Rapport is also installed (see https://forums.malwarebytes.org/index.php?/topic/160672-chrome-crash-with-trusteer-rapport-mbae-10531010/#entry914492). Get a message "Chrome has stopped working" on startup but if either is disabled then Chrome starts OK. Windows 8.1 x64 Chrome 39 64-bit Webroot SecureAnywhere MBAM premium 2.0.3.1025 Trusteer Rapport 3.5.1404.24 MBAE 1.05.1.1014 final
  15. Thanks. Just tested this final build and am still getting a problem with Chrome 64-bit. Instead of "Chrome crashed.." error, I now see a "Chrome stopped working.." error on startup. As per the Known Issues I stopped TR to install MBAE. I will do some more testing then if still a problem will post (with logs) in the release support forum.
  16. OK thanks, I did not realise that was definitely the problem.
  17. Thanks, tried the new version and still getting the same crash with 64-bit Chrome.
  18. Just done the test and it seems to be OK when I switch to 32-bit Chrome.
  19. No Avast, I am using the products listed in the 1st post. Difference might be I am using the 64-bit release of Chrome, if I get time later I might try swapping to the 32-bit version.
  20. Should have thought of trying 1.04 again myself. Have reinstalled 1.04 and it works fine. Chrome starts and both the Rapport64 and MBA64 DLLs are showing against Chrome in Process Explorer.
  21. Can't remember, I have only recently gone back to Rapport. I did run 1.04 but it might have been only after I stopped using Rapport the first time. Tried looking at Rapport logs but they are all binary files. Rapport does not seem to detect MBAE as an issue, it just crashes Chrome seemingly via the Rapport DLL.
  22. Yes, Chrome works fine when either Rapport or MBAE protection are stopped (but still installed).
  23. Testing 1.05.3.1010 and find Chrome crashes on startup when MBAE is enabled. Works fine when MBAE protection is stopped. I see there was a known conflict with Trusteer but that is for install only. Windows 8.1 x64 Chrome 38 64-bit Avira AV Pro MBAM premium 2.0.3.1025 Trusteer Rapport 3.5.1404.21 MBAE 1.05.3.1010 Problem signature: Problem Event Name: APPCRASH Application Name: chrome.exe Application Version: 38.0.2125.111 Application Timestamp: 544718dc Fault Module Name: RapportGP_x64.DLL Fault Module Version: 14526.0.0.0 Fault Module Timestamp: 540eb95a Exception Code: c0000005 Exception Offset: 00000000000fe4e8 OS Version: 6.3.9600.2.0.0.256.48 Locale ID: 2057
  24. So how many people opened this thinking the subject was a statement rather than a question! A little more thought or the use of a "?" please.
  25. I have also done some testing with previous versions and see the issue with 1.62 and 1.65 as well (have not tried earlier). While I experience LAN transfer and audio issue with website blocking enabled I find the easiest way to test is with the LatencyMon utility.
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.