GridinSoft Threat Intelligence

bthenum{00001132-0000-1000-8000-00805f9b34fb}.exe file report

Clean record File reputation report
MD5 662964205a6ac3fa1476eb67787a847e
Latest seen 2026-02-06 23:01:49 (3 months ago)
First seen 2021-08-28 20:41:27 (4 years ago)
Size 98 MB
Signed by Dell Inc

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2021-08-28 20:41:27 (4 years ago); latest analysis 2026-02-06 23:01:49 (3 months ago).

Digital signature

Signed by Dell Inc. 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.

bthenum{00001132-0000-1000-8000-00805f9b34fb}.exe is a Windows file recorded in the ThreatInfo database. The current detection status is Clean, based on the latest analysis from 2026-02-06 23:01:49 (3 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.

MD5: 662964205a6ac3fa1476eb67787a847e
Size: 98 MB
First Published: 2021-08-28 20:41:27 (4 years ago)
Latest Published: 2026-02-06 23:01:49 (3 months ago)
Status: Clean (on last analysis)
Analysis Date: 2026-02-06 23:01:49 (3 months ago)
Signed By: Dell Inc
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.

%appdata%\systweak\adu\advanced driver updater
%appdata%\systweak\aso3\driver updater
%appdata%\realdefense\getmydrivers

ThreatInfo has observed bthenum{00001132-0000-1000-8000-00805f9b34fb}.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 100.0%

The most common operating system signal for bthenum{00001132-0000-1000-8000-00805f9b34fb}.exe is Windows 10 with 100.0% 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.

bthenum{00001132-0000-1000-8000-00805f9b34fb}.exe is identified as pe for 32-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 32-bit
Subsystem Windows GUI
Entry point 0x0000f152
Image base 0x00400000

PE Sections:

Sections 4
Raw data 118784

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

.text 81920 bytes · 69.0% of section data
MD5 7b17486858d1cc08ea976ca41602d61d
.rdata 8192 bytes · 6.9% of section data
MD5 36ad220f39610a6578f27cc65f6b07f8
.data 16384 bytes · 13.8% of section data
MD5 fc7f4cfde754de719bf8c6a8ce0ef7f1
.rsrc 12288 bytes · 10.3% of section data
MD5 9439261fbe28ea27627260b866c49e0c

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 662964205a6ac3fa1476eb67787a847e.
  • 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.