GridinSoft Threat Intelligence
msvcp140.dll file report
Why it matters
Evidence available for this file
Latest status is clean for this hash.
First seen 2018-03-21 06:13:29 (8 years ago); latest analysis 2025-09-18 23:00:38 (8 months 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 2025-09-18 23:00:38 (8 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: | 4835a9b8749970d0ad04f22a546042af |
| Size: | 446 KB |
| First Published: | 2018-03-21 06:13:29 (8 years ago) |
| Latest Published: | 2025-09-18 23:00:38 (8 months ago) |
| Status: | Clean (on last analysis) | |
| Analysis Date: | 2025-09-18 23:00:38 (8 months 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:
| %appdata%\knctr |
| %localappdata%\appset\appset.soft.core |
| %appdata%\tencent\qq\autemp\3073859600\7k3ss431\oldfiles |
| %appdata%\tencent\qq\autemp\3073859600\7dxupa03\oldfiles |
| %appdata%\tencent\tim\autemp\2632904689\7pkg6p1e\oldfiles |
| %programfiles%\zona\jre |
| %sysdrive%\window\window\config |
| %commonappdata%\bromium\vsentry\4.1.6.3263\stage1\stage1image0005\swapdata-3c361943-c05b-474d-ab60-39abecec01e0 |
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 25 countries. Use this signal to compare local evidence with where the sample is most often reported.
The strongest geographic signal for this file is Russian Federation with 68.3% 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 72.0% 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.
ad8eb5592064f8c8c73e76a8c30184fd
a4a9eb8a095f718e5f92ed3ce1bed233
1540970e69b02fd25d0890e5a2d99dfc
04e026fdb0092e6c29ded3b8cd0ceddd
f3418489839f8b2a25b702aec072082c
2bf0e99c8422703232a61bee56d21a5e
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.