GridinSoft Threat Intelligence

LGPO.exe file report

Clean record File reputation report
MD5 e447f9cbad5b6466f678fb5d86e018c7
Latest seen 2023-10-30 23:05:55 (2 years ago)
First seen 2023-08-01 23:29:55 (2 years ago)
Size 471 KB
Product LGPO.exe
Signed by Lenovo

Why it matters

Evidence available for this file

Detection

Latest status is clean for this hash.

Timeline

First seen 2023-08-01 23:29:55 (2 years ago); latest analysis 2023-10-30 23:05:55 (2 years ago).

Publisher context

Company metadata: Microsoft Corporation. Product metadata: LGPO.exe.

Digital signature

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

LGPO.exe is a Windows file recorded in the ThreatInfo database. It is associated with LGPO.exe. The reported company name is Microsoft Corporation. The current detection status is Clean, based on the latest analysis from 2023-10-30 23:05:55 (2 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: LGPO.exe
Company Name: Microsoft Corporation
MD5: e447f9cbad5b6466f678fb5d86e018c7
Size: 471 KB
First Published: 2023-08-01 23:29:55 (2 years ago)
Latest Published: 2023-10-30 23:05:55 (2 years ago)
Status: Clean (on last analysis)
Analysis Date: 2023-10-30 23:05:55 (2 years ago)
Signed By: Lenovo
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.

%commonappdata%\lenovo\vantage\addins\lenovosystemupdateaddin\1.0.9.76\policymigration

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

LGPO.exe 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 0x0002b560
Image base 0x00400000

PE Sections:

Sections 5
Raw data 471040

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

.text 330752 bytes · 70.2% of section data
MD5 d0298894348b905f8c3000d549524485
.rdata 115712 bytes · 24.6% of section data
MD5 b3a0cca1913d3c0f9d6b3470e4bc6148
.data 5632 bytes · 1.2% of section data
MD5 24155a55fba96dcaa0c04391c9751861
.rsrc 2048 bytes · 0.4% of section data
MD5 ff11914ef05a6e319d090a576ef1ad68
.reloc 16896 bytes · 3.6% of section data
MD5 579269f4a10b34a992c6815559361491

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 e447f9cbad5b6466f678fb5d86e018c7.
  • 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.