Dave-H

Thanks. Yes, my v4.6.4 on Windows 10 was fine too when I checked it. However v3.5.1 on Windows XP was still not updating, but it is now. I guess it just took a bit longer for the fix to get through there! Cheers, Dave. 🙂

Thanks @Imacri that's a relief to hear! 🙂

Updating seems to have failed again here. Can anyone confirm? 🤔

Well I never, it's working again now! I'm now on version 1.0.31233. I guess it was a temporary problem after all, but it's still puzzling why one of my machines was acting differently from the other. As 1.0.31231 was the current pattern at the time, and both machines said they had it, the problem with the faulty machine wasn't that it couldn't download any updates, it was actually that it didn't recognise that the pattern file it had wasn't actually out of date.

Could be, although the root certificates are as up-to-date as they can be on both my XP machines. 🙂

Thanks @AdvancedSetup! I'm sure all machines are served equally of course, and always have been, but it's strange that one of my machines isn't now working to get updates, and the other one is, and others have reported similar problems now too. Yes, it could well be a setup problem that other installations might well have as well, but how do you troubleshoot this, bearing in mind that IIRC there is no technical support for version 3.5.1 now? 🤔

Thanks for that, those of us who still use Windows XP on legacy machines, for whatever reason, are well-used to being told that we shouldn't be still doing it! If and when Malwarebytes drops pattern file downloads for version 3.5.1, we will all accept it of course, we're very lucky to have had a working security program on XP for so long, but I think we have always assumed that when and if this facility is dropped, it won't suddenly stop at some arbitrary time with no prior warning given. I have two XP machines, both are on pattern file 1.0.31231. One of them says it's fine, and if I do a manual update check, it says 'Checking' and then says 'Current' as I would expect. The other machine says the pattern is out of date, and shows a red exclamation mark triangle on the tray icon. If I do a manual update on that machine, it says 'Checking' and then just goes back to 'Check for updates' again without doing anything. So, the system is presumably actually working, but on some machines and not others! 🤔

Just to add to this, I'm seeing this exact problem too on Windows 10, an instance in every session. Using MB Premium 4.6.0 on Windows 10 22H2 x64. I think it probably started after the last MB update. The errors have been logged every day for the last six days. Source Malwarebytes Native Message Service Summary Stopped working Date ‎06/‎09/‎2023 16:06 Status Report sent Description Faulting Application Path: C:\PROGRAM FILES\MALWAREBYTES\mbambgnativemsg.exe Problem signature Problem Event Name: BEX64 Application Name: mbambgnativemsg.exe Application Version: 4.0.0.126 Application Timestamp: 645000d3 Fault Module Name: mbambgnativemsg.exe Fault Module Version: 4.0.0.126 Fault Module Timestamp: 645000d3 Exception Offset: 00000000001f5aa5 Exception Code: c0000409 Exception Data: 0000000000000007 OS Version: 10.0.19045.2.0.0.256.48 Locale ID: 2057 Additional Information 1: 3bd1 Additional Information 2: 3bd19d49899070446826c757be6edc05 Additional Information 3: fb83 Additional Information 4: fb838de8386a01bd59fc4926b604cdb0 Extra information about the problem Bucket ID: 39be78d85ee2bee85bc096f25122149d (1999764202039940253) Thanks, Dave. 🙂

Deleted - wrong section!

I've been using Malwarebytes Premium 3.5.1 for years on the XP side of my dual boot machines, and I'm very grateful that it still works after all this time. I never expected direct technical support to be available for 3.5.1 indefinitely, but I had assumed that pattern updates would be provided for as long as they are compatible with the program. I hope that is still the case, I can see no reason to discontinue them just for the sake of it. Yes, old operating systems are potentially vulnerable, but as has been said, why would hackers bother now when their user base is now so small? In any case, Malwarebytes is still doing its job there, and any protection is better than no protection! At the very least I hope that if the decision is made not to provide pattern updates any more, that a reasonable notice is given of this, so people can research alternatives, if they are available. 🙂

OK, that's great. I would say that maybe the developers should look at this problem though. MB setup should not really use absolute paths for things like this, as it is surely not uncommon for people to customise things like the location of browser profiles. MB setup should be able to find them wherever they are. Thanks everyone for their input on this. Cheers, Dave. 🙂

