Kobo not seen after windows 10 upgrade

mikeywilliams25 · 08-06-2015, 01:13 PM

After upgrading to Windows 10 Calibre does not recognize my Kobo Aura h2o as before. It is seen by the computer as a drive and I can connect to it using calibre connect to folder. But it is then not seen by the Extended Touch plugin.

Here is the debug log:

calibre Debug log
calibre 2.33 [64bit] isfrozen: True is64bit: True
Windows-8-6.2.9200 Windows ('64bit', 'WindowsPE')
('Windows', '8', '6.2.9200')
Python 2.7.9
Windows: ('8', '6.2.9200', '', 'Multiprocessor Free')
Successfully initialized third party plugins: Reading List && Goodreads && Kobo Utilities && KoboTouchExtended
Starting up...
Traceback (most recent call last):
File "site-packages\calibre\gui2\ui.py", line 151, in __init__
File "site-packages\calibre\gui2\ui.py", line 165, in init_iaction
File "site-packages\calibre\customize\__init__.py", line 582, in load_actual_plugin
File "importlib\__init__.py", line 37, in import_module
File "site-packages\calibre\customize\zipplugin.py", line 179, in load_module
File "calibre_plugins.reading_list.action", line 14, in <module>
ImportError: No module named PyQt4.Qt
DEBUG: 0.0 KoboUtilites::action.py - loading translations
DEBUG: 0.0 KoboUtilites::dialogs.py - loading translations
DEBUG: 0.0 KoboUtilites::action.py - loading translations
DEBUG: 1.7 No Kobo Touch, Glo or Mini appears to be connected
DEBUG: 1.7 rebuild_menus - self.supports_ratings=None
Started up in 22.15 seconds with 2323 books

theducks · 08-06-2015, 01:32 PM

QT4 is old. Calibre switched to QT5 (internals) quite a while ago.

Is that with the latest Kobo PI ?

mikeywilliams25 · 08-06-2015, 01:53 PM

Quote:

Originally Posted by theducks

QT4 is old. Calibre switched to QT5 (internals) quite a while ago.

Is that with the latest Kobo PI ?

Sorry I'm a bit dense.
What is Kobo Pl?

Calibre on Windows 7 before upgrading worked fine as it still does on my dual booted windows 7.

eschwartz · 08-06-2015, 02:22 PM

The latest Kobo plugin.

Make sure all your plugins are up to date, you should not be getting an error message that says it tried to use Qt4.

mikeywilliams25 · 08-06-2015, 05:29 PM

Quote:

Originally Posted by eschwartz

The latest Kobo plugin.

Make sure all your plugins are up to date, you should not be getting an error message that says it tried to use Qt4.

I checked and indeed they are up to date.

Uninstalled and then reinstalled Calibre.

Still not seeing my Kobo - here is the new debug:
calibre Debug log
calibre 2.33 [64bit] isfrozen: True is64bit: True
Windows-8-6.2.9200 Windows ('64bit', 'WindowsPE')
('Windows', '8', '6.2.9200')
Python 2.7.9
Windows: ('8', '6.2.9200', '', 'Multiprocessor Free')
Successfully initialized third party plugins: KoboTouchExtended && Reading List && Kobo Utilities && Goodreads
Starting up...
DEBUG: 0.0 KoboUtilites::action.py - loading translations
DEBUG: 0.0 KoboUtilites::dialogs.py - loading translations
DEBUG: 0.0 KoboUtilites::action.py - loading translations
DEBUG: 1.6 No Kobo Touch, Glo or Mini appears to be connected
DEBUG: 1.6 rebuild_menus - self.supports_ratings=None
Started up in 4.08 seconds with 2323 books

------------------------------------------
Although it says No Kobo Touch etc is connected my Aura H2o certainly is and shows up in the Windows10 file explorer.

PeterT · 08-06-2015, 05:43 PM

Please follow the steps here: My device is not detected by calibre

Do (to simplify things) start calibre before attaching your device.

davidfor · 08-06-2015, 07:52 PM

Quote:

Originally Posted by theducks

Is that with the latest Kobo PI ?

The message "No Kobo Touch, Glo or Mini appears to be connected" is from the Kobo Utilities plugin, not the driver. I should either add the plugin name like the previous lines, or remove it. Probably the latter as I think at the time this is printed it is a long time before calibre starts looking for devices. Same goes for the next line, but it shows up at other times as well.

