ext.dll
Debugger Extensions file version info
Library on Windows 4 known copies with hashes
Is it the real ext.dll?
C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\winext\C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\winext\C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winext\4 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\winext\ext.dll · signed by Microsoft Windows Kits Publisher
36100c3d66a56da08308fe5d86df52e78e06d4cbd798c7345b8169acdac20fe410.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\winext\ext.dll · signed by Microsoft Windows Kits Publisher
4a33ee81a8f66f659c521eda39c704605a51420f1a88f990a897e87cbae9c9f810.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\winext\ext.dll · signed by Microsoft Corporation
7de47591b76c4ec584d1b478ef507f0c98fb0673a4c0bdd050756c94da3ab04810.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\winext\ext.dll · signed by Microsoft Corporation
afd41f42e448f15c033686b0ad830a60e9fbc91b94bc9d60a3647670fc06acf8From 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.