Jump to content

Recommended Posts

We have released a new beta build to correct the following

Fixed: Users report to lose connection (visibility) to the LAS or Network Neighborhood after upgrading to CU19
https://forums.malwarebytes.com/topic/262752-malwarebytes-42-beta/?do=findComment&comment=1416567

 

Please enable beta updates and then check for updates

NOTE: Please close all open applications before running this update installer. It is a mandatory reboot of the computer. Unsaved documents will be lost.

 

 

Edited by AdvancedSetup
updated information
Link to post
Share on other sites

A very quick test suggests that this fault has been fixed. More testing to follow over the day or three.

FWIW I can report that this update (of only the component pack) did not demand a mandatory reboot, merely a restart of the Malwarebytes application under Windows 10.

Link to post
Share on other sites
15 minutes ago, Pluto said:

A very quick test suggests that this fault has been fixed. More testing to follow over the day or three.

FWIW I can report that this update (of only the component pack) did not demand a mandatory reboot, merely a restart of the Malwarebytes application under Windows 10.

Thank you for the feedback. I would suggest you still go ahead and restart the computer

 

Link to post
Share on other sites

Thank you @Pluto

Can you please try saving your current firewall settings. Then make a new System Restore Point and disable the following software application and reset the firewall to defaults temporarily

HKLM\...\Run: [Malwarebytes Windows Firewall Control] => C:\Program Files\Malwarebytes\Windows Firewall Control\wfc.exe [644784 2020-08-22] (Malwarebytes Inc -> Malwarebytes)

You might also want to review and consider removing restrictions unless you specifically set them.

GroupPolicy\User: Restriction ? <==== ATTENTION
HKLM\SOFTWARE\Policies\Mozilla\Firefox: Restriction <==== ATTENTION
HKLM\SOFTWARE\Policies\Google: Restriction <==== ATTENTION
HKU\S-1-5-21-4294570440-570648401-489032097-1002\SOFTWARE\Policies\Google: Restriction <==== ATTENTION

 

Update your Google Chrome and remove these 2016 updaters

Task: {63EFE5D2-3395-481A-BC19-080FEE749404} - System32\Tasks\GoogleUpdateTaskMachineUA => C:\Program Files (x86)\Google\Update\GoogleUpdate.exe [153752 2016-11-16] (Google Inc -> Google Inc.)
Task: {EABD7320-DA9F-4C8A-8DF7-B396E886883A} - System32\Tasks\GoogleUpdateTaskMachineCore => C:\Program Files (x86)\Google\Update\GoogleUpdate.exe [153752 2016-11-16] (Google Inc -> Google Inc.)

 

One of the logs Additions.txt did not complete for some reason.

Please try restoring the firewall. Then restart the computer and let me know if that works or not

Late for me so I'll check back on you again tomorrow

Thanks

 

Link to post
Share on other sites

This is all appreciated but the amount of time I have available to explore this issue is very limited so, please, let's not loose sight of the fact that prior to component pack 1070 this all worked!

So what changed in this department with 1070? I really do not have the time to strip this machine back to basics to work this one out. Whatever happened to the old mantra to permit everything that originates within the local network? I trust (as others are saying that this update fixed the issue for them) this isn't a schoolboy error of not realising that my LAN is, a little unusually, on 192.168.2 .× ? I ask this because the issue remains with both my Windows 7 & Windows 10 machines. The two machines have little common history so it's rather odd that both should appear to suffer from the same malaise.

The commonalities between the two machines are i) the network itself and ii) both developed the current issue with the arrival of component pack 1070 iii) both are cured by disabling Web Protection.

I trust you follow my argument here.

NB I have removed all the Google stuff from the Win7 machine. No change.

Link to post
Share on other sites

We have reversed the change and so far for the majority of users the updated beta has fixed the issue. Why it has not for you @Pluto is what we're attempting to try and track down.

For now then if you don't have time to help us help you track it down further then please disable the Web Protection module. You can use Malwarebytes Browser Guard and/or uBlock Origin content blocker to help shore up the Web Protection module until an update that works for you is available.

Thank you

 

Link to post
Share on other sites

So logically, the approach should be to examine the distinctions between component packs 1061 and 1070 as the former was absolutely fine.

If this were my mission I would have me run the diagnostic with each component pack in turn, changing nothing else in between. That strategy would probably reveal the issue.

Link to post
Share on other sites

As said the change was already reversed. If its not working for you and you won't allow me to help you diagnose why it's not working I don't know how else to assist you @Pluto

Please try using our MBST tool and uninstall all Malwarebytes software and reboot. Do not reinstall when prompted by the program and then see if normal operation has returned for you as it has for everyone else and let us know.

Thank you

 

Link to post
Share on other sites

OK, a quick bash in the morning (it's 1.30am here). Exactly what you would like me to do with the support tool? Happy to try uninstall/reinstall MB etc. but not messing around with stuff that considerably pre-dates this issue which might compromise the stability of the systems.

Link to post
Share on other sites

Uninstalled as asked via MBST. Interestingly, the tool did not offer to re-install. All well when MB not present, NAS detected correctly within a few seconds of clicking "Network".

Reinstalled MB manually, allowed latest updates, no change from status quo ante. Web Protection inhibits detection of NAS device.

Incidentally, something that might be deluding some folks here into thinking it's working, when it's not… in my case, when NAS is detected (having disabled Web Protection) that detection remains valid for a few minutes after Web Protection is resumed, even when pressing "refresh"! So those who believe that this issue is fixed, it might be useful to see if your NAS is still accessible after, say, 10 minutes of Web Protection remaining active.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

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.