The evidence question
Does the lab system contain one specific, non-protected startup registration that documentation and dependency inspection justify testing as a reversible variable?
Yes: the exact machine-wide Logitech Download Assistant Run value. Its registered LogiLDA.dll payload was not present, while the registration remained visible through the registry and Win32_StartupCommand.
That selects EXP-007. It does not establish that the entry is enabled, invoked, costly, or unnecessary for every future Logitech workflow.
Exact component and protected boundary
| Item | Observed state | Disposition |
|---|---|---|
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunLogitech Download Assistant | String value; Microsoft-signed rundll32.exe; entry point LogiFetch; registered LogiLDA.dll absent | EXP-007 research candidate |
| Teams Run value | Present | Existing EXP-006 scope; not duplicated |
| Tailscale startup link | Present in the common startup folder | Protected user startup application |
| SecurityHealth Run value | Present | Protected Windows security component |
| Realtek audio Run value | Present | Preserved device and audio component |
| Send to OneNote startup link | Present | Unresolved; not selected |
No related Logitech service, scheduled task, or currently present Logitech device was found by the bounded inventory. That absence does not prove that a Logitech device will never be connected or that supported software will not repair the helper later.
EXP-007 is limited to one registry value. It must not uninstall or modify any Logitech application, service, task, file, device, or driver.
Documented behavior and dependencies
Microsoft documents Run values as commands that execute when a user logs on and says their order is indeterminate. Microsoft also documents Win32_StartupCommand as an inventory surface for automatically launched logon commands.
Logitech describes Download Assistant as notification software that helps install Logi Options+ or G HUB for supported devices. Its currently documented device compatibility is limited, but that description does not make the component universally unnecessary.
Microsoft's Post On/Off metric covers background CPU and storage activity after the shell appears. Microsoft says additional startup applications usually affect that phase, while also directing engineers to attribute activity to specific processes. The general guidance does not prove a cost for this entry.
Evidence ledger
Documented facts
- Run values are logon commands with indeterminate ordering.
Win32_StartupCommandenumerates configured automatic logon commands.- Logitech positions Download Assistant as installation-notification software.
- WPR supplies repeatable On/Off recording profiles for process attribution.
Lab measurements
One read-only inventory on AC found the registration and missing payload. No startup duration, CPU cost, storage cost, delay, error, readiness endpoint, or treatment effect was measured.
Hypothesis
If the entry is effectively enabled and Windows attempts to invoke its missing payload, removing the exact value may avoid a failed launch attempt and reduce post-logon work. This is unverified.
Unresolved questions
- Is the entry enabled and attempted at logon?
- Does a boot trace attribute work or errors to it?
- Could Logitech repair or update legitimately recreate it?
- Does any current or planned device workflow depend on it?
What EXP-007 must prove
- Confirm the effective startup state and exact registry identity.
- Define off-to-usable as successful sign-in, responsive shell, required network and device readiness, and protected Omnissa, Windows App, Remote Desktop, and Tailscale workflow readiness.
- Use a supervised WPR On/Off trace to attribute activity before changing anything.
- Qualify instrumentation overhead and preserve repeated control and treatment runs, failures, medians, variability, thermal, power, and network state.
- Accept the change only if the EXP-001 decision rule shows improvement without a readiness or compatibility regression.
Future PowerShell tooling must provide support detection, exact original path/name/type/value capture, dry run, one-value apply, configuration and workflow verification, structured logging, idempotence, exact restoration, rollback verification, and reboot-persistence testing. Apply and rollback require a supervised lab session.
Compatibility and rollback status
The observation applies only to the recorded HP ZBook Firefly 14 inch G8, Windows 11 Pro build 26200, BIOS T76 01.24.02, and the command identity observed July 27, 2026. Any identity, payload, device, software, build, or management-state difference must be treated as unsupported until separately tested.
Nothing changed, so rollback is not currently applicable. The future rollback boundary is restoration of the exact captured registry value only.
Primary sources
All sources were retrieved July 27, 2026.
YouTube briefing
Presenter: This hour inspected the ZBook's logon startup entries without changing them.
Windows still exposes a Logitech Download Assistant Run value. Its launcher is signed by Microsoft, but the registered Logitech helper file is missing.
That is a clue, not a benchmark. We have not proved the entry is enabled, attempted, or slowing startup. No WPR trace, repeated run, median, or measurement-overhead test ran.
The exact value is now the one variable in EXP-007. Teams remains with EXP-006, Tailscale remains protected, and Windows Security and the Realtek audio component remain untouched. Nothing was applied and no performance gain is claimed.
Source and next layer
- Merged source pull request #24
- EXP-007 focused research issue
- Layer evidence and limits
- Preserved read-only observation
The next hourly cycle position is layer 9: Group Policy, MDM-aware policy, registry, and system configuration.