GridinSoft Threat Intelligence

msvcp140.dll file report

Clean record File reputation report
MD5 109f0f02fd37c84bfc7508d4227d7ed5
Latest seen 2025-12-03 23:03:31 (5 months ago)
First seen 2017-09-16 05:17:58 (8 years ago)
Size 429 KB
Publisher Microsoft Corporation
Product Microsoft® Visual Studio® 2017
Signed by Microsoft Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-09-16 05:17:58 (8 years ago); latest analysis 2025-12-03 23:03:31 (5 months 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.

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-12-03 23:03:31 (5 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: 109f0f02fd37c84bfc7508d4227d7ed5
Size: 429 KB
First Published: 2017-09-16 05:17:58 (8 years ago)
Latest Published: 2025-12-03 23:03:31 (5 months ago)
Status: Clean (on last analysis)
Analysis Date: 2025-12-03 23:03:31 (5 months ago)

Overview

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.

Common Places:

%programfiles%\dllescort\sysscan\windows\syswow64
%programfiles%\antivirus\setup\crt\data\avg.vc140.crt
%programfiles%
%commonappdata%\windows\flauncher
%windir%\winsxs
%commonappdata%
%sysdrive%\riot games\league of legends\rads\projects\league_client\releases\0.0.0.141
%sysdrive%\riot games\league of legends\rads\projects\league_client\releases\installer
%sysdrive%\riot games\league of legends\rads\projects\league_client\releases\0.0.0.149
%sysdrive%\riot games\league of legends\rads\projects\league_client\releases\0.0.0.117

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 90 countries. Use this signal to compare local evidence with where the sample is most often reported.

Top country Indonesia
Share 15.2%
Low High activity

The strongest geographic signal for this file is Indonesia with 15.2% of observed hits. Geographic distribution can help identify targeted campaigns, regional software bundles, or where a file is most commonly reported.

OS Version:

Windows 10 69.4%
Windows 7 24.6%
Windows 8.1 4.1%
Windows 8 1.0%
Windows Vista 0.4%
Windows Server 2012 R2 0.3%
Windows Server 2016 0.1%
Windows Server 2008 R2 0.1%

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

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

PE Sections:

Sections 6
Raw data 422912

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

.text 394240 bytes · 93.2% of section data
MD5 e0935df7c04a99ffbc1dfc5980102fdf
.data 6144 bytes · 1.5% of section data
MD5 281e8876846d182f4bfa2e4c06745c7b
.idata 5632 bytes · 1.3% of section data
MD5 d03e3bee64775dc6ccae52dd5f1042b9
.didat 512 bytes · 0.1% of section data
Uncommon name
MD5 d80d61e56c34dd4049786471b6e9b317
.rsrc 1024 bytes · 0.2% of section data
MD5 de87f4cee957dabc7940ce1753d6af5c
.reloc 15360 bytes · 3.6% of section data
MD5 9f0011e16bf3800fe0f2ea33ac5cbc69

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 109f0f02fd37c84bfc7508d4227d7ed5.
  • 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.