GfxUIEx.exe file report

MD5 990a4dca64708e1e7b2d67557c7f926d
Latest seen 2023-12-11 23:06:57 (2 years ago)
First seen 2017-05-22 09:04:49 (8 years ago)
Size 455 KB
Publisher Intel Corporation
Signed by Intel(R) pGFX

Why it matters

Evidence available for this file

Detection

No final classification is available yet.

Timeline

First seen 2017-05-22 09:04:49 (8 years ago); latest analysis 2023-12-11 23:06:57 (2 years ago).

Publisher context

Company metadata: Intel Corporation. Product metadata: Intel(R) Common User Interface.

Digital signature

Signed by Intel(R) pGFX. 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. 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.

GfxUIEx.exe is a Windows file recorded in the ThreatInfo database. It is associated with Intel(R) Common User Interface. The reported company name is Intel Corporation. The current detection status is Undefined, based on the latest analysis from 2023-12-11 23:06:57 (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: Intel(R) Common User Interface
Company Name: Intel Corporation
MD5: 990a4dca64708e1e7b2d67557c7f926d
Size: 455 KB
First Published: 2017-05-22 09:04:49 (8 years ago)
Latest Published: 2023-12-11 23:06:57 (2 years ago)
Status: Undefined (on last analysis)
Analysis Date: 2023-12-11 23:06:57 (2 years ago)
Signed By: Intel(R) pGFX
Status: Valid

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

%localappdata%\innovative solutions\drivermax\agent\uploads\55qm5eg6mj3jhs8t9878e2a485a00lbffog7w6ybk1yv266x31\display\pci_ven_8086@amp;dev_0416
%localappdata%\innovative solutions\drivermax\agent\uploads\bbcur974lee8586295185ctc6ep64xl0wu53riscob127mi1tb\display
%localappdata%\innovative solutions\drivermax\agent\uploads\3g8928js2t22o4o26mw3283l0wqb0f5x19de6304t0vvxn0k8a\display
%localappdata%\innovative solutions\drivermax\agent\uploads\227n90436fqy3b9wo9k78xvbg4b0yw4ou8w5c6w31334lt9608\display

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

50.0%
25.0%
25.0%

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

Windows 10 100.0%

The most common operating system signal for GfxUIEx.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.

GfxUIEx.exe is identified as pe for 64 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: 64
Image Base: 0x0000000140000000
Entry Address: 0x00011fbc

PE Sections:

Name Size of data MD5
.text 154624 21269ab5a8ada1753aefe0006b17c1f5
.rdata 69632 14c660bdc898f3265d25eec10dc87e13
.data 12288 31354afb57426f71d022f4d764f5ad52
.pdata 9216 47bffa9c5e6627e45bcdc5df066f07cf
.rsrc 188928 f2b0154ac2dfcc30b1f423f5408f8a31
.reloc 2560 e75ec3d25af4cbf029942a1ff08dda01

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: