#Logitech g hub stuck on installing how to#
#Logitech g hub stuck on installing update#

I messaged Logitech and they suggested I uninstall G Hub and reinstall as admin. In case anyone finds this, here's an update: Here are the minidumps from the other pc: !AlIE3vqqC9biq35VnMmKO5w_mUVM?e=vNtazVįirst post on here, so my apologies if I did something wrong. Here are the minidumps from the PC that was running g hub on startup: !AlIE3vqqC9biq3pCfXCLlHfoHpVR?e=aLI5J9 On both PCs, the device manager indicates the driver for the mouse was published by Microsoft in 2006 (2.1), so it doesn't look like they are using anything from logitech.

#Logitech g hub stuck on installing how to#

Not sure how to get these things as stable as possible as soon as possible, but that's what I'm after. However, without running Driver Verifier, we were both getting BSODs at a much lower rate while running G Hub. The obvious answer is, don't use G hub, which would kind of suck, because I want to be able to control the LEDs, mouse buttons, dpi, and other mouse settings easily. The result was a BSOD as ghub was launching (again Driver Verifier is still running on this PC, but it is far more stable because g hub wouldn't launch on start up). On the PC that wasn't crashing, the LED colors (also on a G502 Hero mouse) were the default ones, which made me wonder what would happen if I turned G Hub on on that PC. This PC that would crash very quickly had logitech g hub set to start on start-up and the LED colors on the G502 Hero mouse indicated it was running. I turned off the Driver Verifier, and the problem seemed to be logi_joy_vir_hid.sys and HIDCLASS.SYS. But it never seemed to last more than a minute after logging into windows before BSOD. Sometimes it would get stuck before then. On the other PC, it was getting a BSOD shortly after logging into windows. Then I ran Windows Driver Verifier, and was not having any problems on one PC.

#Logitech g hub stuck on installing update#

I used Driver Booster 7 to quickly update all of my drivers.

So I ran the extended Windows Memory Diagnostics and no problems were discovered. The common issue that kept popping up seemed to be a problem with ntoskrl.exe. When I first started getting the BSOD, I used BlueScreenView to view the Minidump files. Windows 10 Home no updates available as of writing this. Motherboard: ASRock B450M Pro4 with the latest BIOS (P3.60) Background: I just built two identical PCs and both are getting BSODS, and it seems highly likely the issue is related.