🟦 6. Official style (EN)
We performed an extensive investigation to determine why Logitech SetPoint stopped opening its main window. We checked drivers, services, Windows security components, reinstalled the software, and analyzed event logs.
Eventually, we discovered that the issue was not caused by SetPoint itself but by the Percentage application. After installing one of the packages required by Percentage, SetPoint failed to initialize HID devices and froze during startup. Removing that package immediately restored normal functionality.
It appears that Percentage or one of its dependencies unintentionally interferes with HID initialization used by older versions of SetPoint.
🟦 7. Technical style (EN)
We ruled out all SetPoint‑related causes: WDAC, SmartScreen, SAC, driver blocks, missing DLLs, COM initialization issues, and process failures.
The root cause turned out to be the Percentage application. One of its installation dependencies modified or hooked into the HID/Bluetooth stack, causing SetPoint to hang during device initialization and preventing the UI from loading.
After removing the package, SetPoint started working normally. This indicates a conflict between Percentage’s dependencies and SetPoint’s HID initialization routines.
🟦 8. Friendly style (EN)
We tried everything to figure out why SetPoint wouldn’t open, and after a lot of testing we finally found the cause. It wasn’t SetPoint at all — it was the Percentage app.
One of the packages it installs caused SetPoint to freeze during startup. As soon as we removed that package, SetPoint started working again.
Looks like one of Percentage’s dependencies conflicts with SetPoint’s HID initialization.
🟦 9. Direct and strict style (EN)
After checking every possible cause on the system — drivers, services, logs, security settings — we found that SetPoint wasn’t the problem.
The issue was caused by the Percentage application. One of its required packages interfered with HID initialization, which made SetPoint freeze on launch.
Removing that package immediately fixed the issue. The conflict clearly comes from Percentage or its dependencies.
🟦 6. Official style (EN)
We performed an extensive investigation to determine why Logitech SetPoint stopped opening its main window. We checked drivers, services, Windows security components, reinstalled the software, and analyzed event logs.
Eventually, we discovered that the issue was not caused by SetPoint itself but by the Percentage application. After installing one of the packages required by Percentage, SetPoint failed to initialize HID devices and froze during startup. Removing that package immediately restored normal functionality.
It appears that Percentage or one of its dependencies unintentionally interferes with HID initialization used by older versions of SetPoint.
🟦 7. Technical style (EN)
We ruled out all SetPoint‑related causes: WDAC, SmartScreen, SAC, driver blocks, missing DLLs, COM initialization issues, and process failures.
The root cause turned out to be the Percentage application. One of its installation dependencies modified or hooked into the HID/Bluetooth stack, causing SetPoint to hang during device initialization and preventing the UI from loading.
After removing the package, SetPoint started working normally. This indicates a conflict between Percentage’s dependencies and SetPoint’s HID initialization routines.
🟦 8. Friendly style (EN)
We tried everything to figure out why SetPoint wouldn’t open, and after a lot of testing we finally found the cause. It wasn’t SetPoint at all — it was the Percentage app.
One of the packages it installs caused SetPoint to freeze during startup. As soon as we removed that package, SetPoint started working again.
Looks like one of Percentage’s dependencies conflicts with SetPoint’s HID initialization.
🟦 9. Direct and strict style (EN)
After checking every possible cause on the system — drivers, services, logs, security settings — we found that SetPoint wasn’t the problem.
The issue was caused by the Percentage application. One of its required packages interfered with HID initialization, which made SetPoint freeze on launch.
Removing that package immediately fixed the issue. The conflict clearly comes from Percentage or its dependencies.