Jump to content

gmshedd

Members
  • Posts

    6
  • Joined

  • Last visited

Reputation

1 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Like many issues, it happened after an update--either of Windows or of MB. Everything has worked fine for a year, with consistent Windows and MB updates being applied, and then, bang, an update happens and a problem appears. At least that's my surmise. Problem has been solved. Thanks for your help.
  2. Sorry to double up here. One more thing: I'm not sure how or why MB wasn't registering with Windows Security Center on this particular PC. I have 5 seats of MB and this was the only one that wasn't registering--maybe because it's the only 32-bit system? Maybe Windows 32-bit acts differently, or the MB 32-bit acts differently.
  3. Ultimately, the fix seemed to be to change the MB security setting to "Always register MB in the Windows Security Center." Of course, this allowed MB to appear in Windows Security settings as the Virus & Threat Protection, as you would expect, but it also allowed MB to connect to the license server (when selecting "Account" in MB settings), which I didn't expect. I think, if MB isn't registered with Windows Security Center, then Windows Defender interferes with MB attempts to install updates and contact the license sever.
  4. I succeeded in getting the latest version (4.3.0) of MB to install on my 32-bit Windows 10 laptop by turning off Defender, but MB is still not showing under Virus & threat protection after rebooting, and I don't see any option to make MB the virus protector under Manage Providers in Windows Security. This information applies to a 32-bit Windows 10 system. My 64-bit systems don't have this problem; they show MB as the active virus protection. However, neither bit version can connect to the license server when I click on Account in the MB Settings.
  5. Thanks for the quick work on the 7Z false + OctoberRaven and Atribune. I'll work on the License server/failed install through support if it persists after I reinstall MB.
  6. Today, for the first time, MB 4.2.1.89 identified my 7-Zip executable and its install file, 7z1900 to be Trojan.SmokeLoader. They've been installed on the laptop for years. No word about it on here or anywhere else on the internet. Scanned as ok with Windows Defender. Quarantined them for the moment. BTW, noticed that MB has a 7Z.dll in its program directory. Two other odd things: MB is "Unable to contact license server", and repeatedly fails to install a new update, even after I explicitly added the license for the affected laptop to my account by logging in on the same laptop (testmy.net shows download speed of 40 Mb and upload at 6 Mb). I downloaded a new install for MB and will try installing fresh and then rescanning the 7Z files.
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.