mikeywilliams25: As well as the instructions PeterT pointed to, disable the KoboTouchExtended driver and enable the KoboTouch driver. That shouldn't make a difference, but it is something that should be tested.

mikeywilliams25 · 08-07-2015, 03:24 AM

First a big thankyou for all the help and advice so kindly offered.

I had indeed followed the procedures as recommended by PeterT which is why I had the debug logs.

I also tried davidfor's suggestion to disable the KoboTouchExtended driver and enable the KoboTouch driver. It did indeed make no difference. I tried connecting before Calibre ran and after. I also updated Calibre to latest 2.34.0.

Just as a double check I booted into my old Windows7 and everything is working as it should. The setup/plugins etc seem to be identical with my Windows10 setup.

Jolly strange.

davidfor · 08-07-2015, 03:45 AM

Quote:

Originally Posted by mikeywilliams25

I had indeed followed the procedures as recommended by PeterT which is why I had the debug logs.

In that case, can you post the results from the last step? The log you posted is from starting calibre in debug mode. The device detection log will show what calibre is seeing in the way of devices.

mikeywilliams25 · 08-07-2015, 04:15 AM

Quote:

Originally Posted by davidfor

In that case, can you post the results from the last step? The log you posted is from starting calibre in debug mode. The device detection log will show what calibre is seeing in the way of devices.

yer tiz:

Spoiler:

davidfor · 08-07-2015, 07:10 AM

Quote:

Originally Posted by mikeywilliams25

Code:

 u'usb\\vid_2237&pid_4213&rev_0110',
 u'usb\\vid_1f4d&pid_a803&rev_0100&mi_00']
Traceback (most recent call last):
  File "site-packages\calibre\devices\scanner.py", line 85, in __call__
DriveError: No removable drives found
Drives detected:

The first line is the identifiers of the Kobo Aura H2O. But, the later line says there are no removable drives. It looks like Win10 is mounting the device in a different way. Has a drive letter been assigned? Or has is some sort of USB turbo function enabled?

mikeywilliams25 · 08-07-2015, 10:20 AM

Quote:

Originally Posted by davidfor

The first line is the identifiers of the Kobo Aura H2O. But, the later line says there are no removable drives. It looks like Win10 is mounting the device in a different way. Has a drive letter been assigned? Or has is some sort of USB turbo function enabled?

The plot thickens:
It has been assigned a drive letter so that I can view the files on the Kobo.
But looking at the drive properties/hardware/events it says the following:

Device USBSTOR\Disk&Ven_Kobo&Prod_eReader-3.15.0&Rev_0110\N250544005987&0 could not be migrated.

Last Device Instance Id: USBSTOR\DISK&VEN_&PROD_ANDROID_ADAPTER&REV_0100\C8 D15E2B8AC5&0
Class Guid: {4D36E967-E325-11CE-BFC1-08002BE10318}
Location Path:
Migration Rank: 0xF000FC001001F120
Present: false
Status: 0xC0000719

----------------------------------------------
Presumable the migrating refers to when I migrated for Windows 7 to 10 a few days ago. What the rest of it means, and why it says it couldnt be migrated when it assigns a drive letter and I can browse and add/delete files.

So maybe I have to wait until Windows10 irons out another bug.
I tried changing the drive letter but that made no difference.
Maybe I should try deleting Kobo drivers and letting them reinstal. Who knows!

theducks · 08-07-2015, 03:07 PM

Quote:

Originally Posted by mikeywilliams25

.

So maybe I have to wait until Windows10 irons out another bug.
I tried changing the drive letter but that made no difference.
Maybe I should try deleting Kobo drivers and letting them reinstal. Who knows!

Connect to folder? (in the meantime). You will lose special Kobo PI features

mikeywilliams25 · 08-07-2015, 03:27 PM

Quote:

Originally Posted by theducks

Connect to folder? (in the meantime). You will lose special Kobo PI features

Connect to folder does work - but I want to be able to send books to the Kobo as kepubs (converted on the fly) and for that I think I need the Kobo Pl features.

eschwartz · 08-07-2015, 03:59 PM

