Jump to content
andylee321

Windows Server 2003 failing to run scans

Recommended Posts

Hi,

We have a Windows Server 2003 that will not scan via the Cloud Console / from the server end.

I have completed the following

- Reboot the server

- Uninstalled MWB / Reinstall MWB

Any other ideas of what I can do? I've also attached some logs from FRST/mb-check-3.1.9.1001

mb-check-results.zip

Scan via console result.PNG

Scan via server result.PNG

Share this post


Link to post
Share on other sites

This has been resolved by running Malwarebytes Breach Remediation. Their were some instances of bad files/ransomware on this server.

Thanks.

Share this post


Link to post
Share on other sites

Thank you for providing the logs and letting us know what fixed it. I will look over the logs and see if we find figure out why the scans were failing initially. 

Share this post


Link to post
Share on other sites

I am experiencing this same error when I attempt to run a Scan with the Endpoint Protection Cloud product, but this is using Server 2008.

After reading your other thread, andylee321, I was able to get the Server 2008 to register as a node in the Cloud Console (I had to install the KB update for TLS) but whether I trigger a Scan from the console, or manually on the system, it gives the same error above.  It gets to the "File Scanning" portion, then abruptly stops.

I was looking at the documentation to run the Malwarebytes Breach Remediation Tool, like you mentioned, hoping to resolve this issue.  But in the MBBR Guide that I have here, dated 30 October 2018, it states the tool only supports OS versions Server 2008 R2 64bit and above.  My system is Server 2008 32bit... The tool that I have here is MBBRv2, dated 11/5/2018, file version 2.7.2.1655.

How did you get the MBBR tool to run successfully on Server 2003?  Did you use an older version of this tool?  Is that version still available for pre-2008R2 systems, such as mine?

Thanks in advance.

Share this post


Link to post
Share on other sites
On 2/11/2019 at 11:47 AM, ktechno1 said:

I am experiencing this same error when I attempt to run a Scan with the Endpoint Protection Cloud product, but this is using Server 2008.

After reading your other thread, andylee321, I was able to get the Server 2008 to register as a node in the Cloud Console (I had to install the KB update for TLS) but whether I trigger a Scan from the console, or manually on the system, it gives the same error above.  It gets to the "File Scanning" portion, then abruptly stops.

I was looking at the documentation to run the Malwarebytes Breach Remediation Tool, like you mentioned, hoping to resolve this issue.  But in the MBBR Guide that I have here, dated 30 October 2018, it states the tool only supports OS versions Server 2008 R2 64bit and above.  My system is Server 2008 32bit... The tool that I have here is MBBRv2, dated 11/5/2018, file version 2.7.2.1655.

How did you get the MBBR tool to run successfully on Server 2003?  Did you use an older version of this tool?  Is that version still available for pre-2008R2 systems, such as mine?

Thanks in advance.

Bump-- Anyone?  I need to get this protection running on this Server system...

Share this post


Link to post
Share on other sites

Hi @ktechno1, unfortunately Server 2008 and 2008 R2 32-bit are no longer supported by the MB3 engine. Server 2008 32-bit can use the last MBBR 2 version, the one you have listed, 2.7.2.1655.

 

From the Cloud Admin Guide - https://www.malwarebytes.com/pdf/guides/MBQSG.pdf
Windows Server 2008 R2 SP1‡§, 2008 SP2 ‡§, 2008§
‡ Microsoft patch KB4019276 must also be installed and enabled
§ As of July 2018, development has halted for Endpoint Clients using this operating system

 

Excerpts from MBBR's Admin Guides.

MBBR 2.7.2.1655 Operating Systems:
o Windows 10 (32/64-bit)
o Windows 8.1 (32/64-bit)
o Windows 8 (32/64-bit)
o Windows 7 (32/64-bit)
o Windows Vista (32/64-bit)
o Windows XP (Service Pack 2 or later, 32-bit only)
o Windows Server 2012/2012 R2 (64-bit only)
o Windows Small Business Server 2011 (64-bit only)
o Windows Server 2008/2008 R2 (32/64-bit)
o Windows Server 2003 (32-bit only)

MBBR 3.6.1.243 Operating Systems:
o Windows 10 (32/64-bit)
o Windows 8.1 (32/64-bit)
o Windows 8 (32/64-bit)
o Windows 7 (32/64-bit) (Service Pack 1 or later)
o Windows Server 2012/2012 R2 (64-bit only)
o Windows Small Business Server 2011 (64-bit only)
o Windows Server 2008 R2 (64 bit)

Edited by djacobson

Share this post


Link to post
Share on other sites

Alright, thank you sir.  I hadn't tried to run MBBR file yet.

Apparently the Admin Guide that came with my Toolset shows for v3, so the supported OS matches your bottom list, but the actual file in my Toolset is the v2.7, so I'll give it a shot.

By the way, do you have a link for the Admin Guide for the older v2?

Share this post


Link to post
Share on other sites

I don't have a web link to it like the main ones, I'm sorry ktechno1. But it will be in the zip folder if you pull a new download of MBBR from your Manage Endpoints page in the cloud portal. Those excerpts were from the guides of the MBBR zips I just downloaded to write that post. Also, because your MBBR 2 zip had the wrong guide in it, I went ahead and refreshed your cloud installers to make sure it grabs the same ones I had this morning.

Share this post


Link to post
Share on other sites

Just to update: the Malwarebytes Breach Remediation utility version 2.7.x was ran on this x86 Server, the Endpoint Agent was uninstalled and reinstalled, and then the Scan would complete successfully.

Thanks for the help!

Share this post


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.

×
×
  • 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.