Problems on Windows 10 (Insider) v. 14376

[beachboybogart]

Okay, I'll try to stay calm. First the news: Windows 10 has another update, and the Kobo Aura is now recognized as a device. I know this because it shows up as a USB Mass Storage device in Device Manager, and because it is recognized as an "ejectable" device in the "Safely Remove Hardware" app.

BUT Calibre doesn't see it. Neither does the Kobo desktop app. But please bear this in mind: I asked simply "if anyone else had seen this". At NO TIME did I suggest that Calibre was at fault. But it is quite possible that someone else has run into this, and has a solution (plug in, latest build, whatever). Now I ask this: why wouldn't this forum be a source of information for this kind of question, anymore than any other forum, considering it's Calibre I'm trying to connect to? You seem to be suggesting that I am the only one in the world that would ever has this problem, and that it's mighty stupid of me to ask other Calibre users if they have, too?

Trust me (or not): I'm grown up enough to know how to search for answers on the Web. But let me take your advice one step further: I drive a Buick; it uses chipped keys for the locks. If I was to buy a third-party chipped key that doesn't work on my car, would it be wrong of me to go to a Buick forum and ask "Anybody else seen this?" Or would you decide for me that I should go to the "chipped key" forum instead.

Originally Posted by eschwartz

And frankly, I am surprised that you posted this as a discussion in the calibre forums -- implying that calibre has anything to do with it one way or another.
When the real problem is that Windows isn't recognizing the device, so no applications will see it, not *just* calibre.

Again, ask on the Windows support forums or raise a bug report with Microsoft. They are far more likely to have an answer than we are.
Such is not unreasonable when running a beta OS.

Or at least, post it in the MobileRead subforum devoted to the Kobo Reader, since fellow Kobo owners might know why the Kobo isn't being registered by your beta OS. Or at least they might share your experience.
They might also suggest asking Microsoft about it, but they would at least be more supportive (since it affects them too), also they won't be snippy about your posting in a forum that has nothing to do with your problem.
Such is not unreasonable when having non-program-specific problems with a specific device.

...

tl;dr

We are only being judgmental because you are asking the wrong people for help. Wrong: I asked the right people. You were the wrong person to answer. And you were damned patronizing about it, assuming I'm not creative enough to also ask elsewhere.
And we are only being unhelpful because we have no help to offer.
Actually, scratch that -- we helpfully told you who might know more about the matter.

[kovidgoyal]

It needs to show up a drive with a drive letter in windows explorer before calibre has a hope of connecting to it.

And, just FYI, if you have problems with device detection, the procedure to follow is described here:

http://manual.calibre-ebook.com/faq....ted-by-calibre

[eschwartz]

And now that it shows up as a device in Windows, we can try to help you get calibre to notice that.

As Kovid said, try the debug device detection and report the results here.

P.S. I didn't patronize you, but you certainly didn't ask in the Kobo forum and it is immaterial whether you also asked in Windows forums -- we are still not the right place to ask why Windows doesn't recognize it.

[beachboybogart]

Again, I did NOT ask (this is the third time I am repeating this) why Windows didn't recognize. I don't know why you are not seeing this and understanding it.

And I'm pretty sure you were the one who suggested I be looking at Windows forums, so I was merely answering you on that.

[beachboybogart]

Originally Posted by kovidgoyal

It needs to show up a drive with a drive letter in windows explorer before calibre has a hope of connecting to it. And, just FYI, if you have problems with device detection, the procedure to follow is described here:http://manual.calibre-ebook.com/faq....ted-by-calibre

Thanks, Kovid. It shows up in Device Manager, but it also shows up as a drive letter in File Manager. The interesting thing now is that, when I click on the drive letter, Windows tells me "the drive is not formatted". I appreciate the link, and I have certainly, as a computer repair person, done my share of device detection, including at times in the past your own techniques for same. I'm pretty sure that, since no one who has seen this thread has responded with a similar issue, that it is most likely a Windows problem.

