Thread: Calibre not seeing Kobo in Windows 10 Preview builds
View Single Post
Old 07-16-2016, 07:32 PM   #3
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 44,475
Karma: 167902649
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by beachboybogart View Post
I've been trying to discover if any Kobo users (Aura HD in particular, but any Kobo) have had problems in the last few builds of Windows 10. Currently, my Kobo is recognized in File Explorer as a drive letter, but is not being seen by Calibre or the Kobo Desktop app.

I've done some extensive testing for drivers, using clean installs of Calibre, etc., to no avail. Users of MobileRead in the Calibre forum have not experienced this.
If you are using the Preview builds, that is a known issue. It's been there for the last 7-8 Fast Ring builds and is still there with the 14390 build. It happens on my laptop running Windows 10 as a VMWare virtual machine and on 3 physical machines.

What I see is the external uSD card in my H2O mounts happily but the internal storage shows as a drive letter and when I click on it, I'm asked to insert a disk. Disk Management shows it as a 3.17GB unallocated storage.

I've reported it with each build but so far no feedback as to whether it will be fixed.

Oddly, when I did a factory reset on an Aura HD, it was recognized and updated. After the update/restart, it was no longer recognized.

There was some discussion of this issue in another thread concerning Firmware 3.19.5761 https://www.mobileread.com/forums/sho...&postcount=155 as a start point.
DNSB is offline   Reply With Quote