Enable test mode to solve USB problems?

I can't find a reference to F.0b on HP for anything other than a ProLiant server and that's only in the service pack name, not a BIOS.

So I'm stumped where that version came from.
The only logical thing to do is to defer to the BIOS version on the HP support page for your machine.
This makes a bit of sense in that the USB 3.0 ports require additional drivers to work properly, it was the USB 2.0 port that troubled me.

I'll wait until I see the other information I requested before giving the green light on BIOS F.0A

Go ahead and download it

Do NOT install it until I see what Windows Update gave you in the option offers and what Device Manager reports as the device errors, ok?

Bill
.

CrabbyRightNow said:

I had to feed my husband. I am now back on the case. I just got a message that the chipset I am trying to install is an older version than the one on my computer. The one on my computer is version 9.3.0.1021. Should I install the older one or abort this mission?

I'm guessing that you aborted the install - best thing to do.

That was the cosmetic chipset driver - right?
The one from HP is version 9.3.0.1019, so I suppose Windows Update is doing it's job.

---

Regarding the USB controllers screenshots in Device Mgr (don't worry about the Vista reference)
scratching his head

Code 52: Windows cannot verify the digital signature for the drivers required for this device
Published: May 27, 2010
Updated: May 27, 2010
Applies To: Windows Server 2008, Windows Vista

Device Manager displays the following message in the Device Properties dialog box, on the General tab, in the Device Status text box:

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)

Diagnosis

---

The driver may be unsigned or corrupted.

Resolution

---

Try one of the following:
• If the device is a CD or DVD drive, use the Automated Troubleshooting Service, at the Microsoft Support Web site.
• Go to the device manufacturer’s Web site and download and install the latest appropriate driver for the device.
• Search for possible solutions for your particular device on the Microsoft Support Web site. For example, for issues related with an iPod, you might search for “code 52” iPod.

None of that is really very useful.
Bullet 1: doesn't apply, but the troubleshooters in Win7 might help. Let me chew on this for a bit.
Bullet 2: You already did that.
Bullet 3: Will take additional research

I think the best approach is to uninstall all three of those drivers
So you don't battle Windows Update, change the option to Check but let me decide when to download and install.

If you don't Windows, then the updates might be downloading and installing in the background while you're trying to manage the drivers in the foreground. This is only temporary, you can change it back to automatic after you are done this exercise.

After changing Windows Update (WU), launch Device manager and uninstall the three problem devices
If there is a prompt or checkbox regarding uninstalling the software for the driver, answer or select yes

Restart the machine and post the Device manager screenshot(s) General tab for the three devices again.
I suspect all three devices will be unknown, but they might still have software on the system.
Check the General tab - if you see:
The drivers for this device are not installed. (Code 28)
in the status box, then you're good and you can try installing the USB chipset driver again.
It should still be on your system, perhaps your Downloads folder, the file name is sp56164.exe

But...but, HP unpacks their software into C:\SwSetup\filename so look there first for a folder named sp56164. Inside that folder should be a setup.exe - that is what really installs the software.

If I explained all that well enough and you understand - use that setup to install the USB Chipset drivers.
Check what Device Manager thinks about the freshly installed driver
code 52 will require a different tact - turning off Driver Signature Enforcement.

So there are at least tow more things to try if the above fails. There's still BIOS F.0A
I'm not sure which should be done first. If you have questions - please feel free to ask. I'll be on and off for the next few hours.

Sort version:
Change Windows update option - not automatic
Uninstall the problem devices in Device manager, remove software for the drivers
resetart
check device manager and devices (code 28 is good)
reinstall USB chipset from C:\SwSetup\sp56164

I know this is frustrating, if the machine was in front of me (or visa-versa), it wouldn't take as long. That unfortunately is the nature of trouble shooting in a forum - it's not real time.

Thanks for being patient, the third possibility was raised in the code 52 message - there might be malicious code on the box. I want to stress MIGHT. Some people get upset when they hear that - we know a lot more than when we started and after the next steps we'll know more. Checking your system for malware will be a step in the process, it's only a matter of which step 4 or 9 (numbers picked randomly with no assigned importance).

Onward and Upward. I'll see how far you get with those instructions and based on the results, provide the remaining steps.

Bill
.

The Give me updates for Microsoft products really only affects things such as MS Office, and ancillary offers such as Silverlight, Bing.....

It doesn't have any bearing on what you're trying to accomplish.

The second dialog is interesting - thanks for posting that.

Check one more automatic update setting and temporarily disable it if enabled

Launch Control Panel -> Devices and Printers
Right click on the Computer icon (it should be labeled with the name of your computer)
Select Device installation settings from the context menu

Change the settings to match the image below and press the [Save] button

If the settings were already set that way, please let me know.

---

I guess I should ask some questions I should have already asked
1) Is the user id you log in an administrator id or a standard id?
2) Your specs say Anti-Virus: Microsoft. Is that Microsoft Defender or Microsoft Security Essentials (MSE)?
-> If MSE. when was the last scan performed and were there any threats discovered?

Bill
.