Jump to content

jskinnerjr

Members
  • Posts

    3
  • Joined

  • Last visited

Reputation

0 Neutral

About jskinnerjr

  • Birthday 07/22/1984

Profile Information

  • Location
    Vermont
  1. Ok, so the solution that I found was to ensure that your registry .Default user has the correct proxy settings. Instead of using whatever user is logged in to update, MalwareBytes uses the proxy settings found in the .DEFAULT system user. For me, the Administrator account on the system was NOT the .DEFAULT account. Here are the 2 keys that I changed to default settings: [HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings] "ProxyEnable" [HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections] "DefaultConnectionSettings" That remedied the situation for me. Seems this is a very rare occurrence.
  2. Hello! I have deployed via the Management Console successfully to all clients. 5 out of approx. 85 clients will not update correctly. They start to update, the progress bar completes and goes away, but no files download, and it says it has been updated successfully, however the signature information is incorrect for the most recent update. If I push a client installation manually, the full push install will update the database. If I push a message for the client to update, it says it was successful but still does not change the date. The other 80 clients all update correctly. I've done the MBAM-clean procedures that are listed elsewhere on the forums multiple times on one of the clients that are not updating correctly, and it has not resolved the issue. Does anyone else have a solution? Thank you in advance! John
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.