GridinSoft Threat Intelligence

msvcp140.dll file report

Clean record File reputation report
MD5 c1b066f9e3e2f3a6785161a8c7e0346a
Latest seen 2026-04-22 23:01:04 (a month ago)
First seen 2019-10-26 05:11:06 (6 years ago)
Size 613 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2019-10-26 05:11:06 (6 years ago); latest analysis 2026-04-22 23:01:04 (a month ago).

Publisher context

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

Digital signature

Signed by Microsoft Corporation. ThreatInfo marks this publisher as trusted for this record.

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 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.

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)
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.

%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.

Windows 10 85.7%
Windows 7 10.3%
Windows 8.1 3.4%
Windows 8 0.5%

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.

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 0x0004d420
Image base 0x0000000180000000

PE Sections:

Sections 7
Raw data 610304

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

.text 331776 bytes · 54.4% of section data
MD5 37728a4bfbde24973b10bc0be74b8f1a
.rdata 249856 bytes · 40.9% of section data
MD5 9ce53ef067deeb780e29a5393fca8360
.data 7168 bytes · 1.2% of section data
MD5 c5506f6f29dbc1f3164e8021022ffdb5
.pdata 16896 bytes · 2.8% of section data
MD5 d351b31aa3d37a044e618cd26e188a89
.didat 512 bytes · 0.1% of section data
Uncommon name
MD5 038fd15383d0bacf950450b6d86beac6
.rsrc 1024 bytes · 0.2% of section data
MD5 4a265838c1ad22716b3bc538bc296cb0
.reloc 3072 bytes · 0.5% of section data
MD5 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.

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 c1b066f9e3e2f3a6785161a8c7e0346a.
  • 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.