bridgeunattend.exe
Bridge Unattend Utility file version info
Program on Windows 6 known copies with hashes
Is it the real bridgeunattend.exe?
C:\Windows\system32\6 known copies
10.0.22000.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\bridgeunattend.exe · signed by Microsoft Windows
ee6cd4ca4e86f9a91583a239144de2ab56d40d4ff87e48a902e2a49950a0485d10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\bridgeunattend.exe · signed by Microsoft Windows
0dab54a90bf52eb64f8eb50d94298f2c55d04682369c93107315ad91a3c6d64210.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\bridgeunattend.exe · signed by Microsoft Windows
b32acfabbbcb47b847d6e580faf1872af9f901a8331be251695fc1022ae3adfc10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\bridgeunattend.exe · signed by Microsoft Windows
7f7fae31cf7b8b04112f746c27b51bb37f3dccef08e5459ab65cbe0f44a146b510.0.14393.0 (rs1_release.160715-1616) · C:\Windows\system32\bridgeunattend.exe · signed by Microsoft Windows
33ac0bc2aac1fb4a70804618460dc701d7d84ecff343ffc20dd0ce873566081f6.3.9600.17415 (winblue_r4.141028-1500) · C:\windows\system32\bridgeunattend.exe · not signed
1fa6532e9048c88faab04e5792db3ad5e29a3c714a43f54c8ee35e3cef7ccff0From 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.