ProcID.exe is part of Intel(R) Processor Identification Utility and developed by Intel(R) Corporation according to the ProcID.exe version information.
ProcID.exe's description is "Intel(R) Processor Identification Utility"
ProcID.exe is digitally signed by Intel(R) Intel(R) Processor Identification Utility 2.
ProcID.exe is usually located in the 'C:\Program Files\Intel Corporation\Intel Processor Identification Utility\' folder.
None of the anti-virus scanners at VirusTotal reports anything malicious about ProcID.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.
The following is the available information on ProcID.exe:
| Property | Value |
|---|---|
| Product name | Intel(R) Processor Identification Utility |
| Company name | Intel(R) Corporation |
| File description | Intel(R) Processor Identification Utility |
| Internal name | Intel(R) Processor Identification Utility |
| Original filename | ProcID.exe |
| Legal copyright | Copyright(C) 2017 Intel(R) Corporation |
| Product version | 5.60 |
| File version | 5.60 |
Here's a screenshot of the file properties when displayed by Windows Explorer:
| Product name | Intel(R) Processor Identification Ut.. |
| Company name | Intel(R) Corporation |
| File description | Intel(R) Processor Identification Ut.. |
| Internal name | Intel(R) Processor Identification Ut.. |
| Original filename | ProcID.exe |
| Legal copyright | Copyright(C) 2017 Intel(R) Corporation |
| Product version | 5.60 |
| File version | 5.60 |
ProcID.exe has a valid digital signature.
| Property | Value |
|---|---|
| Signer name | Intel(R) Intel(R) Processor Identification Utility 2 |
| Certificate issuer name | Intel External Issuing CA 7B |
| Certificate serial number | 56000001a0eee88415d8a917860000000001a0 |
None of the 62 anti-virus programs at VirusTotal detected the ProcID.exe file.
| Property | Value |
|---|---|
| MD5 | 4e9a1bff4b14f6adbf7d360af9a010a6 |
| SHA256 | 8457ba21304b4899d51c117f797231d53cb8dfa3c34f8cecb79a554bbac439cb |
These are some of the error messages that can appear related to procid.exe:
procid.exe has encountered a problem and needs to close. We are sorry for the inconvenience.
procid.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.
Intel(R) Processor Identification Utility has stopped working.
End Program - procid.exe. This program is not responding.
procid.exe is not a valid Win32 application.
procid.exe - Application Error. The application failed to initialize properly (0xXXXXXXXX). Click OK to terminate the application.
To help other users, please let us know what you will do with ProcID.exe:
The poll result listed below shows what users chose to do with ProcID.exe. 0% have voted for removal. Based on votes from 6 users.
| Votes | |||
|---|---|---|---|
| Keep | 100 % | 6 | |
| Remove | 0 % | 0 |
If you feel that you need more information to determine if your should keep this file or remove it, please read this guide.
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.
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.