Problems on Windows 10 (Insider) v. 14376

[HarryT]

Is only the Kobo affected by this? Are other USB devices (external drives, etc) working correctly?

[DNSB]

Originally Posted by HarryT

Is only the Kobo affected by this? Are other USB devices (external drives, etc) working correctly?

There are several other devices including my iPhone and iPad that are affected. I was hopeful when the notes for 14393 stated that iPods would now be mounted properly and it has worked to an extent -- my iPhone/iPad do mount and show the correct free space but when I click on the internal storage, no DCIM directory is shown. On the other hand, my Nexus 7 HD does mount and expose it's externally accessible storage correctly.

There are several devices that have been mentioned in various bug reports by others but I don't have any of them around to test. For the most part, it appears to be devices that mount a select partition rather than the whole file system.

[theducks]

When the original W10 (x64) release installed, I would have a rough time with my K4. Things settled and it just works...every time

So give it a chance. (One does wonder why,they don't have a 'past issues' check list )

[HarryT]

Originally Posted by DNSB

There are several other devices including my iPhone and iPad that are affected. I was hopeful when the notes for 14393 stated that iPods would now be mounted properly and it has worked to an extent -- my iPhone/iPad do mount and show the correct free space but when I click on the internal storage, no DCIM directory is shown. On the other hand, my Nexus 7 HD does mount and expose it's externally accessible storage correctly.

There are several devices that have been mentioned in various bug reports by others but I don't have any of them around to test. For the most part, it appears to be devices that mount a select partition rather than the whole file system.

That's slightly concerning; it would be a real pain if my iPhone or iPad couldn't connect. Fingers crossed it'll be ok.

[beachboybogart]

Originally Posted by theducks

Did you not understand post 17?
It may now be recognized, but it is the wrong TYPE of device.

Yes, pretty sure I understood that post. But I don't understand your response: where does it say the Kobo is the wrong TYPE of device?

[beachboybogart]

Originally Posted by DNSB

I've seen the same issue with my Kobo H2O and Calibre for the last 7-8 preview builds on multiple computers (physical and virtual). The internal storage on my Kobo shows as a drive letter but is not accessible -- click on the drive icon and get an insert disk message. When I look at it in Disk Management, I see 3.17GB of unallocated space. I see no way for Calibre to access the data. This is going to be up to Microsoft and Kobo to fix.

Ah, finally.

Still, the hypothesis is wrong in your retrofitted buick scenario (next post): I would be asking other Buick owners if they had experience with the problem. If no answers, then I would ask Buick and the fob people.

[beachboybogart]

Originally Posted by HarryT

Is only the Kobo affected by this? Are other USB devices (external drives, etc) working correctly?

Personally, all my other devices seem to work fine via USB (XHDs, Android tablet, etc). I was suspicious of my Logitech webcam, but after researching, it appears many people have had the same problem [I]over the years/I], so I would rule it out as a problem device under these circumstances.

[DNSB]

A few hours back, Microsoft released the third cumulative update to Build 14393 bringing it to 14393.10 only hours away from the Anniversary release. The sad news is that the content of the internal storage on a Kobo ereader is still not visible in 14393.10 but then neither is the content internal storage on my iPhone. OTOH, since August 1st was a statutory holiday, I was not able to test on a physical machine, only on VMWare and HyperV virtual machines.

Edit: Back to work today and my Kobo's internal storage is not visible with Build 14393.10 on three physical machines.

[jonty-comp]

Thank goodness, I thought my trusty old Kobo Touch was dying on me - but you're right, it does seem to be Windows 10's fault. The only workaround I had was to download the books from Calibre's webserver using the device browser, but that's such a pain - and it doesn't catalogue them or sync the databases properly!

Here's hoping Microsoft get it sorted pretty quickly after the RTM build drops.

[HarryT]

Originally Posted by jonty-comp

Thank goodness, I thought my trusty old Kobo Touch was dying on me - but you're right, it does seem to be Windows 10's fault. The only workaround I had was to download the books from Calibre's webserver using the device browser, but that's such a pain - and it doesn't catalogue them or sync the databases properly!

Here's hoping Microsoft get it sorted pretty quickly after the RTM build drops.

Apparently reformatting the Kobo's drive with the Windows 10 device manager fixes the problem, but obviously you then need to reload your books.

[beachboybogart]

When backing up your Calibre library, you can also back up the Calibre Configuration files. This will catalogue and sync everything properly, and includes any plugins you have installed.

To find the config files, go Preferences > Advanced > Miscellaneous > Open Calibre configuration directory.

[beachboybogart]

A new cumulative update installed, August 9, with no fixes for Kobos mentioned, and certainly did not change anything. OS still wants to format the drive when it sees it.

[beachboybogart]

UPDATE: Build 14959, Insider Fast Ring, has reestablished the working relationship between my Kobo Aura and Windows 10. As we say in Mexico, thanks the gods.

October 25, 2016: Build 14955 Insider Ring: still no connection to Kobo.

Build 14901 was released to the Insider Fast Ring over the weekend of August 11, and it has completely fixed the Kobo "not recognized" problem. The next build broke that again.