Thread: Troubleshooting PW2 6th Gen sticking on USB Drive Mode
View Single Post
Old 07-01-2022, 09:44 AM   #7
Quoth
Still reading
Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.
 
Quoth's Avatar
 
Posts: 14,327
Karma: 105899727
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper
Well, Device manager is a separate thing. I forget where the drive letter assignments (or removing one) are in Windows 7/10/11.

However, it looks like either Windows has a problem or the Kindle has.

VID_1A40&PID_0101\6&1eb6a6e8&0&2 etc is info unique to maker and model of device.

Except that VID and PID is the ID of a USB hub, not a Kindle. See:
https://devicehunt.com/view/type/usb...40/device/0101

From MS site
Quote:
Single-Interface USB Devices

When a new USB device is plugged in, the system-supplied USB hub driver composes the following device ID by using information extracted from the device's device descriptor:

USB\VID_v(4)&PID_d(4)&REV_r(4)

Where:

v(4) is the 4-digit vendor code that the USB committee assigns to the vendor.

d(4) is the 4-digit product code that the vendor assigns to the device.

r(4) is the revision code.
So you DO have communication on USB.

According to MS, this CAN be caused by improper eject, ancient BIOS, bad device driver etc (One dodgy suggestion is to try Windows Repair) or an incompatible device. The Kindle doesn't need any special device drivers.

If a USB memory stick works AND the Kindle won't work in another PC OR "removing" the USB port in Windows Device Manager doesn't work (Reboot and it will automatically be added again), it's likely a faulty Kindle.

Do try a USB hub in-between in-case all the PCs have very fancy USB3.0 ports or something. Sometimes that works.

On another site:
Quote:
11. Replace the hardware. A problem with the device itself might be causing the Code 43 error, in which case replacing the hardware is your next logical step. In most cases, this is the solution to a Code 43 error

Last edited by Quoth; 07-01-2022 at 09:48 AM.
Quoth is offline   Reply With Quote