PrintBrmEngine.exe
PrintBrmEngine EXE file version info
Program on Windows 10 known copies with hashes
Is it the real PrintBrmEngine.exe?
PrintBrmEng.exe in the file’s header: a renamed copy still carries itC:\Windows\system32\spool\tools\10 known copies
10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\spool\tools\PrintBrmEngine.exe · signed by Microsoft Windows
bf28d4128d12c471c7886ae14c03742454a7009b1cb05c5a02ae3a6a5269313a10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\spool\tools\PrintBrmEngine.exe · signed by Microsoft Windows
5ac64aadefb3b1a084f2ad4d827b86da7e13b2c7648b4454a0f6cbe3a6f42e4b10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\spool\tools\PrintBrmEngine.exe · signed by Microsoft Windows
62df4ace3a28c1210faf34cbdac9b09c099109257a7ecbba8d07be944baa20b310.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\spool\tools\PrintBrmEngine.exe · signed by Microsoft Windows
921e361678f4dd5f5fe59195b30a0133fe549f73ec608b4cd64e00d5530f6a0910.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\spool\tools\PrintBrmEngine.exe · signed by Microsoft Windows
c3247f0751ffa3167e89b2da622aa46bbe5605a5d930511b8209303778499a9b10.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\spool\tools\PrintBrmEngine.exe · signed by Microsoft Windows
3a95a49cd2135f4bc26ea6842055cc97a25b088075dc896130823655b37a01b310.0.17763.1 (WinBuild.160101.0800) · C:\windows\system32\spool\tools\PrintBrmEngine.exe · signed by Microsoft Windows
4fb79fa73d202c11543a5385729232d1dd84ee89af28d2e4a1142259f6518c6910.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\spool\tools\PrintBrmEngine.exe · signed by Microsoft Windows
b45e80d042bd7f45ffce382f7c299a22ee480e066cd40f971c40d96cd78c85eb10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\spool\tools\PrintBrmEngine.exe · signed by Microsoft Windows
d74a27da850f130b31a1dc498ef66228dd30d43365e11b6f8b2472e396dddd7310.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\spool\tools\PrintBrmEngine.exe · signed by Microsoft Windows
3d378c05229a0a2a51f952c0eb3bdbff34ab62f0d6399d7cc2f73e091df64c97From the file’s version info and the copies recorded by xCyclopedia (MIT). A copy in another folder, signed by someone else or with another hash is not necessarily malicious, but it is worth a closer look. In Ceplin, "<sha256>".whatis() says which known copy a hash is.