● Update · August 16, 2026
Nothing in this report has changed, and that is the point. LG agreed to disable the McAfee pop-up; by July 24 the McAfee references were off the Store listing. Every finding below sits in the layer underneath that pop-up — the delivery, the missing consent, the persistence. Both LG packages are still resident on this machine, still wired to 51 hardware IDs.
What is new is a promise, not a change. An LG support notice dated August 3, 2026 says LG “is updating the Installer so customers can decide whether they would like to install it” — the first acknowledgement of the consent gap this report documents. It carries no date, version or mechanism, and says nothing about the two driver-store packages below. The app's Store product was updated on August 12; no changelog is published, and we have not re-run a first-connection test, so we cannot tell you whether the behaviour recorded here still reproduces. This machine has not been cleaned or reconnected — it is held as it was. What the notice says, in full.
One limit, stated plainly: LG told press the installer “does not access, collect, or transmit any customer personal data.” This report makes no claim either way. We captured no network traffic, and nothing here is evidence of exfiltration. What is documented is how the software arrived, that no consent surface existed, and that Windows maintained it for nine months after the monitor was gone. Claim-by-claim comparison in the full report.
Handling note. Redacted for the machine owner's privacy: hostname, OS baseline date and the panel's serial descriptor are withheld. Manufacturer and product IDs and the model mapping are kept — they prove identification without fingerprinting the unit. Removal was not performed here; the machine is preserved as evidence and available for verification.
Summary of findings
- On September 30, 2025, with an LG UltraGear 27GR83Q connected, Windows Update delivered two LG packages of class Extension and SoftwareComponent. Neither contains driver code.
- The packages install
LGElectronics.LGMonitorApp from the Microsoft Store under SYSTEM, about 32 seconds after delivery. No prompt, no EULA, no entry in the classic programs list.
- The monitor was disconnected in mid-October 2025. The app remained, and self-updated as SYSTEM on July 9, 2026, nine months later.
- Both LG packages remain in the Windows driver store, wired to 51 hardware IDs across 19 monitor models. Uninstalling the app alone leaves the machine armed.
- Both packages are signed "Microsoft Windows Hardware Compatibility Publisher." The machine was on stock default policy. This is the out-of-box Windows experience.
The machine
- Host: REDACTED (Windows 11, stock default device-installation policy)
- OS baseline: REDACTED
- Trigger device: LG UltraGear 27GR83Q (manufacturer and product IDs retained in evidence; serial descriptor and numeric serial withheld)
- Other displays present: seven other panels from three brands were recorded on this install; none triggered any software delivery.
The install chain, to the second
Reconstructed from Windows Update, CBS/servicing, Store install-service and Reliability Monitor logs. A small clock offset between sources was measured and accounted for; the ordering is unaffected.
- 9:52 PMDelivery. Windows Update hands over two LG packages for the connected UltraGear: an Extension INF and a SoftwareComponent INF. Neither carries driver binaries.
- ~9:52 PMA device that doesn't exist. The Extension package fabricates a phantom child device under the monitor. Its only purpose is to give the SoftwareComponent package something to bind to.
- +32 secThe directive fires. Windows fetches
LGElectronics.LGMonitorApp from the Microsoft Store. SYSTEM installs it.
- Next logonRegistered to the user. No installer window, no consent dialog, no entry in the classic Programs and Features list — at any point.
The two packages
Both from provider LG Electronics Inc., dated August 27, 2024, WHQL-signed and co-signed by Microsoft. In the driver store:
lgmonitorappextension.inf — class Extension. No driver code. Fabricates a phantom child device so a companion package has a binding target.
lgmonitorappsoftwarecomponent.inf — class SoftwareComponent. No driver code. Carries the single directive that delivers the app.
The delivery directive lives in the SoftwareComponent INF: an AddComponent entry with SoftwareType = 2 — the INF form that tells Windows to install a named Microsoft Store app for a device. Target: LGElectronics.LGMonitorApp. That is the entire mechanism. A “driver” whose only job is to make Windows install an app.
The full INF text and the complete signing chain are preserved in the evidence set.
Consent surfaces: none
We looked specifically for the points where a user could have seen or approved this:
- No installer window or progress UI at install time.
- No EULA or terms prompt before the app was placed.
- No entry in the classic Programs and Features list — the app appears only under Settings → Apps → Installed apps.
- Delivery ran under SYSTEM, not the user. Nothing was gated on a click.
Persistence is active, and Windows does the maintaining
The panel was unplugged in mid-October 2025. The app was not. Version chain on this machine:
1.2405.3001.0installed Sep 30, 2025
1.2602.502.0interim build
1.2606.1601.0SYSTEM self-update, Jul 9, 2026
- July 9, 2026, 2:11 AM — the app self-updates to
1.2606.1601.0, staged by SYSTEM. Nine months after the monitor left.
- July 15, 2026 — Device Setup Manager is still re-staging the orphaned monitor's metadata.
- July 17, 2026 — the Microsoft Store install service touches the app again.
Uninstalling the app alone does not end this. Both LG packages stay in the driver store, and reconnecting any listed LG panel re-arms the chain. Full removal is in the fix.
The trigger list
The resident LG extension package wires 51 hardware IDs across 19 monitor models for automatic app delivery. The models:
34WQ73A34BQ77QC27BQ85U27UQ750
28MQ75027GR83Q27GR93U32GR93U
27UQ850V32UQ850V32GR75Q27GS85Q
32GS85Q27BA85024BR750E27UP850
24BA85024BA75027BA750
Each model maps to one or more hardware IDs (monitor plus hub/companion enumerations), 51 in total; the complete table is preserved in the evidence set. Note what is absent: the models driving the news cycle — UltraGear 34GX900A-B, 27GP83B, 27GN800, UltraFine 32UN880-B — do not appear in this revision. LG ships multiple revisions with different coverage, so the real footprint is larger than any single list, ours included.
What is not affected
- Every non-LG display on this machine. Seven other panels from three brands were present across this install. None triggered any software delivery.
- Dell, as a direct contrast. The Dell S2716DG's package came through the same Windows Update channel — a normal monitor driver, no app payload. Same road, ordinary cargo. That's what a benign monitor package looks like, and it's what LG's is not.
Alienware was named alongside LG in early coverage, so the distinction matters. Dell told TechSpot that current Alienware Command Center versions require the user to approve installation and show no third-party advertising, with an opt-in prompt added in AWCC 6.6, February 2025. Dell's documentation confirms Windows can still begin that install after detecting supported hardware — same road, consent step added. We have not tested Alienware hardware ourselves; we report Dell's statement as a statement.
Removal (two layers)
-
Remove the app. Settings → Apps → Installed apps → uninstall LG Monitor App. Or from an elevated PowerShell:
Get-AppxPackage -AllUsers LGElectronics.LGMonitorApp | Remove-AppxPackage -AllUsers
-
Remove both delivery packages so the machine can't re-arm. List the driver store:
pnputil /enum-drivers
Find the entries from LG Electronics Inc. named lgmonitorappextension.inf and lgmonitorappsoftwarecomponent.inf. Read each published name off the list (oemXX.inf; the numbers differ on every machine), then run once per package:
pnputil /delete-driver oemXX.inf /uninstall
Surgical: it removes only LG's app-delivery packages. Other devices keep their drivers and companion software, and real driver updates keep flowing. Windows Update can re-offer LG's packages if a listed LG panel is connected again.
On Windows Home, where there is no Group Policy Editor, the device-metadata hardening step and its caveats are on the main page: the fix, including the registry method.
Verify it yourself
This machine was not cleaned; it is held as evidence. If you can reproduce or refute any step, we want to see it. What we're collecting — and the PowerShell to read your app version — is on the main page.
← Back to the alert