msvcr100.dll file report

MD5 2b92a88e329f4845d31941967a3baa90
Latest seen 2025-11-02 23:01:13 (6 months ago)
First seen 2017-05-21 06:07:41 (8 years ago)
Size 750 KB

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2017-05-21 06:07:41 (8 years ago); latest analysis 2025-11-02 23:01:13 (6 months ago).

Publisher context

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

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.

msvcr100.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft® Visual Studio® 2010. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2025-11-02 23:01:13 (6 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® 2010
Company Name: Microsoft Corporation
MD5: 2b92a88e329f4845d31941967a3baa90
Size: 750 KB
First Published: 2017-05-21 06:07:41 (8 years ago)
Latest Published: 2025-11-02 23:01:13 (6 months ago)
Status: Clean (on last analysis)
Analysis Date: 2025-11-02 23:01:13 (6 months ago)
Signed By: Microsoft Corporation
Status: Valid

The signature on msvcr100.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.

%programfiles%\drivertoolkit\download\6f6d3821790b78d16f9fd38a032eeaf9\ledvisualizer
%programfiles%\simprocess\jre\bin\plugin2
%programfiles%\simprocess\jre\bin
%programfiles%\drivertoolkit\download\7a89a90533c2b8a6e7d9bf8568d7c2af\ledvisualizer
%programfiles%\drivertoolkit\download\d95e13932a6e947cebc9177ab5652bc5\ledvisualizer
%programfiles%\zaxar
%programfiles%\drivertuner\download\2dfcee6b123f3a946849010afec25068\ledvisualizer
%programfiles%
%programfiles%\drivertoolkit\download\d95e13932a6e947cebc9177ab5652bc5
%programfiles%\online.io\jre

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

69.4%
20.3%
1.2%
1.2%
1.0%
0.8%
0.8%
0.8%
0.6%
0.4%
0.4%
0.4%
0.4%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%
0.2%

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

Windows 10 61.1%
Windows 7 25.5%
Windows 8.1 11.7%
Windows XP 1.2%
Windows Vista 0.4%

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

msvcr100.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: 0x78aa0000
Entry Address: 0x00010844

PE Sections:

Name Size of data MD5
.text 720896 0e0badc20919c817cf732558b3a27c92
.data 19968 cb50c2986936ab3b953fa3b4f1302452
.rsrc 1024 64f5bc9d2bf390ef50ca3a77e2fe3da3
.reloc 19968 5ce932f023b081eb6714d311becb1b85

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: