Version table

[Doc898913]

Hi Support

I was wondering if you have a page that presents the latest versions of your products that I can reference. Alternatively, the file paths to the Malware antivirus engine and also the malware endpoint version. 

We run a product called Galactic Scan and it detects Malwarebytes anti-virus as being out of date. When I log into the portal. It shows the latest version as being the same.

What I believe to be the issue is as follows

The Galactic scan is comparing the antivirus version engine to the endpoint engine and this is why it is showing as out of date. 

So, I have Galactic Scan support asking for a why to confirm the version is the latest version and they can change their scanner to look at the right files

[Malwarebytes]

***This is an automated reply***

Hi,

Thanks for posting in the Malwarebytes for Windows Help forum.

If you are having technical issues with our Windows product, please do the following:

Malwarebytes Support Tool - Advanced Options

This feature is designed for the following reasons:

• For use when you are on the forums and need to provide logs for assistance
• For use when you don't need or want to create a ticket with Malwarebytes
• For use when you want to perform local troubleshooting on your own

How to use the Advanced Options:

Spoiler

1. Download Malwarebytes Support Tool
2. Double-click mb-support-X.X.X.XXXX.exe to run the program
   • You may be prompted by User Account Control (UAC) to allow changes to be made to your computer. Click Yes to consent.
3. Place a checkmark next to Accept License Agreement and click Next
4. Navigate to the Advanced tab
5. The Advanced menu page contains four categories:
   • Gather Logs: Collects troubleshooting information from the computer. As part of this process, Farbar Recovery Scan Tool (FRST) is run to perform a complete diagnosis. The information is saved to a file on the Desktop named mbst-grab-results.zip and can be added as an email attachment or uploaded to a forum post to assist with troubleshooting the issue at hand.
   • Clean: Performs an automated uninstallation of all Malwarebytes products installed to the computer and prompts to install the latest version of Malwarebytes for Windows afterwards. The Premium license key is backed up and reinstated. All user configurations and other data are removed. This process requires a reboot.
   •  Repair System: Includes various system-related repairs in case a Windows service is not functioning correctly that Malwarebytes for Windows is dependent on. It is not recommended to use any Repair System options unless instructed by a Malwarebytes Support agent.
   • Anonymously help the community by providing usage and threat statistics: Unchecking this option will prevent Malwarebytes Support Tool from sending anonymous telemetry data on usage of the program.
6. To provide logs for review click the Gather Logs button
7. Upon completion, click OK
8. A file named mbst-grab-results.zip will be saved to your Desktop
9. Please attach the file in your next reply.
10. To uninstall all Malwarebytes Products, click the Clean button.
11. Click the Yes button to proceed. 
12. Save all your work and click OK when you are ready to reboot.
13. After the reboot, you will have the option to re-install the latest version of Malwarebytes for Windows.
14. Select Yes to install Malwarebytes.
15. Malwarebytes for Windows will open once the installation completes successfully.

Screenshots:

Spoiler

 

 

 

 

Spoiler

 

 

 

 

If you are having licensing issues, please do the following: 

Spoiler

For any of these issues:

• Renewals
• Refunds (including double billing)
• Cancellations
• Update Billing Info
• Multiple Transactions
• Consumer Purchases
• Transaction Receipt

Please contact our support team at https://support.malwarebytes.com/hc/en-us/requests/new to get help

If you need help looking up your license details, please head here: Find my premium license key

 

 

Thanks in advance for your patience.

-The Malwarebytes Forum Team

[lmacri]

Hi Doc898913:

The "official" release notes are posted at  https://support.malwarebytes.com/hc/en-us/sections/23038336826899-Version-History   but it often takes several days for that version history to be updated after a new version of Malwarebytes is released.  Employee H4V0C has pinned a topic called Malwarebytes 5 at the top of this forum board that is updated shortly after a new product (scan engine) or component package is released, and many users subscribe to that topic so they are notified by email as soon as an update is released.  Note: H4V0C will likely start a new topic when Malwarebytes v5.2.x is eventually released and you will have to subscribe to that new topic to continue receiving mail notifications.

Unfortunately, for the past two years the product version number has not matched the version number of the Malwarebytes installer, which makes it very difficult, if not impossible, for Galactic Scan or any software updater app to correctly detect when an update is released for Malwarebytes.  See P1W's 23-Jun-2023 What's the conventional version number of the mb4_offline installer?  for more information.  My 25-Mar-2024 post <here> in P1W's topic describes the difficulties I now have using winget commands or software updater apps like QuickInstaller and UCheck to correctly detect the latest available version of Malwarebytes.
------------
Dell Inspiron 15 5584 * 64-bit Win 10 Pro v22H2 build 19045.4651 * Firefox v128.0.0 * Microsoft Defender v4.18.24060.7-1.1.24060.5 * Malwarebytes Premium v5.1.6.117-1.0.1280 * Macrium Reflect Free v8.0.7783 * QuickInstaller (Preview) 0.3.8859.20616 * UCheck Free Portable v5.5.0.2

Edited July 23 by AdvancedSetup
Updated URL to correct location

[AdvancedSetup]

@Doc898913

You can use the following PowerShell 5.1 code to enumerate the version information.

NOTE: This is not a supported or company approved method of determining the current version number.
Use at your own risk. Any and all invalid or wrong data obtained is at the risk of the person using such methods.

 

# Define the path to the JSON file
$jsonFilePath = "C:\ProgramData\Malwarebytes\MBAMService\config\UpdateControllerConfig.json"

# Define the path to the log file on the user's desktop
$logFilePath = [System.IO.Path]::Combine([System.Environment]::GetFolderPath('Desktop'), "Malwarebytes_Version.txt")

# Read the JSON file as plain text. The JSON file appears to have invalid data in it to read as valid JSON format
try {
    $jsonContent = Get-Content -Path $jsonFilePath -Raw
    Write-Output "Raw JSON content read successfully."
} catch {
    Write-Error "Failed to read the JSON file: $_"
    exit 1
}

# Extract version information using regex
try {
    $dbclsPkgVersion = [regex]::Match($jsonContent, '"dbcls_pkg_version":\s*"([^"]+)"').Groups[1].Value
    $controllersVersion = [regex]::Match($jsonContent, '"controllers_version":\s*"([^"]+)"').Groups[1].Value
    $installerVersion = [regex]::Match($jsonContent, '"installer_version":\s*"([^"]+)"').Groups[1].Value

    # Prepare log entries in the desired order
    $logEntries = @(
        "Malwarebytes version: $installerVersion"
        "Update package version: $dbclsPkgVersion"
        "Component package version: $controllersVersion"
    )

    # Write log entries to the log file
    $logEntries | Out-File -FilePath $logFilePath -Encoding utf8

    # Confirm the log file creation
    Write-Output "Log file created at: $logFilePath"
} catch {
    Write-Error "Failed to extract version information from the JSON content: $_"
    exit 1
}

 

Sample output:

Malwarebytes version: 5.1.6
Update package version: 1.0.87102
Component package version: 1.0.1280

 

 

[Doc898913]

Thank you will do some testing and see if this will do what we need

[Ried]

Thanks for all your help fellas. Our Business HelpDesk will be continuing with this user as he is referring specifically to our EndPoint Agent product.