GridinSoft Threat Intelligence
msvcp140.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2019-10-26 05:11:06 (6 years ago); latest analysis 2026-04-22 23:01:04 (a month ago).
Company metadata: Microsoft Corporation. Product metadata: Microsoft® Visual Studio® 2017.
Signed by Microsoft Corporation. ThreatInfo marks this publisher as trusted for this record.
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 2026-04-22 23:01:04 (a month 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: | c1b066f9e3e2f3a6785161a8c7e0346a |
| Size: | 613 KB |
| First Published: | 2019-10-26 05:11:06 (6 years ago) |
| Latest Published: | 2026-04-22 23:01:04 (a month ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2026-04-22 23:01:04 (a month ago) |
Overview
| Signed By: | Microsoft Corporation |
| Status: | Trusted Publisher |
ThreatInfo marks this publisher as trusted for this record, but the file hash and source should still match the expected software distribution.
Common Places:
| %programfiles% |
| %programfiles%\reviversoft |
| %commonappdata%\bromium\vsentry\4.1.9.2740\stage1\stage1image0005\swapdata-54ee731a-8898-4715-9dce-7378a635560b |
| %commonappdata%\bromium\vsentry\4.1.9.2740\stage1\stage1image0001\swapdata-a9cc26a2-1e91-4341-95be-fefeef9ac694 |
| %appdata%\tencent\qqlive\playersdk64 |
| %programfiles%\psqlodbc\1302 |
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 23.1% 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 85.7% 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 64-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.
37728a4bfbde24973b10bc0be74b8f1a
9ce53ef067deeb780e29a5393fca8360
c5506f6f29dbc1f3164e8021022ffdb5
d351b31aa3d37a044e618cd26e188a89
038fd15383d0bacf950450b6d86beac6
4a265838c1ad22716b3bc538bc296cb0
f5cd99c4d115da441546126edf6df190
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.