autofmt.exe
Auto File System Format Utility file version info
Program on Windows 16 known copies with hashes Command autofmt
Is it the real autofmt.exe?
C:\Windows\system32\C:\Windows\SysWOW64\16 known copies
10.0.19041.662 (WinBuild.160101.0800) · C:\Windows\SysWOW64\autofmt.exe · signed by Microsoft Windows
06263e020a00ac0ab567c949e0e3b99270a1ab9a819a721ba8eb616d7b852aa210.0.19041.662 (WinBuild.160101.0800) · C:\Windows\system32\autofmt.exe · signed by Microsoft Windows
561576e824768797d8b484edc365d232e2f6532d22d748fc2bfe04e85635e6f610.0.19041.1266 (WinBuild.160101.0800) · C:\Windows\SysWOW64\autofmt.exe · signed by Microsoft Windows
77cfa37c20e31db458b1212957fa10ba238588f85bfaf40bcbe8358f55c4989e10.0.19041.1023 (WinBuild.160101.0800) · C:\Windows\system32\autofmt.exe · signed by Microsoft Windows
4ad9e718008a7eb006a3659ec9fae8838860db6ac805e447f72d5f238143d35e10.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\autofmt.exe · signed by Microsoft Windows
279c7e6ec8f21a6f8a18e8a448e5523d5a37790937e43edf86743d25884494b610.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\autofmt.exe · signed by Microsoft Windows
ddda05b812afdf53f7d9c76400ee7a8024c94c89ef67a55d96b868823945422710.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\autofmt.exe · signed by Microsoft Windows
c9d39f03badcd9e52ef9af034c94f582af1d99df399fe08b8d19911befa5712010.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\autofmt.exe · signed by Microsoft Windows
d1cda8ccff47cc8c16301e52dff2ec4939a426a7d73dfcae47726ade48774a8210.0.17763.1490 (WinBuild.160101.0800) · C:\Windows\system32\autofmt.exe · signed by Microsoft Windows
428a3b0abe59983dff07b302c2527f5dd0161f96b8534ba64ab230afd2b114ab10.0.17763.1490 (WinBuild.160101.0800) · C:\Windows\SysWOW64\autofmt.exe · signed by Microsoft Windows
a27f730f1313d5a5759a6a8353af042766f0050154dd53389b3f316e1e9732a710.0.17763.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\autofmt.exe · signed by Microsoft Windows
4591abc010c00a0c9ad881627e2a2748a15d0f768906ae574244dd8e7106bf9410.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\autofmt.exe · signed by Microsoft Windows
c03082dcce81fa7a4b4fe30d71f45c8f2f2d64bf207eb38505bc158936fe99a510.0.14393.1532 (rs1_release_d.170711-1840) · C:\Windows\SysWOW64\autofmt.exe · signed by Microsoft Windows
58e3d25b9c8fb5ff95a1794f75952d2e816f80294d8c717b9f394dfc9eb5996a10.0.14393.1532 (rs1_release_d.170711-1840) · C:\Windows\system32\autofmt.exe · signed by Microsoft Windows
8e17300288e2844d0dd1b0b0c1b2d1f31c3016eda1922f88bb423f44368b946a6.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\system32\autofmt.exe · not signed
3da1eaca001e72e677491e73ae9333478af48492269d7caf069ed339b97182576.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\SysWOW64\autofmt.exe · not signed
8bf9e95427e6ef301e6c1c39097f97f1b50ee4c7d4bcb36781b4174c68f7a444From 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.