Enable test mode to solve USB problems?

Ok, now we're getting somewhere
- inch by inch, slowly I turned....

@CompGeek: see post# 44 :)

The setupapi.dev.log was interesting. It pulls drivers from a few places, one of which is C:\SwSetup (HP's extraction folder)
I'll look deeper into the log, but a quick glance seems as though that folder might be the culprit. I don't know at this point.

---

@Crabby: Good news/bad news - I'll take both. You made me think of another thread where a card reader wasn't working, we checked everything - the solution was to put a card in the reader. Almost like this issue where you plugged in a device and at least there's power.

I have a way to circumvent the code 52 (I think), but that's not a solution, it's a wonky workaround.

So here's where I think we need to go - BIOS F.0A
Before you do that though
Do you have a tablet or a phone that you can get to the forum if the PC complains.
You can roll back a BIOS flash, but not if you can't get to the information.

Maybe a friendly neighbor with a laptop or tablet?

I'm comfortable flashing BIOS, but I'm not there and would be more comfortable if I knew you can reach the forum.
Precautionary only ... given this machine, I think it's a justified precaution

Bill

.

Good call - and goodnight.

The f8 at every boot - nope not worth your time.
Disabling Driver Signing Enforcement is the last ditch effort. I don't want to cripple a good security feature just to get past this. If it comes to that I guess hat's what it comes to.

On the morrow then.

CrabbyRightNow said:

Driver signing error:
This is what one of the tech guys in the shop told me he thought was the problem (see my first post). He said I maybe could work around it by pressing f8 and enabling test mode.

This would also be a good test. You can do this one very quickly and it should not detract you from doing the other suggestions for more than a few minutes.

Start the laptop and repeatedly press the F8 key before the Starting Windows screen comes up. You will be offered some startup options. Choose (highlight) "Safe Mode" and press ENTER.

See if the USB 2.0 port works in Safe Mode, and if they are then recognized in Device Manager and let us know.

Ok good, that gives me that warm and fuzzy feeling knowing you can get back here.


I misunderstood the f8 test mode - thanks TVeblen.

@CompGeek: Disabling Device Signature Enforcement should be in the Advanced Boot Menu - no special tools required.
See: Advanced startup options (including safe mode) - Windows Help

Bill
.

On that code 52 I did find this and it seems to point at something being corrupted and / or damaged ? during install? Code 52: Windows cannot verify the digital signature for the drivers required for this device

Crabby,

I'd like to do the following before flashing BIOS F.04

1) Rename C:\SwSetup to C:\SwSetup-x
This is the folder HP uses to extract install files. IT is only a repository for installs, but the setupapi.dev.log (thanks CG) indicates to me that the structure is odd (the tree and sub-folder names).

2) Use CCleaner Registry feature to cleanup old entries. This tool is relatively safe and I trust it completely, especially if you answer yes you back up the changes.

Piriform cCleaner Download page
Press the Download button under the FREE version
Alternate download method: Piriform cCleaner Download button

Select Run on the download action bar

During or after the install

• Do NOT accept a free trial if offered
  
  
• Do NOT install cross marketing software if offered
  Remove the checkmark from boxes for any additional software (usually a browser or toolbar. ie. Ask or Google)

Launch cCleaner
select Registry in the left hand pane
Press [Scan for issues]
Click on the Data column in the main pane to sort
Select all (I think they are by default)
Press [fix issues]
Answer Yes to the prompt for backup before making changes (press the button to Create a backup, I forget how cCleaner prompts for this)
Press Fix ALL issues

Please restart after cleaning the registry.
...
CompGeek raised a good point. Are you opposed to a Clean install or just want to avoid doing it?

Bill
.

CrabbyRightNow said:

Here is sigtest. I see the words "unsigned". Is that a clue?

I think it's been established fact that the drivers are being flagged as unsigned and that's why they're not installing.
The question is why and that's what some of the tools might show.

I'm going on the assumption that a driver from a major Vendor would not exhibit this issue. That might be a bad assumption. CompGeek's tool shows the MD5, SHA1, PESHA1, PE256, and SHA256 and those can be verified (by CG?? :))

Bill
.