GridinSoft Threat Intelligence

msvcp140.dll.quarantined file report

Clean record File reputation report
MD5 1d8c79f293ca86e8857149fb4efe4452
Latest seen 2025-12-22 23:02:08 (5 months ago)
First seen 2017-05-21 04:03:36 (9 years ago)
Size 429 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 04:03:36 (9 years ago); latest analysis 2025-12-22 23:02:08 (5 months ago).

Publisher context

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

Digital signature

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

Aliases

This hash has appeared under multiple file names, which can happen with repackaging, bundling, or deliberate renaming.

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.quarantined is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2015. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2025-12-22 23:02:08 (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.

Product Name: Microsoft® Visual Studio® 2015
Company Name: Microsoft Corporation
MD5: 1d8c79f293ca86e8857149fb4efe4452
Size: 429 KB
First Published: 2017-05-21 04:03:36 (9 years ago)
Latest Published: 2025-12-22 23:02:08 (5 months ago)
Status: Clean (on last analysis)
Analysis Date: 2025-12-22 23:02:08 (5 months ago)
Signed By: Microsoft Corporation
Status: Valid

The signature on msvcp140.dll.quarantined 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%\firefox
%programfiles%\58cc3bb3_jumpeasy\sdirec
%sysdrive%\archivos de programa\firefox
%localappdata%
%programfiles%\5911cbfd_jumpeasy\sdirec
%appdata%\audiohdriver
%programfiles%\58d3c64b_jumpeasy\sdirec
%programfiles%\5901eb50_jumpeasy\sdirec
%appdata%\baidu\baiduyunguanjia
%appdata%\knctr\app

ThreatInfo has observed msvcp140.dll.quarantined 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.

msvcp140.dll msvcp140.dll.dll file.dll vcruntime140.dll msvcp140.dll.old msvcp140____0.dll msvcp140.dll.quarantined

This hash has been seen with multiple file names. Alternate names can appear when software is updated, copied between folders, packed by an installer, or deliberately renamed to avoid recognition. Compare the exact MD5 above before assuming two names refer to the same file.

Windows 10 55.8%
Windows 7 32.5%
Windows 8.1 9.0%
Windows 8 1.5%
Windows XP 1.0%
Windows Server 2012 R2 0.1%

The most common operating system signal for msvcp140.dll.quarantined is Windows 10 with 55.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.quarantined 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 0x0003ab20
Image base 0x10000000

PE Sections:

Sections 6
Raw data 422400

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

.text 393728 bytes · 93.2% of section data
MD5 c3da67ef2b50c62cb202693028cd3ffd
.data 6144 bytes · 1.5% of section data
MD5 e9d0a8ad18a640e6eb9d3b70d4de5777
.idata 5632 bytes · 1.3% of section data
MD5 1267395feeff6e4532b60d230cdc81db
.didat 512 bytes · 0.1% of section data
Uncommon name
MD5 21d4e34e4fb35ccaf095ebdc1cc6fc16
.rsrc 1024 bytes · 0.2% of section data
MD5 5ea0b9ffec8c26809cf345a6cfa6c141
.reloc 15360 bytes · 3.6% of section data
MD5 ef499f9c35126e67e8c95accaeb94489

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 1d8c79f293ca86e8857149fb4efe4452.
  • 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.