I have attempted to fix this issue in over a dozen ways and even had the assistance of Microsoft's tech support team helping me and they came to the conclusion that the issue must be that HP has not provided this update for the driver.
Windows 10: Update Issue With HP HIDClass Driver
I wanted to have HP help me with this via chat support but their chatbot is just not helpful for complex questions so I am wondering how could I go about finding this update so that I can attempt to download and conduct the update manually? Or if anyone has any other ideas? Thanks.
I think people are having trouble understanding the vague advice given on here so far. Plus the Microsoft Update Catalogue page is a bit confusing at first glance. I think this is a compatability issue with the latest big Windows 10 update that we downloaded a few days ago.
I also have tried everything. Went to troubleshooter thinking it was a windows update issue but nothing detected. Surely has to be a generic update problem, but who is responsible for fixing it? HP or Microsoft?
HP and Microsoft work together to identify issues that may occur post Windows 10 updates. As issues are identified, HP will release updated drivers and software as fixes through Windows update as well as our Software Download pages. It is recommended that you run all Windows updates to ensure that all latest drivers, software and fixes are installed in your PC. Here is a list of top known issues that may occur on HP products post a Windows 10 update is installed.
HP constantly strives to improve its products and periodically provides updates for software, drivers, and firmware free of charge. So, keep your HP or Compaq computer up-to-date and running smoothly by updating the software on a regular basis.
Is your HP battery not charging or not holding a charge? If you are facing battery related issues with your HP Notebook PC, you may need to replace or calibrate the battery. Test your battery condition and improve battery life using HP Battery Check Utility
This document provides information about working with Windows 10 power plans. In addition, it provides methods for shutting down your computer, using various power modes, and troubleshooting power issues.
This smaller update is intended to combat the Control Center issue some users have. For some users it silently crashes when it tries to open the Main Window. Which after doing the driver package install is the default Window to be launched. Unfortunately, on all my machines and systems the Control Center is working as expected. Right now, I have only some little guessing, where the issue may come from, but do not have any clue about the why and how to fix it.
Recently some users were asking about compatibility and related issues. However it took some time until one was finally dropping a name and i figured all issue were about the same game. Just to make things quick in the future, if you have any game/tool/program that HID Wiimote does not work with, state its name along with the issue in detail. That way i can specifically look into it. If the particular piece of software is either still in active development or open source, there is a good chance i am able to fix it.
The current release only includes the gamepad mode. The following updates are going to resolve around adding further driver modes. The goal is to finally have one driver supporting all kinds of different mode, i.e. IR mouse, DPad mouse, etc.
As said the current release only includes the gamepad mode. So no update for people that use the Wiimote as mouse. Also to simplify the development process a Control Center is only compatible with its accompanied device driver version.
Rather small technical changes for HID Wiimote. First one is primary a fix for Unity3D, when you want to use the Wiimote as gamepad. Unity3D uses RawInput instead if DirectInput, when reading from generic non XInput Gamepads. It seems RawInput has some issues with axes that have a negative value range, e.g. -127 to 127. So the change is to simply use a value range from 0 to 255.
Rather small update with just one and a half fix. Regarding the connectivity issue on Windows 10 Version 1511, i had no issues while testing. Therefore i assume either the updated WDK or another Windows update fixed it. If the problem persists, please report back, so i can take another look at it.
This build has nothing new except that is has been rebuild with the newest Visual Studio 2015 and Windows Driver Kit 10. So for non Windows 10 users there is no urgent need to download/update it. But you can if you like to, just make sure to uninstall the previous/old driver.
So this is a multi-system Desktop build and not an Universal Driver. I am going to provide an Universal Driver as well soon, but there is some work to be done. The driver compiles fine and without any error. The only issue is that i have to make an universal .inf file, which simply requires me to read through the MSDN documentation. However, i am currently not able to test the Universal Driver on a Windows Phone nor on an IoT-System, so the build is going to be purely experimental and for people that just want to give it a try.
Recently, the click commands from my mouse doesn't seen to work. Rather the windows get deselected whenever I click on them. Same thing happens with the touchpad. Even when I tried the touchpad without the USB mouse plugged in. The mouse movement, however, works correctly.
The HP laptops update the 18.32.12 wireless drivers from HP that work for the Intel 8260 AC NIC to later versions like 18.40.0.9 that are very buggy to the point of being unusable. User's cannot even log into their laptops on wifi until we manually roll back the driver.
The HP desktops update the Intel AMT drivers/firmware from our OOB drivers with a later version from Microsoft that is missing the Intel Management and Security Status tool that is mandatory for our systems to automatically get AMT configured.
Why are HP and Microsoft not coordinated in which drivers should or should not get updated automatically? Aren't the OEMs supposed to post their drivers to Windows Updates so only the correct drivers per model get updated?
I added two Run Command Lines to my task sequence. The first was to disable driver updates and reboot. I found it essential to do this before any from the network is accessed, otherwise you will get the dreaded "No physical adapters present, cannot deploy over wireless" and your deployment will fail.
I actually would prefer to get drivers through Windows updates because it's easier than other driver deployment methods, but it becomes much more work when the drivers are not correct or are bug-ridden.
"When the system looks for a driver to use for a particular piece of hardware, it ranks them according to various criteria. If a driver provides a perfect match to the hardware ID, then it becomes a top candidate. And if more than one driver provides a perfect match, then the one with the most recent timestamp is chosen. If there is still a tie, then the one with the highest file version number is chosen"
"Intentionally backdating the drivers avoids this problem. It means that if you have a custom manufacturer-provided driver, it will retain priority over the Windows-provided driver. On the other hand, if your existing driver was the Windows-provided driver from an earlier build, then the third-level selection rule will choose the one with the higher version number, which is the one from the more recent build," Microsoft explains in a developer blog post.
According to a source familiar with the Windows optional drivers, the date shown in Windows Update is taken from the INF file for the driver package. Unless intentionally changed to an earlier date, this date reflects when the driver was created.
For each driver with the same name, they represent the best driver for a specific device in your system. In our example, this means that there are three different devices in our system that have a driver confusingly labeled the same. 2ff7e9595c
Comments