Meantime, I will continue with web searches and hope that at some point, an OS update--or some other magical meeting of coding--will clear this up.

[theducks]

Originally Posted by beachboybogart

Again, I did NOT ask (this is the third time I am repeating this) why Windows didn't recognize. I don't know why you are not seeing this and understanding it.

And I'm pretty sure you were the one who suggested I be looking at Windows forums, so I was merely answering you on that.

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

[DNSB]

Originally Posted by beachboybogart

The first build that stopped Calibre from working has since been released to the general public; it is no longer a "beta". And frankly, I am surprised and disappointed that this board in particular is engorged with so many unhelpful and judgmental comments. What a shame.

You may recall my OP asked if "anyone else" was having this problem.

Do you mean it has been released to the Slow Ring? Or the even slower Preview Ring? Either way, it's still preview/beta code.

[DNSB]

Originally Posted by kovidgoyal

It needs to show up a drive with a drive letter in windows explorer before calibre has a hope of connecting to it.

And, just FYI, if you have problems with device detection, the procedure to follow is described here:

http://manual.calibre-ebook.com/faq....ted-by-calibre

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.

[DNSB]

Originally Posted by beachboybogart

Trust me (or not): I'm grown up enough to know how to search for answers on the Web. But let me take your advice one step further: I drive a Buick; it uses chipped keys for the locks. If I was to buy a third-party chipped key that doesn't work on my car, would it be wrong of me to go to a Buick forum and ask "Anybody else seen this?" Or would you decide for me that I should go to the "chipped key" forum instead.

Hmmm... let's change your hypothetical. Buick comes up with an update for your car which then breaks the third-party chipped key you've been using for the last couple of years. So a complaint to Buick and the chipped key manufacturer would be in order (in my not-so-humble opinion).

In this case, both Microsoft and Kobo are aware* of the issue though I haven't heard of any fixes being forthcoming.

*Aware in this case means that I have whinged about the issue.

[PeterT]

As I've mentioned to Kobo staff this is a very ugly situation. If the fix requires Kobo to update f/w then there will be an issue with all those people who won't update f/w but run Windows 10

[JSWolf]

I'm going to wait ad see what happens before doing the anniversary upgrade. if it works, I'll do it. If not I'll wait until things are fixed.

[DNSB]

Originally Posted by JSWolf

I'm going to wait ad see what happens before doing the anniversary upgrade. if it works, I'll do it. If not I'll wait until things are fixed.

I'm expecting maybe 2-3 more preview builds before the code is frozen for the anniversary release. Quite a bit of the changes in the last few builds has been bugfixes so there is still a chance of a fix before code freeze but I wouldn't want to bet anything I was attached to.

[BetterRed]

Originally Posted by DNSB

I'm expecting maybe 2-3 more preview builds before the code is frozen for the anniversary release.

According to Yusuf Mehdi (Corporate Vice President, Windows and Devices Group) Windows Anniversary edition will be released in two weeks - Aug 2nd 2016.

I'm not familiar with MS's current practices. But when testing earlier versions of NT and derivatives in a corporate environment, two weeks out from release, the product would already be frozen and designated RTM (Ready for manufacture). And we would be finalising our 'early adopter' (IOW the quants) deployment processes

BR

[DNSB]

Originally Posted by BetterRed

According to Yusuf Mehdi (Corporate Vice President, Windows and Devices Group) Windows Anniversary edition will be released in two weeks - Aug 2nd 2016.

I'm not familiar with MS's current practices. But when testing earlier versions of NT and derivatives in a corporate environment, two weeks out from release, the product would already be frozen and designated RTM (Ready for manufacture). And we would be finalising our 'early adopter' (IOW the quants) deployment processes

BR

From what I was told—informally and so far off the record I'd need the Hubble to see it—the code freeze was going to be around July 25th. So a week from now more or less depending on time zone.

[DNSB]

For what it may be worth, Build 14393 was released today and no joy. Same issue.