Upgraded to Win 10. Calibre not detecting Kindle

[Kostas15]

Originally Posted by PeterT

The problem is that tablets /smartphone / cameras tend to implement a totally different protocol for communicating to the PC; either MTP or PTP (or both). eReaders and USB memory sticks implement the USB Mass Storage protocol.

What would be interesting is screen prints from Windows Device Manager showing both images with and without the eReader connected, and if at all possible drilling down into the specifics of the eReader device in device manager.

Also, a screen print from Windows Explorer when the eReader is attached to hopefully show Windows assigning it a drive letter.

I attach a print screen showing the device manager prior to connecting kindle and a screen shot after connecting kindle to comp
As you can see the win 10 is recognising the kindle but not the Calibre program.
The third screen shot shows the small windo opened by Win 10 to indicate it has detected the kindle and assigned a letter to it

[theducks]

Your second slide shows there is a problem still. (AKA Unknown device)

The drive letter message may be premature as the device did not fully install

[kovidgoyal]

Run the following in a command prompt and paste the output (with your kindle connected)

calibre-debug -c "import win32file, string, os; t = win32file.GetDriveType; print ' '.join(['%s:%s' % (d, t(d + ':' + os.sep)) for d in string.ascii_uppercase if t(d+':'+os.sep) > 1])"

[sandysot]

It seems that Apple has something called BkService Agent which seems to be a new copyright enhancement measure. It prevents accessing the kindle or pub files.I don't know whether windows has implemented "book protection" features but it seems probable.

[Kostas15]

Originally Posted by kovidgoyal

Run the following in a command prompt and paste the output (with your kindle connected)

calibre-debug -c "import win32file, string, os; t = win32file.GetDriveType; print ' '.join(['%s:%s' % (d, t(d + ':' + os.sep)) for d in string.ascii_uppercase if t(d+':'+os.sep) > 1])"

Hi kovidgoyal

I mentioned in a previous message that I am no wizz kid with comps, However
I have tried to carry out your instructions but when I press enter to run the string (I copied and pasted it in) all that seems to happen is it opens ready for more instruction.

Am I doing something wrong?

I attach a screen print of the CMD page

Many thanks

I will be pleased to supply any further info if I can. Explain simply though please

I have just followed the suggestions you have made in the sticky section about connection problems and ran the debug app.

The results are shown below

calibre 2.48 isfrozen: True is64bit: False
Windows-8-6.2.9200 Windows ('32bit', 'WindowsPE')
('Windows', '8', '6.2.9200')
Python 2.7.9
Windows: ('8', '6.2.9200', '', 'Multiprocessor Free')
USB devices on system:
[u'usb\\root_hub&vid10de&pid07fe&rev00a1',
u'usb\\vid_04f2&pid_0718&rev_0003',
u'usb\\vid_0ac8&pid_3450&rev_0900&mi_00',
u'usb\\vid_0bda&pid_0156&rev_5691',
u'usb\\root_hub20&vid10de&pid056a&rev00a1',
u'usb\\vid_0ac8&pid_3450&rev_0900',
u'usb\\vid_1949&pid_0004&rev_0100']
Traceback (most recent call last):
File "site-packages\calibre\devices\scanner.py", line 85, in __call__
DriveError: No removable drives found
Drives detected:

No disabled plugins
Looking for devices of type: MTP_DEVICE
List of WPD PNP ids:
[u'\\\\?\\swd#wpdbusenum#{88e5571f-a7f8-11e5-93cd-806e6f6e6963}#0000000000100000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
u'\\\\?\\swd#wpdbusenum#{88e55720-a7f8-11e5-93cd-806e6f6e6963}#000000012ff6d800#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
u'\\\\?\\swd#wpdbusenum#{3cce5b96-b61d-11e5-93d5-4061864c3dad}#0000000000002000#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
u'\\\\?\\swd#wpdbusenum#{88e5571e-a7f8-11e5-93cd-806e6f6e6963}#0000001870c2b400#{6ac27878-a6fa-4155-ba85-f98f491d4f33}']
No suitable MTP devices found

Looking for devices of type: SMART_DEVICE_APP
All IP addresses {'{395EE80C-06E9-4C43-8D3A-B4446B958AEB}': [{'addr': '192.168.0.2', 'broadcast': '192.168.0.255', 'netmask': '255.255.255.0'}], '{88E5571A-A7F8-11E5-93CD-806E6F6E6963}': [{'addr': '127.0.0.1', 'broadcast': '127.255.255.255', 'netmask': '255.0.0.0'}]}
No device is connected

Looking for devices...
u'usb\\vid_1949&pid_0004&rev_0100'

Devices possibly connected: None

[PeterT]

There actually IS output from the command on your screen print

C:3 D:3 E:3 G:3 H:5 I:3

and I think your Kindle is drive I: (at least it was in one of your screen shots).

So for some reason, Windows 10 does not seem to set the REMOVABLE attribute for your Kindle (and from other threads, Kobo's).

I think this should let Kovid find a work-around

[kovidgoyal]

To confirm, your Kindle drive is one of those listed? Presumably, I:?

In which case windows is reporting the drive as a fixed not a removable drive, which is the cause of the problem.

[PeterT]

And Kovod; if you see the thread Kobo not recognized anymore we see the same there; no drive's flagged with the Removable attribute.

So something (on SOME Windows 10 upgrades) is preventing drives being marked as Removable...

[kovidgoyal]

Here's a build of calibre with a workaround for the windows 10 bug, hopefully it will do the trick:

https://download.calibre-ebook.com/betas/

[theducks]

Kindle 4NT now works with USB Video adapter active.

Win 10:
2 steps forward,
1 step sideways

[JSWolf]

Kostas15, boot your Windows 10 into safe mode. Then try the regular version of Calibre with your Kindle plugged in and see if it works. If it works, something running on startup is the problem and you just have to stop it running.

[theducks]

Spoke to soon

Once the (K4) device charged, it went wild.
Disconnected, Detect, every 15 seconds.

What did M$ do?

Thankfully, I can do without the USB Vid.

[JSWolf]

Originally Posted by theducks

Spoke to soon

Once the (K4) device charged, it went wild.
Disconnected, Detect, every 15 seconds.

What did M$ do?

Thankfully, I can do without the USB Vid.

Maybe the USB Vid thing is the problem. Maybe they didn't work with MS to get it working under Windows 10.

[theducks]

Originally Posted by JSWolf

Maybe the USB Vid thing is the problem. Maybe they didn't work with MS to get it working under Windows 10.

I think it is a Windows Download supplied driver (that does not mean it is not buggy).

The original (W7) did not migrate properly (was yellow flagged n the device manager)

The only reason I twigged, was someone else mentioned ANOTHER (brand) also had issues.

[Kostas15]

Originally Posted by kovidgoyal

Here's a build of calibre with a workaround for the windows 10 bug, hopefully it will do the trick:

https://download.calibre-ebook.com/betas/

I downloaded and installed the top Beta 2.49 of the three there

Plugged in the kindle and opened Calibre
Just shows the existing books loaded into Calibre and did not recognise Kindle

I also started comp in safe mode and did same thing using the Beta Calibre with same result