Enable test mode to solve USB problems?

CrabbyRightNow said:

I need a portable drive to take back and forth from Michigan to Florida.
Did you really mean 2 gigabytes? I have close to 500 GB on my hard drive right now that I need to back up. I take a lot of photos and videos. I need at least a terabyte.

andrew129260 said:

I am sure he meant 2TB

Opps, of course I meant TB - what a maroon I can be :)

The desktop versions of external drives are also portable - the main purposes are different.

A slim/portable drive is usually carried around wherever you go. It is storage for devices (laptops / game machines) that have no internal space for another drive.

A desktop version usually sits on your desk and is used for backup and cold storage (files that aren't needed all the time, but you don't want to look in a backup for them). This, of course, can be used for live data too, but that's a tricky data schema.

I think the desktop drives are a bit more reliable, only because of the form factor (bigger means more air, not only for cooling, but for the heads. Finally, the more you transport a drive, the more likely an error (bumps and bruises).

So if you're only going to transport the drive between MI and FL, then a desktop is what I suggest. If you want to carry the drive with you when you paint, then the slim/portable does the trick.

The best of both is to use the space on your laptop while you're out and about, and then copy ('backup') the new stuff over to the external drive on your desk when you get home. (every once in a while, you'll have to manage the data on your laptop - keep only what you want to have readily available). It sounds like a lot of work, but once you get a routine, it's not that bad.

Bill
.

CrabbyRightNow said:

I still have USB2. USB3s still don't work. Don't know why they worked last night before I plugged mouse into USB2. A clue?

I'm catching up - darn ... the re-install of USB 3.0 driver failed.

I was curious about your comment (the mouse worked on USB3.0) - is it a USB 3.0 mouse?

Clearly the ports are not working, but if the mouse isn't 3.0, I'm not sure it will work on a 3.0 port.

A 3.0 device will work on a 2.0 port (backward compatible).reading, reading, reading....

Bill

CrabbyRightNow said:

This is from a link ComputerGeek posted. Would something along these lines be worth a try?
.....
The .sysold files are the ones I renamed, I think also renamed the usbccgp.sys - but accidentally deleted it after the rename..

If it's a permissions issue, it's better to check before rename. Right click the file(s) and look on the security tab /advanced button and see who the owner is and who has permissions. You might find that you don't have to make any changes.

---

ComputerGeek said:

.....
(fyi.To anyone reading the thread in the future: The intent is to verify that the installed files (as enumerated in my batch file) match the set of files for the driver package Windows has saved in the DriverStore. Any mis-match in the set of installed files would cause the digital signature to break

I'm still catching up, but have a question. Is the install failure (code 52) - in other words, is the 3.0 install issue a signature issue, or is it something else. The event viewer would probably tell us something about the error.

Let me take a look at all the data recently posted and then I'll play catchup again.

Bill
.

In post# 239: The device error is only on the USB 3.0 device. I believe it will show (code 28) which means device driver not installed. Could you check that in DevMgr? Double click the problem device and look at the general tab.



Shows that a restart is required - have you restarted the machine?

Bill
.

just an image tip:
Open Paint
click the blue file menu, select properties
change both width and height to a smaller value (40)
press [OK]
Ctrl+S to save (I don't know if this is necessary, but please do it in case it is)
name=x
close Paint

The next time you paste something into Paint, you won't have all of the extra white space.

Bill
.

Scalpel!

The Controller - no driver,
the HUB is unplugged??

Please merge this file into the registry. It adds an environment variable to your profile so you can see 'ghost' devices in DevMgr.

Download HKCUenv.reg and double click to merge it
HKCUenv.reg

Here's what is in the .reg file

Code:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Environment]
"devmgr_show_nonpresent_devices"="1"

Once the environment variable is set,
open DevMgr
select View - Show Hidden devices

look for a greyed out (nonpresent) device for the HUB (probably under other devices, but possibly under Universal Serial Bus)
and post a screen shot, then you can uninstall the ghost hub (if it's there).

+edit

I don't know if Disable Driver Signature Enforcement is a per boot setting. so you might check that it is still disabled before trying to re-install the USB 3.0 driver
see post#229

Let me know where you found the driver (SwSetup or Downloads) or if you downloaded it again.

IF the scalpel approach to cleaning up ghost entries didn't help use the Hatchet
Run drive cleanup: see post# 22

and try the USB 3.0 install (keeping the Device Signature Enforcement caveat above in mind

Jerry, I know you're probably going to point out the unsigned driver - hence my question about disabling the enforcement being a per boot setting

-edit

Thanks,

Bill
.

Take no action yet-until I see that the other normal channels have been tried
Information only at this point

There is the "the heck with the HP installer, use DevMgr to install the driver from the unpacked source" approach you have not tried.

Here's a USB only csv file of DevMenView
DMV_Sheila(onlyUSB).zip

The current USB 3.0 driver on the machine is v 1.0.0.199

I came across an advisory on HP which talks about installing from external devices and recommends installing from the HDD. That's what Sheila has always done, so this advisory is not applicable to the issue.

DESCRIPTION

The Intel USB 3.0 driver does not re-install from an external USB device. Device Manager will display the USB 3.0 driver as an Unknown Device.
Figure 1: Driver Installation via Installer:

This is, in my opinion, utter nonsense. HP service paqs, expand into the Swsetup folder (normally on C:\), so it would already be unzipped and on the hard drive. The install is initiated from the unpacked location. Maybe there's something in the upper installer that fails when the USB device is updated, but the rest .....

Try a normal install, then if the device still doesn't function, try an install from C:\SwSetup\sp56724
HP's high level installer might be causing the problem, not the driver

The USB 3.0 device is not working, so it's worth a shot to try v 1.0.3.214

I'm aware of the model differences in both the driver and the advisory, I'm also aware of how poorly HP keeps it's information updated.

I'm still digging through the DMV.

Another hold off for later post: I don't want to lose the information

Intel released two USB 3.0 chipset drivers (216 and 220 chipset)
You have an Intel 216 chipset on your machine.

Here's the USB 3.0 driver for the 216 chipset from Intel
USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family

Intel said:

Filee name: Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver.zip
Version: 1.0.10.255 (Latest)
Date: 02/03/2014
Size: 5.22 MB
Language: English
Operating Systems: Windows 7 *, Windows Server 2008 R2*