What is osmclienticon.exe?
osmclienticon.exe is part of Microsoft Office 2013 and developed by Microsoft Corporation according to the osmclienticon.exe version information.
osmclienticon.exe's description is "Microsoft Office 2013 component"
osmclienticon.exe is digitally signed by Microsoft Corporation.
osmclienticon.exe is usually located in the 'C:\Windows\Installer\{90150000-0011-0000-1000-0000000FF1CE}\' folder.
None of the anti-virus scanners at VirusTotal reports anything malicious about osmclienticon.exe.
If you have additional information about the file, please share it with the FreeFixer users by posting a comment at the bottom of this page.
Vendor and version information [?]
The following is the available information on osmclienticon.exe:
| Property | Value |
|---|---|
| Product name | Microsoft Office 2013 |
| Company name | Microsoft Corporation |
| File description | Microsoft Office 2013 component |
| Internal name | icons.exe |
| Original filename | icons.exe |
| Product version | 15.0.4420.1017 |
| File version | 15.0.4420.1017 |
Here's a screenshot of the file properties when displayed by Windows Explorer:
| Product name | Microsoft Office 2013 |
| Company name | Microsoft Corporation |
| File description | Microsoft Office 2013 component |
| Internal name | icons.exe |
| Original filename | icons.exe |
| Product version | 15.0.4420.1017 |
| File version | 15.0.4420.1017 |
Digital signatures [?]
osmclienticon.exe has a valid digital signature.
| Property | Value |
|---|---|
| Signer name | Microsoft Corporation |
| Certificate issuer name | Microsoft Code Signing PCA |
| Certificate serial number | 3300000088590e3c511fe26a67000100000088 |
VirusTotal report
None of the 45 anti-virus programs at VirusTotal detected the osmclienticon.exe file.
Hashes [?]
| Property | Value |
|---|---|
| MD5 | e26004202f3085719cb1d91331316920 |
| SHA256 | ba560047ceee209e31a72d7adf62f852c071a9635849c935faa79cdf74bd2fef |
Error Messages
These are some of the error messages that can appear related to osmclienticon.exe:
osmclienticon.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
osmclienticon.exe - Application Error. The instruction at "0xXXXXXXXX" referenced memory at "0xXXXXXXXX". The memory could not be "read/written". Click on OK to terminate the program.
Microsoft Office 2013 component has stopped working.
End Program - osmclienticon.exe. This program is not responding.
osmclienticon.exe is not a valid Win32 application.
osmclienticon.exe - Application Error. The application failed to initialize properly (0xXXXXXXXX). Click OK to terminate the application.
What will you do with the file?
To help other users, please let us know what you will do with the file:
What did other users do?
The poll result listed below shows what users chose to do with the file. 0% have voted for removal. Based on votes from 1 user.
| Votes | |||
|---|---|---|---|
| Keep | 100 % | 1 | |
| Remove | 0 % | 0 |
Malware or legitimate?
If you feel that you need more information to determine if your should keep this file or remove it, please read this guide.
And now some shameless self promotion ;)
Hi, my name is Roger Karlsson. I've been running this website since 2006. I want to let you know about the FreeFixer program. FreeFixer is a freeware tool that analyzes your system and let you manually identify unwanted programs. Once you've identified some malware files, FreeFixer is pretty good at removing them. You can download FreeFixer here. It runs on Windows 2000/XP/2003/2008/2016/2019/Vista/7/8/8.1/10. Supports both 32- and 64-bit Windows.
If you have questions, feedback on FreeFixer or the freefixer.com website, need help analyzing FreeFixer's scan result or just want to say hello, please contact me. You can find my email address at the contact page.
Comments
Please share with the other users what you think about this file. What does this file do? Is it legitimate or something that your computer is better without? Do you know how it was installed on your system? Did you install it yourself or did it come bundled with some other software? Is it running smoothly or do you get some error message? Any information that will help to document this file is welcome. Thank you for your contributions.
I'm reading all new comments so don't hesitate to post a question about the file. If I don't have the answer perhaps another user can help you.
No comments posted yet.