GridinSoft Threat Intelligence

Microsoft.WindowsAPICodePack.dll file report

Under review File reputation report
MD5 0d661949ebc172dfb3c3b98566bdf0fe
Latest seen 2024-11-02 23:05:59 (2 years ago)
First seen 2017-11-15 16:02:32 (8 years ago)
Size 96 KB
Publisher Microsoft

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-11-15 16:02:32 (8 years ago); latest analysis 2024-11-02 23:05:59 (2 years ago).

Publisher context

Company metadata: Microsoft. Product metadata: Microsoft Windows API Code Pack for .NET Framework.

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. Use the hash and metadata below to verify the exact file identity.
  2. Review publisher, signature, paths, and PE details for inconsistencies.
  3. Run a local scan if the file appears unexpectedly or starts with Windows.

Microsoft.WindowsAPICodePack.dll is a Windows file recorded in the ThreatInfo database. It is associated with Microsoft Windows API Code Pack for .NET Framework. The reported company name is Microsoft. The current detection status is Undefined, based on the latest analysis from 2024-11-02 23:05:59 (2 years ago).

ThreatInfo does not have a final classification for this file yet. Use the technical details below to compare the hash, size, signature, and observed locations with the copy found on your device.

Product Name: Microsoft Windows API Code Pack for .NET Framework
Company Name: Microsoft
MD5: 0d661949ebc172dfb3c3b98566bdf0fe
Size: 96 KB
First Published: 2017-11-15 16:02:32 (8 years ago)
Latest Published: 2024-11-02 23:05:59 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2024-11-02 23:05:59 (2 years ago)
%programfiles%\soundbox2014
%programfiles%\soundbox2014\imagecreator
%programfiles%
%localappdata%
%programfiles%\ashampoo

ThreatInfo has observed Microsoft.WindowsAPICodePack.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 75.6%
Windows 7 24.4%

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

Microsoft.WindowsAPICodePack.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 0x0001955e
Image base 0x10000000

.NET Info:

MVID: 2b780013-043a-4c06-a901-e00dbb3135dd
Typelib ID: ac9740bc-3035-43ee-9a68-1dde36ab1f5e

PE Sections:

Sections 3
Raw data 97792

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

.text 95744 bytes · 97.9% of section data
MD5 981ba5ffc3199a3f54814f44fe51bce3
.rsrc 1536 bytes · 1.6% of section data
MD5 586280f8f195d2c37713c62e5bc48eac
.reloc 512 bytes · 0.5% of section data
MD5 062881b9fb201fb633aa3faff071bd37

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 file is still under review

ThreatInfo has not assigned a final verdict yet. Compare the file hash, location, signature, and publisher before trusting the file on a production system.

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 0d661949ebc172dfb3c3b98566bdf0fe.
  • 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.