unbcl.dll
Unmanaged BCL file version info
Library on Windows 3 known copies with hashes
Is it the real unbcl.dll?
Installed in
C:\Windows\system32\migwiz\C:\Windows\system32\oobe\C:\Windows\SysWOW64\migwiz\Signed byMicrosoft Windows
ProductMicrosoft Windows Operating System, Microsoft Corporation
DescriptionUnmanaged BCL
3 known copies
10.0.19041.450 (WinBuild.160101.0800) · C:\Windows\SysWOW64\migwiz\unbcl.dll · signed by Microsoft Windows
3b4bab09ba7c40d3a97bd4ff7d42cdcddf9dc827e9da8d9e5b4fe49c95bcfa0f10.0.19041.450 (WinBuild.160101.0800) · C:\Windows\system32\oobe\unbcl.dll · signed by Microsoft Windows
3c74fa8e35a6e3c9e78868d8ee333ad038cf65de86583dc823886bf039ef528710.0.19041.450 (WinBuild.160101.0800) · C:\Windows\system32\migwiz\unbcl.dll · signed by Microsoft Windows
854b885cff8691a3e9e7495e8c7a1c5973aa044f4f931e6ab315dc139198e2c7From 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.