GridinSoft Threat Intelligence

DPInst64.exe file report

Clean record File reputation report
MD5 043693bf0f25d7fbbff014986b2aa6a2
Latest seen 2021-01-14 14:04:00 (5 years ago)
First seen 2018-05-10 10:12:12 (8 years ago)
Size 1022 KB
Signed by Intel Corporation

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2018-05-10 10:12:12 (8 years ago); latest analysis 2021-01-14 14:04:00 (5 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: Driver Package Installer (DPInst).

Digital signature

Signed by Intel 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.

DPInst64.exe is a Windows file recorded in the ThreatInfo database. It is associated with Driver Package Installer (DPInst). The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2021-01-14 14:04:00 (5 years 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: Driver Package Installer (DPInst)
Company Name: Microsoft Corporation
MD5: 043693bf0f25d7fbbff014986b2aa6a2
Size: 1022 KB
First Published: 2018-05-10 10:12:12 (8 years ago)
Latest Published: 2021-01-14 14:04:00 (5 years ago)
Status: Clean (on last analysis)
Analysis Date: 2021-01-14 14:04:00 (5 years ago)
Signed By: Intel 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%

ThreatInfo has observed DPInst64.exe 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 83.3%
Windows 7 16.7%

The most common operating system signal for DPInst64.exe is Windows 10 with 83.3% 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.

DPInst64.exe is identified as pe for 64-bit 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.

Format pe
Architecture 64-bit
Subsystem Windows GUI
Entry point 0x0005cba8
Image base 0x0000000100000000

PE Sections:

Sections 5
Raw data 1039360

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

.text 522752 bytes · 50.3% of section data
MD5 ae27ad8303f4cc33f8ec441de06c7c51
.data 2560 bytes · 0.2% of section data
MD5 8f85419e9c2896562538ec7cacf29f41
.pdata 28160 bytes · 2.7% of section data
MD5 b1373dc60e5c5ab762740c34b90fc12b
.rsrc 481792 bytes · 46.4% of section data
MD5 8f0ac76dee60ddf3f8186e5b0b7e8368
.reloc 4096 bytes · 0.4% of section data
MD5 dfe2cab536b3702cd7bc3316f20c6105

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 043693bf0f25d7fbbff014986b2aa6a2.
  • 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.