Malwarebytes Offline Download - Build Number Discrepancy

[Steven J. Marty]

According to the posting here, the current version of Malwarebytes is v4.1.2.73.  I am downloading the offline installer from here.  The file that is downloaded is named mb4-setup-consumer-4.1.2.173-1.0.979-1.0.26665.exe instead of mb4-setup-consumer-4.1.2.73-1.0.979-1.0.26665.exe.  Additionally, when viewing the properties of the downloaded file, the file version is reported as v4.1.1.173 instead of v4.1.2.73.

Has the offline installer been compromised in some way or are the build/version number discrepancies just simple mistakes in the versioning?

[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

[exile360]

Greetings,

Thank you for bringing this to our attention.  It is possible that they are using different numbering to track file/installer versions compared to the actual product/build version, or of course it could be a discrepancy as you suggest.

I will make a note of this for the Product team while we await a response from a staff member.

Thanks

[Porthos]

20 minutes ago, Steven J. Marty said:

the file version is reported as v4.1.1.173 instead of v4.1.2.73.

The file version of the installer has nothing to do with the program version when you look at the properties.

[Steven J. Marty]

2 minutes ago, Porthos said:

The file version of the installer has nothing to do with the program version when you look at the properties.

There are multiple discrepancies...the file name, the file version, and the program version...none of them match one another.  I keep offline copies of all installers and these version numbers have matched for as long as I have used Malwarebytes software.

[LiquidTension]

Hello,

This is currently expected. The "4.1.2.173" in the file name is a combination of the Malwarebytes service and MBSetup version numbers.

4.1.2 = Malwarebytes service Major.Minor.Patch semver
173 = MBSetup build number

We are reviewing whether a change to this file naming format is needed.

[Maurice Naggar]

Hi Steven.

Compromised ....no, I dont expect so.   The file name pattern is consistent with the one  that came before,  { including where the dots in the filename are).    

LiquidTension is spot on.      😉