I think there is a KEPUB output plugin you can use to convert to KEPUB and store them in calibre.

08-06-2015, 01:13 PM	#1
mikeywilliams25 Enthusiast Posts: 48 Karma: 10 Join Date: Aug 2008 Location: London Device: Kobo GloHD and Aura h2O	Kobo not seen after windows 10 upgrade After upgrading to Windows 10 Calibre does not recognize my Kobo Aura h2o as before. It is seen by the computer as a drive and I can connect to it using calibre connect to folder. But it is then not seen by the Extended Touch plugin. Here is the debug log: calibre Debug log calibre 2.33 [64bit] isfrozen: True is64bit: True Windows-8-6.2.9200 Windows ('64bit', 'WindowsPE') ('Windows', '8', '6.2.9200') Python 2.7.9 Windows: ('8', '6.2.9200', '', 'Multiprocessor Free') Successfully initialized third party plugins: Reading List && Goodreads && Kobo Utilities && KoboTouchExtended Starting up... Traceback (most recent call last): File "site-packages\calibre\gui2\ui.py", line 151, in __init__ File "site-packages\calibre\gui2\ui.py", line 165, in init_iaction File "site-packages\calibre\customize\__init__.py", line 582, in load_actual_plugin File "importlib\__init__.py", line 37, in import_module File "site-packages\calibre\customize\zipplugin.py", line 179, in load_module File "calibre_plugins.reading_list.action", line 14, in <module> ImportError: No module named PyQt4.Qt DEBUG: 0.0 KoboUtilites::action.py - loading translations DEBUG: 0.0 KoboUtilites::dialogs.py - loading translations DEBUG: 0.0 KoboUtilites::action.py - loading translations DEBUG: 1.7 No Kobo Touch, Glo or Mini appears to be connected DEBUG: 1.7 rebuild_menus - self.supports_ratings=None Started up in 22.15 seconds with 2323 books

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Windows 10 - free upgrade to those with PC using Windows 7 or 8	Lynx-lynx	News	2334	03-22-2021 10:35 PM
Windows 7 upgrade to 2.16 issue	Phssthpok	Devices	6	01-29-2015 03:55 PM
Why can’t I complete the Kobo Touch firmware upgrade or Desktop upgrade?	DarrellAtKobo	Kobo Reader	31	08-31-2012 10:45 PM
Did your Upgrade work ? Windows Versions	PeterT	Kobo Reader	18	07-03-2010 08:19 PM

08-06-2015, 01:32 PM	#2
theducks Well trained by Cats Posts: 30,928 Karma: 60358908 Join Date: Aug 2009 Location: The Central Coast of California Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A	QT4 is old. Calibre switched to QT5 (internals) quite a while ago. Is that with the latest Kobo PI ?

08-06-2015, 02:22 PM	#4
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	The latest Kobo plugin. Make sure all your plugins are up to date, you should not be getting an error message that says it tried to use Qt4.

08-06-2015, 05:43 PM	#6
PeterT Grand Sorcerer Posts: 13,354 Karma: 78877538 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	Please follow the steps here: My device is not detected by calibre Do (to simplify things) start calibre before attaching your device.

08-07-2015, 03:24 AM	#8
mikeywilliams25 Enthusiast Posts: 48 Karma: 10 Join Date: Aug 2008 Location: London Device: Kobo GloHD and Aura h2O	First a big thankyou for all the help and advice so kindly offered. I had indeed followed the procedures as recommended by PeterT which is why I had the debug logs. I also tried davidfor's suggestion to disable the KoboTouchExtended driver and enable the KoboTouch driver. It did indeed make no difference. I tried connecting before Calibre ran and after. I also updated Calibre to latest 2.34.0. Just as a double check I booted into my old Windows7 and everything is working as it should. The setup/plugins etc seem to be identical with my Windows10 setup. Jolly strange.

08-07-2015, 03:59 PM	#15
eschwartz Ex-Helpdesk Junkie Posts: 19,421 Karma: 85400180 Join Date: Nov 2012 Location: The Beaten Path, USA, Roundworld, This Side of Infinity Device: Kindle Touch fw5.3.7 (Wifi only)	I think there is a KEPUB output plugin you can use to convert to KEPUB and store them in calibre.

Advert

Advert