exts.dll
Debugger Extensions file version info
Library on Windows 4 known copies with hashes
Is it the real exts.dll?
C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\winxp\C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\winxp\C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winxp\4 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\winxp\exts.dll · signed by Microsoft Windows Kits Publisher
6fe0cb3e796de9237b3cc39313049d583c746002bbd072234a947ad3b9ffc6e910.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\winxp\exts.dll · signed by Microsoft Windows Kits Publisher
a089488828e1ab174553fb9589dc422922e6d949afdc37db2cf667686f8c6cc010.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\winxp\exts.dll · signed by Microsoft Corporation
b0acdc5d090c21421752604bfb958fc12c4faafd483b758262ffc727397e341610.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winxp\exts.dll · signed by Microsoft Corporation
fa832c02b9a0a357d19ccb458347c6d1be3ff6b86b765605960a310505ee80a4From 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.