What is the "bm.exe" ? Variant 892648

Our database contains 60 different files for filename bm.exe but this page contains information about single file with specific attributes. If you want to see general information about the bm.exe then visit General Information Page . You can also check most distributed file variants with name bm.exe. This file belongs to product HP Button Manager Application. This file has description HP Button Manager MFC Application. Agregate rating is 1(1) stars - based on 1 reviews.This is executable file. You can find it running in Task Manager as the process bm.exe.

bm.exe Process
Product:
HP Button Manager Application
Company:
(Empty Value)
Description:
HP Button Manager MFC Application
Version:
2.4.0.0
MD5:
cf9e4610e4081c968709ede0b523a070
SHA1:
64ca0fa250bce218ece0b3ca765283d4ca68614e
SHA256:
0526ee3f102aacd9c5e5bcb5044e1ccff8e2d6aa4dab69ba92d106e3dd9101e6
Size:
266240
Directory:
%PROGRAMFILES%\HP\Button Manager
Operating System:
Windows XP
Occurence:
Low oc0

System Explorer Community Antivirus Report

This file was checked and tolerated by following antivirus shields :
Antivirus NameLatest Toleration
Avira Antivirus2016-07-09 15:47:06
Norton Internet Security2016-04-26 18:33:41
AVG AntiVirus Free Edition2016-04-26 18:33:41
avast! Antivirus2014-04-24 02:15:12
Microsoft Security Essentials2013-05-01 10:17:54
Antivirus shields were enabled and have latest antivirus database.

Is the Process "bm.exe" Safe or Threat ?

Loading Graph
100% of reviewed files are marked as Threat .
Our final rating for this file is Threat. Final rating is based on file reviews, discovered date, users occurence and antivirus scan results.
67% of reviewed files with different MD5 located in different directory are marked as Safe .
33% of reviewed files with different MD5 located in different directory are marked as Threat .

User Reviews of the "bm.exe"

  • THREATrating from user Barry for file %PROGRAMFILES%\HP\Button Manager\BM.exe (Variant: 9032)

    Process caused repeated Security event id 577 entries which caused security log to fill quickly. Only discovered when disabling.