GridinSoft Threat Intelligence

msvcp140.dll file report

Clean record File reputation report
MD5 d396985225d85caa7d743d67c7da6316
Latest seen 2025-05-26 23:01:25 (a year ago)
First seen 2017-09-16 05:17:48 (8 years ago)
Size 626 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-09-16 05:17:48 (8 years ago); latest analysis 2025-05-26 23:01:25 (a year ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Microsoft® Visual Studio® 2017.

Digital signature

Signed by Microsoft Corporation. The signature is reported as valid, but signed files can still be bundled or abused.

Observed locations

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

  1. Confirm the hash and publisher match the expected software.
  2. Review the observed locations and signature information below.
  3. Rescan if the file was downloaded from an unknown source or appears in an unusual path.

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-05-26 23:01:25 (a year 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.

Product Name: Microsoft® Visual Studio® 2017
Company Name: Microsoft Corporation
MD5: d396985225d85caa7d743d67c7da6316
Size: 626 KB
First Published: 2017-09-16 05:17:48 (8 years ago)
Latest Published: 2025-05-26 23:01:25 (a year ago)
Status: Clean (on last analysis)
Analysis Date: 2025-05-26 23:01:25 (a year ago)
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.

%programfiles%\dllescort\sysscan\windows\system32
%programfiles%\antivirus\setup\crt\data\avg.vc140.crt
%programfiles%\jetstrmedia
%programfiles%
%sysdrive%\desktop-t86glr8\backup set 2018-03-07 010008\backup files 2018-03-07 010008\backup files 7.zip\c\program files
%sysdrive%\willy-pc\backup set 2018-03-04 191736\backup files 2018-03-11 211437\backup files 3.zip\c\users\willy\appdata\local
%programfiles%\avast software\avast\setup\crt\data\avast.vc140.crt
%sysdrive%\_genie timeline(1)\0\c\windows\winsxs\amd64_avg.vc140.crt_f92d94485545da78_14.0.25325.0_none_6bbcfeb7d72790b2
%sysdrive%\zaza-pc\backup set 2018-03-19 142120\backup files 2018-03-19 142120\backup files 3.zip\c\program files\avast software\avast\setup\crt\data\avast.vc140.crt
%sysdrive%\enterprise1701\backup set 2018-02-26 120549\backup files 2018-02-26 120549\backup files 20.zip\c\program files

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.

Windows 10 64.8%
Windows 7 31.1%
Windows 8.1 3.0%
Windows Server 2003 0.7%
Windows XP 0.4%

The most common operating system signal for msvcp140.dll is Windows 10 with 64.8% 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.

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.

Format pe
Architecture 64-bit
Subsystem Windows CUI
Entry point 0x0004bcb0
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 624640

Section layout highlights raw-size concentration, repeated names, packer markers, and hashes that can be compared across related samples.

.text 330240 bytes · 52.9% of section data
MD5 6615d45d328b7d42ca893021b3dc0fa2
.rdata 265216 bytes · 42.5% of section data
MD5 8a17da4e6cd3566e2089d114d073a003
.data 7168 bytes · 1.1% of section data
MD5 b826ef2a5c382f7798eeb33876649d6f
.pdata 17408 bytes · 2.8% of section data
MD5 89aef66726cc3a1c3d55ffa5958ad524
.didat 512 bytes · 0.1% of section data
Uncommon name
MD5 e1f9e0d059a3851905586e8ded917f34
.rsrc 1024 bytes · 0.2% of section data
MD5 cd6a86deaf4a119edac519275798b9e9
.reloc 3072 bytes · 0.5% of section data
MD5 c429688d9963d5dec279dcff2994471b

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.

Scan with GridinSoft Anti-Malware Use a local scan if the file origin or behavior is unclear. Check this hash on VirusTotal

Recommended next steps

  • Compare the local file MD5 with d396985225d85caa7d743d67c7da6316.
  • Check the file path, publisher, and signature against the details in this report.
  • Run a GridinSoft scan if the source, path, or behavior looks unusual.