Jump to content

PaulBostock

Members
  • Content Count

    30
  • Joined

  • Last visited

Everything posted by PaulBostock

  1. As Trumph would say.........lock her up (this topic that is)........lol
  2. Just installed MB version 3.9.27 (from @treed link in post # 73) Rebooted with NO PROBLEMS. Thanks to all who had a hand in the fix.
  3. On reflection there could be something. On boot up & at around 60% the progress bar stops for about 5 to 10 seconds & then proceeds to the finish & the boot is completed. It has done this for ever & I have no idea what is going on. I have often thought that because I have a SSD it should be faster. But heck its booting up in 30 to 40 seconds anyways.
  4. Thanks @treed for the info on this issue. I too am puzzled by the performance issue. My iMac is a late 2015 & is maxed out spec wise. It has never exhibited any performance issues. It is very stable & runs very well. Boots up in about 30 to 40 seconds. Anyways thanks again, much appreciated.
  5. On July 31 this problem was first reported to MB via this forum/topic. Over a week ago. Like a number of other peopler here I am far from impressed by the way it has been handled by MB. I ditched the new version & went back to version 3.8.17. That works for me........for now. I only have one Mac to look after & my subscription is not up till December. Whilst I have lost some trust in MB It is not a complete loss of trust........yet. I am going to be watching what happens over the next days/weeks. Lets hope that MB can get this train wreck out of the ditch & back on the rails. I like this program, it works well for me & I want to keep using it, but after this muck up my renewal will not be automatic.
  6. Well I clicked on the links & they are all OK. I did the uninstall of the bad version & installed the old. Works fine. Why on earth Malwarebytes would not post this message directly to this topic is beyond me. Sloppy Sloppy Sloppy.
  7. Attention Malwarebytes: I have installed version 3.8.17..........Your flawed version is still available for download. Thats just plain SLOPPY Take it OFFLINE
  8. I have this boot problem on my late 2015 iMac running macOS 10.14.6 I had put a ticket to MB last week. Yesterday I was contacted by MB support & asked to install a new MB version.........which did not solve the issue. I also send in some reports to MB I keep my iMac running 24/7 & use the sleep function instead of powering down At this point I do have App Block active & will switch it off when I power down. I agree with nancyc. A lot of users may have boot issues & have not attributed it to Malwarebytes. I have had a Mac for over 10 years now & until now have never had an issue that caused my Mac not to boot up. One theory has been that only older Macs get this problem, but nancyc. has a 2017 Mac. So that blows that idea out of the water.
  9. Can the problem be software related? As an example I have Adguard (The App not the browser extension) in my open at login list. (As well as other programs.) On July 31 Apple released an updated Gateway Configuration Data #175. I have no idea, just thoughts
  10. Sorry, my comment was not targeted to anyone specific, other than people who may come on this topic for the first time & who have not been following it in detail over the past day or so. In regards to it being platform specific you are probably right. The mystery to me is that the mac's involved are both laptops & iMacs from a wide range of years.
  11. For the people who are NOT experiencing a problem please remember that you have to REBOOT your Mac for the problem to surface. Thanks
  12. I opened a ticket with Malwarebytes on this problem last week This afternoon I was provided with a new version of Malwarebytes for Mac: 3.9.24 It did not solve the issue for me. I have just sent in a file to help malwarebytes diagnose the issue So they are working on it. In the mean time I keep App Block off, that is where the problem is. (At least with me)
  13. So feeling brave & with Ad Block off I just installed the latest macOS supplemental update with no apparent issues. I noticed that on July 31 Apple released updated Gatekeeper configuration data # 175 For me it seems that the boot issues I experienced may be tied into the App Block. Thanks
  14. Thanks @treed for your update. I just did what was suggested earlier in this topic & switched off App Block. I then did a cold reboot with no problem. It booted up as normal in under a minute. Since the MB update the only problem I have experienced was my iMac hanging during the boot process. Once I got the iMac booted I experienced no further issues that I was aware of. I am running a late 2015 iMac with macOS 10.14.6 & have a SSD. I am also running the latest version of Adguard, the App not the browser extension. Thanks
  15. I have not tried that because post #12 seems to refute post # 6. I read post #12 saying there is still a problem after switching off the "App Block". Plus I would think that Malwarebytes would be releasing a "official fix" in the very near future, which I would prefer to wait for. I do not want to get into a situation where I cannot get my iMac rebooted. Thanks for your help.
  16. As noted above ( post #4) I had serious problems booting my iMac up after yesterdays MB update. Today Apple has issued a supplemental update for macOS 10.14.6. This update requires a reboot. Given the problem I had with my iMac (per post #4 above) I do not feel secure doing this. Can someone from Malwarebytes please give us all an update on a fix for the various problems we have encountered. Thanks
  17. I too have a problem. Late 2015 iMac running macOS 10.14.6 Just upgraded to MB 3.6.23 iMac stalled on startup after MB update. Refused to boot until I pulled the power cord & rebooted again. Need help please. Thanks
  18. @treed: It would be great to have dark mode on MB for Mac. It would be much easier on my eyesight & no doubt other users as well. What are the plans for introducing this feature? Thanks
  19. @treed. I have just downloaded & installed the latest version of MM. Ver 3.8.16 with no problems. An observation if I may. The MM version history on this website stops at ver 3.6 (December 2018) I believe that users of this program would find it usefull to see current versions listed. It would give users an up-to-date listing of changes have been made in the various updates . Thanks for your consideration.
  20. This was posted by Treed last December. We do not, and for good reason. You should not allow anything to scan Time Machine backups! Time Machine backups have a special, unique structure that can be very fragile if it is disturbed, and changes should not be made to Time Machine backups by anything other than Time Machine. Allowing a third-party program to alter the backups in any way can destroy the entire backup set. Worse, it can do so without making the problem immediately obvious. I've seen cases where people have somehow edited these backups outside of Time Machine itself, and the backup continues to work for a while. But then, when it's needed most, it fails and cannot be used to restore data. For this reason, my advice is as follows: With any backup system, it's important to have at least two different, redundant backups, created by at least two different backup programs. In my case, that is Time Machine to a Time Capsule plus an external drive, and Carbon Copy Cloner to a couple additional external drives. Since Time Machine backups can be fragile, never let anything other than Time Machine mess with them. Do not scan them with any antivirus software! If your machine gets infected and the malware ends up backed up, it can't hurt you unless you restore your machine from Time Machine to a point in time when the machine was infected. Once your machine is clean, all subsequent backups will be clean, and the malware present in older "snapshots" will eventually be flushed from the backup during normal pruning, once the drive becomes full.
×
×
  • 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.