View Single Post
Old 09-02-2019, 03:21 PM   #52
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,123
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by crane3 View Post
Also possible a faulty/screwed-up usb driver from microsoft. Check if there is a 'later' driver for update.

I encountered same problem when trying to update the Mars via usb as it was the 1st gen & the only possible method with firmware. I did let it go for a while as I was still able to do stuff in wifi.

Read about another person had similar problem on a newsgroup; decided to check for udates & received an usb update, coincidentally. The usb driver was an outsourced to another company by microsoft.

A bad micro$oft may be "rare" but also worthwhile checking.
I agree.
Chip
Don't look for the Kindle in the Device Manager. Look for a UNKNOWN or USB device with a Yellow mark. Delete that, then attach the Kindle again.
A corrupt detection leaves the status as a Known Un-Known.
theducks is offline   Reply With Quote