Enable test mode to solve USB problems?

[CrabbyRightNow]

I see it now in task scheduler but I don't know how to disable it.

 

[CrabbyRightNow]

It's called PC Optimizer Pro64 startups

 

[CrabbyRightNow]

Should I go ahead and work on the clean start?

 

[Slartybart]

If you're still in task scheduler, right click on PC Optimizer Pro64 startups and select delete from the context menu

otherwise, sure - do the clean startup

The clean startup is a no brainier and shouldn't take longer than a few minutes
you're only doing STEP ONE, but I added the same process for the Startup tab (disable all is easiest, the only tick your touchpad)
:ar: be sure to hide all MS services on the service tab


Call it quits for the night when you get tired, I'll be up for a while.
It's probably better to do the next steps fresh and wide awake.

 

[CrabbyRightNow]

@Crabby: When you get back to the forum, please humor CompGeek (his words) and do the SearchMyFiles post he requested.

then read through my post#85 and complete the Clean Startup stuff.

If PC Optimizer is not in the uninstall list - do the Task Scheduler part (I saw the task in Speccy, so I know it is there)

Try installing the Intel USB 3.0 Host Controller Driver again
C:\SwSetup\sp56164\setup.exe

Tell me what DevMgr thinks about the device now. Back to code 52, but no longer unknown?
You can leave it as it is - no need to uninstall it again. The software (if installed) is from the support page for your machine. That's about as good a driver as you're going to get for now.

Bill
.

I just did the install and now am getting code 52.

 

[Slartybart]

You're ok - I expected a code 52

How about the Clean Startup?

 

[ComputerGeek]

I KNEW that darn file had to be there! That Device Manager trace show it IS a driver signing problem

Here's an excerpt of Crabby's last attempt to install "USB Enhanced Host Controller - 1E2D" (that's one of the USB 2.0 controllers. Note today's timestamp at end of the trace (if you use a text editor that shows line numbering, like Notepad++, it's lines 96,514 - 96,532

  dvi: 19:03:39.447                Writing common driver property settings.
     dvi: 19:03:39.462                     DriverDescription=Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
     dvi: 19:03:39.462                     DeviceDisplayName=Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
     dvi: 19:03:39.462                Install Device: Restarting device.
     dvi: 19:03:39.821                Install Device: Restarting device completed.
[COLOR="Red"]!!!  dvi: 19:03:39.821                Device not started: Device has problem: 0x34: CM_PROB_UNSIGNED_DRIVER.[/COLOR]
     dvi: 19:03:39.821           Default installer: Exit
     dvi: 19:03:39.821      {DIF_INSTALLDEVICE - exit(0x00000000)}
     dvi: 19:03:39.837      {DIF_NEWDEVICEWIZARD_FINISHINSTALL}
     dvi: 19:03:39.837           Looking for class installer for 'Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D'...
     dvi: 19:03:39.837           No class installer for 'Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D'
     dvi: 19:03:39.837           Default installer: Enter
     dvi: 19:03:39.837           Default installer: Exit
     dvi: 19:03:39.837      {DIF_NEWDEVICEWIZARD_FINISHINSTALL - exit(0xe000020e)}
     ndv: 19:03:39.837      Device install status=0x00000000
     ndv: 19:03:39.837      Performing device install final cleanup...
[COLOR="Red"]!    ndv: 19:03:39.837      Queueing up error report since device has a PnP problem...[/COLOR]
     ndv: 19:03:39.837 {Core Device Install - exit(0x00000000)}
     ump: 19:03:39.837 Server install process exited with code 0x00000000
<<<  Section end 2015/01/12 19:03:39.837

Note the error entries I highlighted in red!! If you google the first error, it's further confirmed by MSDN documentation HERE - Indeed, we're back to our old friend error Code 52 as the culprit. It's a driver signing problem.

Display Message (Windows 7 and later versions of Windows)
"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)"

Of course now the hard part is figuring out how to fix the driver signing error

 

[CrabbyRightNow]

You're ok - I expected a code 52

How about the Clean Startup?

I did the clean startup. USBs still don't work. They still all have code 52. The USB3 ports seem to have power (mouse lights up) but the USB2 does not light up when I plug in the mouse.e

I also was able to delete PC Optimizer from task scheduler. I must have clicked on the wrong thing before.

 

[CrabbyRightNow]

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. But he said I would have to do it every time I rebooted. I asked him if he had tried it and he said he would get back to me (this was all in a telephone call) but he never called me back. When I went to the shop to pick up my computer, the other tech guy didn't mention it. So I don't know what was up with that. Should I try it?

 

[CrabbyRightNow]

I just looked at the link for fixing a driver signing error and decided it is time for me to go to bed. Goodnight, and thank you all for continuing to work on this. I will check back in the morning for further instructions.

 

[Slartybart]

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

.

 

[Slartybart]

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.

 

[TVeblen]

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.

 

[ComputerGeek]

Quoting Slartybart "Great team effort". Crabby, you've been doing a GREAT job. You know what you're doing around a computer and I'm impressed you can keep up with our collective slew of requests! Good work!

Next., i'd like to check some things re: the USB driver signing problems. Slartybart may still have other avenues to explore. fyi... I have a (limited) knowledge of how driver signing and enforcement works. But let's try collecting some data and see if that helps

• Download sigcheck. Unzip and move the executable to C:\Windows\System32
• Download attached SigTest.zip. Extract the SigTest.cmd file to your desktop
• Right click SigTest.cmd Run as Admin. It generates C:\sigtest.txt. Attach to next post

Next, let's see if there's a simple way to disable driver signature enforcement and if that will "by-pass" the problem ( till you are able to do a clean install)

• Download EasyBCD (scroll down, click Register for the free version)
• Click Download then install (you don't have to enter any of the registration info)
• Run EasyBCD. Click Advanced Settings. Click Advanced tab.
• Check "Allow use of unsigned drivers on 64-Bit windows". Click Save Settings
• Then File->Exit. Reboot. Any better luck with the installs?

 

[CrabbyRightNow]

I've had my coffee and am back on the case.

Bill, I have another HP notebook, an old, slow one, that I have hooked up next to this one in case a disaster strikes.

TV, I booted into safe mode and neither the USB2 nor the 3 USB3 ports worked or showed any sign of life (mouse didn't light up). Device manager showed code 52 on all three USB devices. I rebooted and now the 3 USBs again are lighting up the mouse, but the usB2 still looks dead as a doornail. Device manager shows them all with code 52.

 

[Slartybart]

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
.

 

[ICIT2LOL]

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

 

[CrabbyRightNow]

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

 

[Slartybart]

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
.

 

[Slartybart]

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
.