GridinSoft Threat Intelligence
msvcp140.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2017-07-29 08:06:49 (8 years ago); latest analysis 2025-11-02 23:01:12 (6 months ago).
Company metadata: Microsoft Corporation. Product metadata: Microsoft® Visual Studio® 2017.
Signed by Microsoft Corporation. The signature is reported as valid, but signed files can still be bundled or abused.
ThreatInfo has seen this file in user or system paths listed below. Unexpected locations increase the need for local verification.
Recommended action
What to do next
- Confirm the hash and publisher match the expected software.
- Review the observed locations and signature information below.
- Rescan if the file was downloaded from an unknown source or appears in an unusual path.
File context
msvcp140.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2017. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2025-11-02 23:01:12 (6 months ago).
This record is currently marked as clean, but file reputation can depend on the exact path, hash, and source. Compare the MD5 and publisher data below with the file on your system.
File Details
| Product Name: | Microsoft® Visual Studio® 2017 |
| Company Name: | Microsoft Corporation |
| MD5: | 0a252601b942f683c2c60beacb4f1a72 |
| Size: | 427 KB |
| First Published: | 2017-07-29 08:06:49 (8 years ago) |
| Latest Published: | 2025-11-02 23:01:12 (6 months ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2025-11-02 23:01:12 (6 months ago) |
Overview
| Signed By: | Microsoft Corporation |
| Status: | Valid |
The signature on msvcp140.dll is reported as valid. A valid signature helps confirm publisher identity, but it does not automatically make the file safe if the installer was bundled, abused, or downloaded from an untrusted source.
Common Places:
| %programfiles%\simplitec\simplitec power suite |
| %programfiles%\simplitec |
| %appdata%\tencent\tim\autemp\18122697\7clklr0f\oldfiles |
| %programfiles%\forwardchess\jre |
| %programfiles%\infovotantes\java |
| %programfiles%\nero |
| %programfiles%\zona\jre |
| %programfiles%\bootmod3\jre |
| %programfiles%\software\note5\note5_5.1.4.36469\main |
ThreatInfo has observed msvcp140.dll in the locations listed above. Files found in temporary folders, user profile folders, startup locations, or unusual application directories should be reviewed more carefully than files installed under a known program directory.
Geographic signal
Observed country distribution
ThreatInfo has seen msvcp140.dll across 48 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is United States with 21.0% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.
OS Version:
The most common operating system signal for msvcp140.dll is Windows 10 with 74.4% of observed hits. If your system differs from the common profile, check whether the file was introduced by a specific installer, archive, or removable device.
Analysis
msvcp140.dll is identified as pe for 32-bit systems. The subsystem is Windows CUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.
PE Sections:
Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.
eb5339ba68177d07a607fda421eef34d
339c43fc9b3806a395cda9cbc62772d4
5180b499cd0ad215495a098788c04c81
f71a62e6742323e594d137888e6f8675
7d73f8b4db4fc746e3dcf8ce48cbc8a3
e2c4cc076968c6fcf610125a157b2f2b
PE section names and hashes can reveal packing, injected resources, or unusual build artifacts. Sections with uncommon names, very large raw data, or hashes that differ from a trusted copy deserve additional review.
Report conclusion
This hash is currently recorded as clean
Use the MD5, publisher, signature, and observed paths in this report to verify that the file on your device is the same copy described here.