Thanks all! @Porthos One machine (the original with the problem) is 64 bit with 64 bit Firefox, the other (the new MB install with the same problem) is 32 bit, so I don't think this is relevant. @AdvancedSetup I will do those tests and report back. I can't do it today I'm afraid, but I will do it tomorrow. @Ried The only thing not standard on Firefox is that the Firefox user profiles on both machines are stored in C:\Program Files\Firefox\Profile folders, and not in Users\....\AppData\Roaming\Mozilla.... folders where they would normally be stored by default. That's just because that's the way I like it, and it's a perfectly valid Firefox installation option. I'm now wondering if that's why MB can't find the profiles though. 🤔

I've just looked in the logs at mbsetup.log, and this must be significant. 2022-12-05 19:15:58 (UTC -0000) d:\jenkins\workspace\a_mb4_mbsetup\src\mbsetup\mbsetup.cpp:2909: Checking BG for Chrome: 2022-12-05 19:15:58 (UTC -0000) d:\jenkins\workspace\a_mb4_mbsetup\src\mbsetup\mbsetup.cpp:2936: Checking BG for Edge: 2022-12-05 19:15:58 (UTC -0000) d:\jenkins\workspace\a_mb4_mbsetup\src\mbsetup\mbsetup.cpp:2943: Edge Ext Folder: C:\Users\Dave\AppData\Local\Microsoft\Edge\User Data\Default\Extensions\ihcjicgdanjaechkgeegckofjjedodee 2022-12-05 19:15:58 (UTC -0000) d:\jenkins\workspace\a_mb4_mbsetup\src\mbsetup\mbsetup.cpp:2952: Found Edge Ext Folder 2022-12-05 19:15:58 (UTC -0000) d:\jenkins\workspace\a_mb4_mbsetup\src\mbsetup\mbsetup.cpp:2963: Checking BG for Firefox: 2022-12-05 19:15:58 (UTC -0000) d:\jenkins\workspace\a_mb4_mbsetup\src\mbsetup\mbsetup.cpp:3011: Firefox Ext not found - prompt to install BG It would appear that the setup found the Browser Guard extension in Edge, but could not find it in Firefox, where it is also installed. I can't see why that would be. What Firefox folder would it have been looking for? 🤔

Just as an update, it would appear that ihcjicgdanjaechkgeegckofjjedodee is the Chrome extension ID of Browser Guard itself. The other ID fmgckcapmffomaifonnhgkfdgljnkpgi does not produce any relevant results on a search I did say that I'd never had a Chromium browser on the machine, but of course I've now remembered that Edge is a Chromium browser now! 😁

Interesting, I didn't think that I'd ever had any version of any Chromium browser on that machine! Yes, I'm aware I can dismiss the warning, that's what I ended up doing on the first machine in fact. It was just when the same thing happened on the new MB install on the second machine, I was intrigued and decided to ask here in case it was a known issue that could be fixed. Thanks, Dave. 🙂

Thanks Porthos, here are the logs. This was done on the machine with the brand new clean installation of Malwarebytes Premium. This is what I'm seeing BTW. mbst-grab-results.zip

The second machine is a clean install! I've only just installed MB on it, it has never been there before. The first machine has had it for a while. The fact that the problem immediately also appeared on a brand new clean install is what prompted me to ask here about it. Uninstalling and reinstalling on the second machine surely cannot make a scrap of difference, as it's a new install anyway. As I said earlier, there is no evidence of any other malfunction in MB, on either machine. This surely has to be a bug. 🙂 Off to bed now anyway, it's late here in England! I'll pick up any replies tomorrow. Cheers and goodnight, Dave.

Those two are the only ones on both Windows 10 installations. They are both multi-boot machines, but surely MB shouldn't be seeing browsers that are installed on other operating systems which aren't running! 🙂

2.5.5 🙂

On two different computers, I'm running MB Premium 4.5.18, one 32 bit and the other 64 bit. Both under Windows 10 22H2. On both of them, there is a nag on the homepage of MB saying there are things needing my attention, and it says that Browser Guard should be installed. On both machines, Browser Guard is installed, on both Firefox and Edge! I've tried uninstalling it and reinstalling it several times, but there is no difference. Why is MB Premium showing me it's not installed when it is, and how can I tell it that it is installed? MB Premium is working perfectly on both machines in every other respect. Thanks, Dave. 🙂

Why are you running such an old version? Are you running an operating system that 3.5.1 won't work on? That is the last version for Windows XP. 🙂

Seems OK here with version 3.5.1. 🤔

Yes, all fine here now too. Thanks for the quick fix, and of course for carrying on the pattern updates support for the legacy version in the first place! It's much appreciated. 👍

Confirmed. ☹️

That's really good to hear, thank you very much! 👍😍👍