srcsrv.dll
Microsoft Source Server file version info
Library on Windows 8 known copies with hashes
Is it the real srcsrv.dll?
C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\srcsrv\C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\8 known copies
10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\srcsrv\srcsrv.dll · signed by Microsoft Corporation
008140a6e748f41d1609fd30edbe6ac80af5769eeaeeef352dac73ddcc2095c110.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\srcsrv\srcsrv.dll · signed by Microsoft Corporation
2a1e28aa182a0317e2d607d2838dd8ef1d9f4de7cbd09e6730ac8eaf162b136810.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm64\srcsrv.dll · signed by Microsoft Corporation
595486c598160bc52ba4d08087814aa509269b1d5bc9faf718d84dff61f1555810.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\srcsrv.dll · signed by Microsoft Corporation
5acb479b2eec488e637f5ce45d42b444565a301695f5a548a2e16170b53f5ab510.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\srcsrv.dll · signed by Microsoft Corporation
691ea1c3c3a3ca065fb18c015013bcc7c2b2855e9ba377683c89237d70f2a46810.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x64\srcsrv\srcsrv.dll · signed by Microsoft Corporation
7d9c8717cd8d6d98438b50d0dfc1481775ac15dbefed94bb5c3d2e9c1674896c10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\x86\srcsrv\srcsrv.dll · signed by Microsoft Corporation
84504ab2727aff0bcc35f7e97bdf57c8a8285115f656e53ff13d75fc23ba9bbb10.0.19041.1 (WinBuild.160101.0800) · C:\Program Files (x86)\Windows Kits\10\Debuggers\arm\srcsrv.dll · signed by Microsoft Corporation
c71681f15b31bf4bf72cd0f1c11e1da7d4446aed95f5787f4dfd39dcea3d9c08From 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.