Patch My PC Ideas & Feedback
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
Request for Logitech G Hub to be included in catalog.
It is primary used for gaming accessories (headset / mice etc) and in the COVID / WFH era, staff would like to utilise their own headset for meetings.
An issue occurs when running the Logitech G HUB installation process as the SYSTEM account. After installation, Logitech G HUB automatically launches. However, when executed as the SYSTEM account, the installer mistakenly believes the installation is still ongoing, causing the executable process to hang indefinitely.
There are no additional command-line parameters available to prevent the auto-launch, and no straightforward workaround exists to address this behavior. Unfortunately, this limitation forces us to mark this app as No-Go.
The crew over at silentinstallhq suggest something similar by killing off the launched application as well as a required step. https://silentinstallhq.com/logitech-g-hub-silent-install-how-to-guide/
lghub_installer.exe --silent
TASKKILL /F /IM lghub.exe
Is it possible that the script that launches the installer could also run a separate thread/script who's responsibility is to monitor the installer and wait in the background to see when/if the application attempts to launch in system?
This separate thread could then close the application instance that launched... Which would potentially allow the main thread and the installer to continue and finish normally?
An issue occurs when running the Logitech G HUB installation process as the SYSTEM account. After installation, Logitech G HUB automatically launches. However, when executed as the SYSTEM account, the installer mistakenly believes the installation is still ongoing, causing the executable process to hang indefinitely.
There are no additional command-line parameters available to prevent the auto-launch, and no straightforward workaround exists to address this behavior. Unfortunately, this limitation forces us to mark this app as No-Go.
I understand the concerns raised by Ben. Though for our situation being Intune managed devices... Surely the device is already online and has internet connectivity to even receive the package?
Could this not still be packaged with a provisor/note about it's limitations? The same for any other online only software installations?
My org is preferentially approving applications supported by PMPC. We don't really want to add too much to the workload of having to do things manually.
Unfortunately, the LG Hub installer will reach to the internet during install to update to the latest version. We cannot assume that all clients will have internet connectivity. Install fails if the updater cannot communicate with the LG download URL.
shadow it