kdbgctrl.exe
Windows kernel debugger configuration utility file version info
Program on Windows 4 known copies with hashes
Is it the real kdbgctrl.exe?
C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\4 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\kdbgctrl.exe · signed by Microsoft Windows Kits Publisher
bbc4cdde93875ba3e498a82d1a915d2ac4d6fbe5aa6f18d2877d64b01dba191d10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\kdbgctrl.exe · signed by Microsoft Windows Kits Publisher
d0567180649d535ceb06a460bb71b70c9081d18206f3d849b316777279ba0b4410.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\kdbgctrl.exe · signed by Microsoft Corporation
f885af4010a30ac4ec2987938c58ab736621f313d432bd7f8f17b527d2e7a7cb10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\kdbgctrl.exe · signed by Microsoft Corporation
fd5c21d94f7342e5f4080b9424fec378df62d827579dfdb534b38fdc8c8acfbeFrom 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.