File Identifier

File Identifier is a free utility that may be installed with File Viewer Lite. It is designed to help you recognize unknown files on your Windows computer. When you attempt to open an unknown file, the File Identifier dialog box will appear. Click OK to view information about the file directly from FileInfo.com.

Additional information

Architecture

x64, x86

Software vendor

Sharpened Productions

Vendor website

https://windowsfileviewer.com/

File Identifier also allows you to look up information about any Windows file using the contextual menu option. Simply right-click a file and select “Show file information.”

File Identifier | Application Packaging

Source => https://windowsfileviewer.com/file_identifier

Note: We can help make ‘File Identifier’ installer enterprise deployment ready.

osd365 | Global application packaging services

Application packaging plays a vital role in efficiently managing software deployments within organizations.  

Application packaging minimizes cost and improves System efficiency during and after deployment of the software to the System.

osd365 application packaging services provides the following advantages.

  • Custom osd365 uninstall codes : This helps organizations identify and uninstall software installed outside of the purview of the organizations software management systems.
  • Desktop shortcuts : If not directed otherwise, desktop shortcuts will not be installed.
  • Silent : If not directed otherwise, all our installation processes are silent.

Note : Some software vendors do not make their software available to the public domain. In such cases, you have to download and provide the software and the appropriate licenses.

Request for quote

Please login to submit a request.

DCOM hardening issue.

This application fails to authenticate with WMI on the SCCM server because Microsoft has not yet hardened DCOM on their Windows Preinstallation Environment. We are working on a different approach, but it will only be released during the first quarter of 2024. But until that time, the only workaround will be to uninstall the update corresponding to KB5004442.