autoconv.exe
Auto File System Conversion Utility file version info
Program on Windows 16 known copies with hashes Command autoconv
Is it the real autoconv.exe?
C:\Windows\system32\C:\Windows\SysWOW64\16 known copies
10.0.19041.662 (WinBuild.160101.0800) · C:\Windows\SysWOW64\autoconv.exe · signed by Microsoft Windows
86ee7446784d9afbe3b44ec20825027baa5d32a45d4efaf137c360a102bedc3910.0.19041.662 (WinBuild.160101.0800) · C:\Windows\system32\autoconv.exe · signed by Microsoft Windows
a3172d37531665f5528e5b6831cc00644694b95ce3ccedcb32f1f0997de2246510.0.19041.1266 (WinBuild.160101.0800) · C:\Windows\SysWOW64\autoconv.exe · signed by Microsoft Windows
9e03f82b733908ff583ec767f2f7ffbc705f01c5e451fa5b6e603ff1b6261f0c10.0.19041.1023 (WinBuild.160101.0800) · C:\Windows\system32\autoconv.exe · signed by Microsoft Windows
e6c20451167b160c70bd03f7fff6b40b20e69be567cddbcfc48a7aa7365fbaa110.0.19041.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\autoconv.exe · signed by Microsoft Windows
9dda6341087e07b7c50e3c1816b7076c2d7b2be7d281c231f99144fc144a11a410.0.19041.1 (WinBuild.160101.0800) · C:\Windows\system32\autoconv.exe · signed by Microsoft Windows
b903052e0d28c704bb0d7c1a36eced237369c7ae0418145d4bb65c63005cda2f10.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\system32\autoconv.exe · signed by Microsoft Windows
20f166d445e04b250a1b6a14b83381f4bc9e959e378213aaa7b73e4ff0248a7710.0.18362.1 (WinBuild.160101.0800) · C:\WINDOWS\SysWOW64\autoconv.exe · signed by Microsoft Windows
5e2e3ffa5e2c761c2459696d0404232be64944f338650a5701d6bce300c8bf9910.0.17763.1490 (WinBuild.160101.0800) · C:\Windows\system32\autoconv.exe · signed by Microsoft Windows
31cf1cd007394e0e6f8926666917659927008bbee9e6f4b218d4f359c215ebaa10.0.17763.1490 (WinBuild.160101.0800) · C:\Windows\SysWOW64\autoconv.exe · signed by Microsoft Windows
bfe7dc2ab8c610fba1339a86c7e3c0d8d574a82f17670c31c32c11558000c54e10.0.17763.1 (WinBuild.160101.0800) · C:\Windows\SysWOW64\autoconv.exe · signed by Microsoft Windows
3da90503c57c57c198904eab618ab5ed4942e8fa225643f4705328cdf4c69ec410.0.17763.1 (WinBuild.160101.0800) · C:\Windows\system32\autoconv.exe · signed by Microsoft Windows
d9c70d9db3512834dba65648edf305339d4fc3a023956e5df12ee54023251f3d10.0.14393.1532 (rs1_release_d.170711-1840) · C:\Windows\system32\autoconv.exe · signed by Microsoft Windows
3a2ed5ebd7d053c3328ecffa4fc7d8a9608329b21449ae901d18bcf5034d5de510.0.14393.1532 (rs1_release_d.170711-1840) · C:\Windows\SysWOW64\autoconv.exe · signed by Microsoft Windows
9aef49e3087cd8e5557affdfa0e92e1a58e78adc95d94579cbc91e40cee883566.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\system32\autoconv.exe · not signed
17a36d732a619e9d6df37aa8e322b41ded3cbea440dfc5b6f8b981d275d2f41b6.3.9600.16384 (winblue_rtm.130821-1623) · C:\windows\SysWOW64\autoconv.exe · not signed
50b933a5b3ec2c3cbf95efd1e1f5b4fe664b06f55eb2b7277b14ef8d07cd5820From 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.