GridinSoft Threat Intelligence

msvcp140_1.dll file report

Clean record File reputation report
MD5 cb8e791faf8a711f9863f759f37fd316
Latest seen 2026-02-04 23:01:14 (3 months ago)
First seen 2019-06-12 08:27:31 (6 years ago)
Size 27 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2019-06-12 08:27:31 (6 years ago); latest analysis 2026-02-04 23:01:14 (3 months 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_1.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-02-04 23:01:14 (3 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.

Product Name: Microsoft® Visual Studio® 2017
Company Name: Microsoft Corporation
MD5: cb8e791faf8a711f9863f759f37fd316
Size: 27 KB
First Published: 2019-06-12 08:27:31 (6 years ago)
Latest Published: 2026-02-04 23:01:14 (3 months ago)
Status: Clean (on last analysis)
Analysis Date: 2026-02-04 23:01:14 (3 months 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.

%appdata%\tencent\pallas
%profile%
%localappdata%

ThreatInfo has observed msvcp140_1.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 90.3%
Windows 7 7.2%
Windows 8.1 2.2%
Windows 8 0.3%

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

Format pe
Architecture 32-bit
Subsystem Windows CUI
Entry point 0x00001dd0
Image base 0x10000000

PE Sections:

Sections 5
Raw data 11264

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

.text 7168 bytes · 63.6% of section data
MD5 26ea61b05159b66bfc386bfac3e191bc
.data 512 bytes · 4.5% of section data
MD5 1689dc4c13c1bc6573537d2f42b32ae2
.idata 1536 bytes · 13.6% of section data
MD5 fb4bfff388eb0eb6c70a7d6080076f49
.rsrc 1024 bytes · 9.1% of section data
MD5 39cd96e0db8f79343130c226bcfb5deb
.reloc 1024 bytes · 9.1% of section data
MD5 6e62bc80dcff5d40a82bd519b35b0c01

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