msdia140.dll file report

MD5 ddc85eff55a22dc0992cbf5a1ea82aaf
Latest seen 2026-03-18 23:00:52 (2 months ago)
First seen 2018-04-12 20:11:07 (8 years ago)
Size 1 MB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-04-12 20:11:07 (8 years ago); latest analysis 2026-03-18 23:00:52 (2 months ago).

Publisher context

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

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.

msdia140.dll 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 2026-03-18 23:00:52 (2 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: ddc85eff55a22dc0992cbf5a1ea82aaf
Size: 1 MB
First Published: 2018-04-12 20:11:07 (8 years ago)
Latest Published: 2026-03-18 23:00:52 (2 months ago)
Status: Clean (on last analysis)
Analysis Date: 2026-03-18 23:00:52 (2 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.

%programfiles%\bytefence
%sysdrive%\archivos de programa\bytefence
%programfiles%\bytefence
%programfiles%\bytefence
%programfiles%\bytefence
%programfiles%\bytefence
%programfiles%\bytefence
%programfiles%\bytefence
%programfiles%\bytefence
%programfiles%\bytefence

ThreatInfo has observed msdia140.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.

10.6%
9.1%
8.5%
8.4%
6.1%
5.8%
5.7%
3.9%
2.5%
2.5%
2.3%
2.3%
2.1%
2.0%
1.7%
1.6%
1.6%
1.5%
1.4%
1.4%
1.3%
1.2%
1.0%
0.9%
0.8%
0.8%
0.8%
0.7%
0.7%
0.7%
0.7%
0.5%
0.5%
0.4%
0.4%
0.4%
0.4%
0.4%
0.4%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.3%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%
0.1%

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

Windows 10 62.7%
Windows 7 29.4%
Windows 8.1 6.2%
Windows 8 0.8%
Windows XP 0.7%
Windows Vista 0.2%

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

msdia140.dll is identified as pe for 32 systems. The subsystem is Windows GUI. PE header values are useful for triage, especially when they do not match the expected publisher, product, or release timeline.

Subsystem: Windows GUI
PE Type: pe
OS Bitness: 32
Image Base: 0x10000000
Entry Address: 0x0008eebf

PE Sections:

Name Size of data MD5
.text 942592 c674a725b038e3c8f90060ad2365fc86
.data 10240 f9024d92b11b3fbfb9d1a4ece9acac64
.idata 3072 bb46c7cd93323d238730ec288d3b75d8
.tls 512 1f354d76203061bfdd5a53dae48d5435
.rsrc 64512 673a5495c5643693fd8db381993d3bbc
.reloc 43520 8a802052e3bcf9a58bccbc9dd4207e61

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.

More information: