Did you just find a download or a file on your computer that has been digitally signed by Microsoft Windows Hardware Compatibility Publisher? If that's the case, please read on.
You'll typically notice Microsoft Windows Hardware Compatibility Publisher when clicking to run the file. The publisher name is then displayed as the "Verified publisher" in the UAC dialog as the screenshot shows:
You can view additional details from the Microsoft Windows Hardware Compatibility Publisher certificate with the following procedure:
Here is a screenshot of a file signed by Microsoft Windows Hardware Compatibility Publisher:
As you can see in the screenshot above, Windows states that "This digital signature is OK". This means that the file has been published by Microsoft Windows Hardware Compatibility Publisher and that the file has not been tampered with.
If you click the View Certificate button shown in the screenshot above, you can examine all the details of the certificate, such as when it was issued, who issued the certificate, how long it is valid, etc. You can also examine the address for Microsoft Windows Hardware Compatibility Publisher, such as the street name, city and country.
Microsoft Windows Hardware Compatibility PCA, Microsoft Windows Hardware Compatibility, Microsoft Windows Third Party Component CA 2014 and Microsoft Windows Third Party Component CA 2012 has issued the Microsoft Windows Hardware Compatibility Publisher certificates. You can also see the details of the issuer by clicking the View Certificate button shown in the screengrab above.
The following are the Microsoft Windows Hardware Compatibility Publisher files I have gathered, thanks to the FreeFixer users.
The FreeFixer tool treats files from Microsoft Windows Hardware Compatibility Publisher as safe, which means that the Microsoft Windows Hardware Compatibility Publisher files will appear with a green background and that there is no removal checkbox for the file. However, as you can see in the scan results below, a few of the anti-virus scanners detects the Microsoft Windows Hardware Compatibility Publisher file(s). I'm pretty sure those detections are false positives and that the files are safe. It's unlikely that Microsoft Windows Hardware Compatibility Publisher would ship a malware file.
Here's the detection names for the Microsoft Windows Hardware Compatibility Publisher files. I have grouped the detection names by each scanner engine. Thanks to VirusTotal for the scan results.
As mentioned above, I think these detections are false positives since it is very unlikely that Microsoft Windows Hardware Compatibility Publisher would ship a malware file.
Scanner | Detection Names |
---|---|
APEX | Malicious |
AegisLab | Troj.W32.Gen.m2M2, AdWare.W32.BrainInst, W32.Virut |
Agnitum | Trojan.Inject!lsJh8B2mO2g |
Antiy-AVL | Trojan/Win32.Tgenic, Trojan/Win32.Menti, Worm/Win32.Otwycal, Trojan/Win32.SGeneric, Trojan[:HEUR]/Win32.Unknown, Worm/Win32.Otwycal.gen, Worm/Win32.Klez.gen, Worm/Win32.WhiteIce.gen, Backdoor/Win32.Bifrose.gen, Trojan/Win32.Agent |
Avira | WORM/Conficker.Z.32 |
Baidu | Win32.Trojan.WisdomEyes.16070401.9500.9504, Win32.Trojan.WisdomEyes.16070401.9500.9669 |
Baidu-International | Hacktool.Win64.NetFilter.A |
Bkav | HW32.CDB.9be0, HW32.CDB.8117, W32.Clodaed.Trojan.4969, W32.HfsAutoA.Ffc1, HW32.CDB.619b, W32.Clodbae.Trojan.b5af, HW32.CDB.3205, HW32.Laneul.jsmg, W32.Clodea0.Trojan.d774, HW32.CDB.Bbe4, HW32.Laneul.hykq, W32.HfsAutoA.B76C, HW32.Packed.ECC9, HW32.CDB.F961, HW32.Laneul.juio, HW32.Nonim.xuak, W32.Clod861.Trojan.2fb2, HW64.packed.9E7E, HW32.Nonim.wqsy, W32.HfsReno.8a5c, HW64.packed.A908 |
ByteHero | Trojan.Exception.gen.101, Trojan-Dropper.win32.Agent.a |
CMC | Heur.Win32.Obfuscated.1!O |
ClamAV | Win.Trojan.7507983, Win.Trojan.Agent-564482, Win.Trojan.Rootkit-6573, Win.Trojan.6536826, Win.Trojan.Agent-343335, Win.Trojan.Agent-230945, PUA.Win32.Packer.Msvcpp-1, Win.Trojan.Agent-576433, Win.Trojan.Slugin-357 |
Comodo | UnclassifiedMalware |
Cybereason | malicious.dda988 |
Cylance | Unsafe |
DrWeb | DLOADER.Trojan, BackDoor.Siggen.41201 |
Emsisoft | Gen:Trojan.Heur.LP.ay4@aCPH@bli (B), Trojan.Generic.KDV.530539 (B), Win32.Worm.AutoIt.Z (B), Android.Adware.Kuguo.A (B), JS:Trojan.Clicker.NBP (B), Gen:Variant.Graftor.127006 (B), Android.Trojan.FakeInst.DA (B) |
Invincea | virus.win32.sality.at |
Jiangmin | Trojan/Reconyc.fid, Trojan.Cosmu.i, Win32/Virut.bn, I-Worm/Polip.cl, Trojan.Generic.fnrd, Trojan.Kryplod.iy |
Kingsoft | Win32.Troj.Agent2.cq.(kcloud) |
McAfee-GW-Edition | Heuristic.BehavesLike.Win32.Suspicious-DTR.K, Heuristic.LooksLike.Win32.Suspicious.I, Heuristic.LooksLike.Win32.Suspicious.B, Heuristic.LooksLike.Win32.Suspicious.E, BehavesLike.Win32.PWSZbot.dh |
NANO-Antivirus | Trojan.Win32.Cholera.ctdfbm, Trojan.Win32.Inject.cslkna, Trojan.Win32.Agent.derwez, Trojan.Win32.Warezov.daszf, Trojan.Win32.Graftor.cticpm, Trojan.Win32.IframeExec.cxhgiu, Trojan.Win32.Heuristic210.dfvtzs |
Prevx | Medium Risk Malware |
Rising | PE:Trojan.Barys!6.50A, PE:Malware.XPACK-HIE/Heur!1.9C48, PE:Adware.OneStep!6.161D, PE:Trojan.Symmi!6.804, PE:Malware.Viking!6.17A9, PE:Backdoor.Agent!6.13D4, PE:Worm.Chir!6.171E, PE:Rootkit.Agent!6.2332 |
Symantec | Suspicious.Insight |
TheHacker | Backdoor/IRCNite.arz, Trojan/VB.qdc, Trojan/Menti.mxvf, Trojan/Agent.sjtk, Trojan/VBKrypt.efmc, Backdoor/IRCNite.cei, Trojan/Menti.myha, Trojan/AutoRun.AntiAV.t, Backdoor/Bredavi.eks, Trojan/Small.nav |
Trapmine | malicious.moderate.ml.score |
TrendMicro-HouseCall | TROJ_GEN.R0CBH0AA314, TROJ_GEN.F47V0201, Suspicious_GEN.F47V0818 |
VBA32 | Trojan.Menti, Trojan.Agent, Trojan.Agent.ashi, Virus.Win32.Virut.X6 |
ViRobot | Trojan.Win32.A.ShipUp.1404928, Trojan.Win32.A.NSAnti.102400.X, Trojan.Win32.A.Menti.90112.EH |
Webwasher-Gateway | BlockReason.0 |
Yandex | Riskware.Agent!, Trojan.MulDrop!kaXunN8DGBI |
Zillya | Trojan.Monder.Win32.49829, Trojan.Menti.Win32.35788 |
eGambit | Unsafe.AI_Score_91%, Unsafe.AI_Score_97% |
eSafe | Win32.TrojanHorse, Win32.Trojan |
nProtect | Trojan/W32.Agent.405504.XW, Trojan/W32.Agent.544768.L, Trojan-Downloader/W32.Cekar.61512 |
The detection percentage is based on that I have gathered 212340 scan reports for the Microsoft Windows Hardware Compatibility Publisher files. 157 of these scan results came up with some sort of detection. You can review the full details of the scan results by examining the files listed above.
The analysis has been done on certificates with the following serial numbers:
el controlador parece es el del problema, suministrado por ESET version 10.13.360 2.5" sata external case. lo que solicito es por cual otro controlador o driver se puede utilizar, en los archivos figura como windows explorer. Los puerto del pc funcionan correctamente y la memoria no tiene problemas en otros computadores
ENRIQUE CALAD A
ecalad@hotmail.com
# 17 May 2020, 0:47
tito writes