Issues Managing Kobo Glo HD on the Surface Pro 3

cable · 07-25-2016, 10:58 AM

Hi there,

I'm using a Kobo Glo HD, with essentially the latest firmware, which is as we speak 3.19.5761.

The device I'm using is a Surface Pro 3, which only has one USB port. I'm using Windows 10, with the upcoming Anniversary Update that is basically an RTM version. For people wondering, th OS build is 14393.0 and is a part of the Windows Insider program (Release Preview Build).

I did a complete factory reset on this device, only to get the Kobo Glo HD working, but it did not help.

The device itself gets recognized and shows up as F:\ but you cannot access it.

In the Device Manager it shows up under Disk drives and it's called Kobo eReader-3.19.576 USB Device.

I've been reading around these forums this and this, and tried several of these "solutions".

Tried to restart the Surface and the Kobo
Been looking into USB settings of the Surface but you cannot seem to tweak them
Made a complete factory reset of the Surface
Latest software updates on both the PC and the Kobo

I've tried to manage the Kobo on other computers with the current version of Windows 10, and the Kobo works just fine there and I can manage it through Calibre all I want.

Any idea what to do? I'd love to be able to manage the Kobo only on my Surface Pro 3.

By the looks of it now, it seems to be troublesome with the 'newer' version of Windows that comes out 2nd of August (in a week) - else it might be some setting of the USB port that I might not be aware of.

Thanks in advance,
cable

JSWolf · 07-25-2016, 11:09 AM

The problem seems to be with the Windows 10 beta. That's why I would never install such on a machine I wanted to use for real work unless it was to be able to dual-boot.

PeterT · 07-25-2016, 11:39 AM

Have you tried following the instructions in the calibre forums for a device not being detected? While its unlikely to help, seeing what USB data calibre detects would be interesting.

cable · 07-25-2016, 12:15 PM

Quote:

Originally Posted by JSWolf

The problem seems to be with the Windows 10 beta. That's why I would never install such on a machine I wanted to use for real work unless it was to be able to dual-boot.

It's weird, as this is supposedly the RTM version that will be rolling out to all computers within next week.

Quote:

Originally Posted by PeterT

Have you tried following the instructions in the calibre forums for a device not being detected? While its unlikely to help, seeing what USB data calibre detects would be interesting.

I'll look into it.

Spoiler:

Here's the debug information given:

Quote:

calibre 2.63 [64bit] embedded-python: 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: Kobo Utilities (2, 3, 2) && KoboTouchExtended (2, 7, 2)
USB devices on system:
(USBDevice(vendor_id=0x45e product_id=0x7be bcd=0x2152 devid=usb\vid_045e&pid_07be&rev_2152 devinst=2),
USBDevice(vendor_id=0x45e product_id=0x7bf bcd=0x2152 devid=usb\vid_045e&pid_07bf&rev_2152&mi_00 devinst=3),
USBDevice(vendor_id=0x1286 product_id=0x204b bcd=0x3201 devid=usb\vid_1286&pid_204b&rev_3201 devinst=4),
USBDevice(vendor_id=0x45e product_id=0x7be bcd=0x2152 devid=usb\vid_045e&pid_07be&rev_2152&mi_00 devinst=5),
USBDevice(vendor_id=0x2237 product_id=0x4223 bcd=0x110 devid=usb\vid_2237&pid_4223&rev_0110 devinst=6),
USBDevice(vendor_id=0x45e product_id=0x7bf bcd=0x2152 devid=usb\vid_045e&pid_07bf&rev_2152 devinst=7),
USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub30&vid8086&pid9c31&rev0004 devinst=8),
USBDevice(vendor_id=0x45e product_id=0x7dc bcd=0x207 devid=usb\vid_045e&pid_07dc&rev_0207 devinst=9))

No disabled plugins
Looking for devices of type: MTP_DEVICE
List of WPD PNP ids:
[u'\\\\?\\swd#wpdbusenum#_??_usbstor#disk&ven_kobo& prod_ereader-3.19.576&rev_0110#n437635907271&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}#{6ac27878-a6fa-4155-ba85-f98f491d4f33}']
No suitable MTP devices found

Looking for devices of type: SMART_DEVICE_APP
All IP addresses {'{7A678D26-954E-40E3-9B81-D90325EBFD4B}': [{'addr': '192.168.0.13', 'broadcast': '192.168.0.255', 'netmask': '255.255.255.0'}], '{D28C4111-241F-4D26-9E15-5567B3A9246C}': [{'addr': '169.254.140.24'}], '{581BED40-51C8-11E6-B798-806E6F6E6963}': [{'addr': '127.0.0.1', 'broadcast': '127.255.255.255', 'netmask': '255.0.0.0'}], '{7E0DC5BC-68F5-4228-813B-36CA571A27B2}': [{'addr': '169.254.115.140'}]}
No device is connected

Looking for devices...
USBDevice(vendor_id=0x2237 product_id=0x4223 bcd=0x110 devid=usb\vid_2237&pid_4223&rev_0110 devinst=6)
Detected possible device KOBOTOUCH
USBDevice(vendor_id=0x2237 product_id=0x4223 bcd=0x110 devid=usb\vid_2237&pid_4223&rev_0110 devinst=6)
Detected possible device KOBOTOUCHEXTENDED

Devices possibly connected: KoboTouch, KoboTouchExtended,
Trying to open KoboTouch ... Storage number map:
{(7L, 0L): [(3L, 'C')], (7L, 1L): [(1L, 'F')]}
Storage number for USBSTOR\DISK&VEN_KOBO&PROD_EREADER-3.19.576&REV_0110\N437635907271&0: StorageDeviceNumber(type=7L, number=1L, partition_number=0L)
Failed to get readonly status for drive: F with error: [Error 87] The parameter is incorrect.
Drive letters for USBDevice(vendor_id=0x2237 product_id=0x4223 bcd=0x110 devid=usb\vid_2237&pid_4223&rev_0110 devinst=6)
{u'drive_letters': ['F'],
u'pnp_id_map': {'F': u'\\\\?\\usbstor#disk&ven_kobo&prod_ereader-3.19.576&rev_0110#n437635907271&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}'},
u'readonly_drives': set([]),
u'sort_map': {'F': (1L, 1L)}}
Unable to get free space for drive: F
(87, 'GetDiskFreeSpaceEx', 'The parameter is incorrect.')
Ignoring the drive F because failed to get free space for it
failed
Trying to open KoboTouchExtended ... Storage number map:
{(7L, 0L): [(3L, 'C')], (7L, 1L): [(1L, 'F')]}
Storage number for USBSTOR\DISK&VEN_KOBO&PROD_EREADER-3.19.576&REV_0110\N437635907271&0: StorageDeviceNumber(type=7L, number=1L, partition_number=0L)
Failed to get readonly status for drive: F with error: [Error 87] The parameter is incorrect.
Drive letters for USBDevice(vendor_id=0x2237 product_id=0x4223 bcd=0x110 devid=usb\vid_2237&pid_4223&rev_0110 devinst=6)
{u'drive_letters': ['F'],
u'pnp_id_map': {'F': u'\\\\?\\usbstor#disk&ven_kobo&prod_ereader-3.19.576&rev_0110#n437635907271&0#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}'},
u'readonly_drives': set([]),
u'sort_map': {'F': (1L, 1L)}}
Unable to get free space for drive: F
(87, 'GetDiskFreeSpaceEx', 'The parameter is incorrect.')
Ignoring the drive F because failed to get free space for it
failed
Opening of the following devices failed
Driver:KoboTouch, Options - format_map: ['kepub', 'epub', 'pdf', 'txt', 'cbz', 'cbr'], use_subdirs: True, read_metadata: True, use_author_sort: False, save_template: {author_sort}/{title} - {authors}, extra_customization: [], manage_collections: True, collections_columns: , create_collections: False, delete_empty_collections: False, upload_covers: False, keep_cover_aspect: False, upload_grayscale: False, show_archived_books: False, show_previews: False, show_recommendations: False, update_series: True, update_device_metadata: True, modify_css: False, support_newer_firmware: False, debugging_title: , driver_version:
Traceback (most recent call last):
File "site-packages\calibre\devices\__init__.py", line 154, in debug
File "site-packages\calibre\devices\usbms\device.py", line 867, in open
File "site-packages\calibre\devices\usbms\device.py", line 277, in open_windows
DeviceError: Unable to detect any disk drives for the device: Kobo Touch/Glo/Mini/Aura HD/Aura H2O/Glo HD/Touch 2. Try rebooting

Driver:KoboTouchExtended, Options - format_map: ['kepub', 'epub', 'cbr', 'cbz', 'pdf', 'txt'], use_subdirs: True, read_metadata: True, use_author_sort: False, save_template: {author_sort}/{title} - {authors}, extra_customization: [], manage_collections: True, collections_columns: , create_collections: False, delete_empty_collections: False, upload_covers: False, keep_cover_aspect: False, upload_grayscale: False, show_archived_books: False, show_previews: False, show_recommendations: False, update_series: True, update_device_metadata: True, modify_css: False, support_newer_firmware: False, debugging_title: , driver_version: , extra_features: True, upload_encumbered: False, skip_failed: False, hyphenate: False, replace_lang: False, smarten_punctuation: False, clean_markup: False, full_page_numbers: False, disable_hyphenation: False, file_copy_dir:
Traceback (most recent call last):
File "site-packages\calibre\devices\__init__.py", line 154, in debug
File "site-packages\calibre\devices\usbms\device.py", line 867, in open
File "site-packages\calibre\devices\usbms\device.py", line 277, in open_windows
DeviceError: Unable to detect any disk drives for the device: Kobo Touch/Glo/Mini/Aura HD/Aura. Try rebooting

cable · 07-25-2016, 12:45 PM

Quote:

Originally Posted by PeterT

Have you tried following the instructions in the calibre forums for a device not being detected? While its unlikely to help, seeing what USB data calibre detects would be interesting.

Also worth noting is that I can manage the Kobo on other computers (accessing files, seeing how much storage is left, etc) through Windows Explorer.

Which I cannot do on this one (it's however shown in Windows Explorer, but no storage information is visible, just a plain drive).

PeterT · 07-25-2016, 01:06 PM

Are those other computers also on a preview build of Windows 10?

cable · 07-25-2016, 02:50 PM

Quote:

Originally Posted by PeterT

Are those other computers also on a preview build of Windows 10?

They're not. However, I might consider throwing on the Release Preview on one of them. I'd bet my money on it that it would work still.

I technically think that it has to do something with the USB port itself, some sort of setting that prevents it to handle the Kobo properly, like it was in one of those threads I mentioned above (USB fast setting or something like that).

Edit: Read an interesting fact here that the USB port on the SP3 is underpowered, so there's that.

PeterT · 07-25-2016, 07:04 PM

People are having the same issue with the preview build on Intel based systems.

davidfor · 07-25-2016, 08:01 PM

Quote:

Originally Posted by cable

They're not. However, I might consider throwing on the Release Preview on one of them. I'd bet my money on it that it would work still.

I'm willing to take that bet.

Quote:

I technically think that it has to do something with the USB port itself, some sort of setting that prevents it to handle the Kobo properly, like it was in one of those threads I mentioned above (USB fast setting or something like that).

Edit: Read an interesting fact here that the USB port on the SP3 is underpowered, so there's that.

I don't remember seeing a report of Kobo devices working with any of the different Surface device, so I wouldn't be surprised if they don't work. But, based on the number of reports of Kob devices not working with the current Win10 prerelease versions, that is where I would point the blame. MS have changed something about how they mount USB devices. The Kobo devices are suffering.

robko · 07-25-2016, 08:58 PM

FWIW: Mounts fine on my Surface 3 (NOT Surface Pro) running currently released Win 10 (not preview).

There are enough reports of it not mounting with the latest Win 10 preview build that it's hard to imagine that there isn't something related to that causing the issue. Whether that is dependent on hardware configuration as well as that build or not I can't say. Don't think we've seen any reports of anyone with that build saying it works on their computer, so my guess is something between the new build and Kobo hardware or firmware that don't like each other.

DNSB · 07-25-2016, 10:52 PM

Quote:

Originally Posted by cable

Hi there,

I'm using a Kobo Glo HD, with essentially the latest firmware, which is as we speak 3.19.5761.

The device I'm using is a Surface Pro 3, which only has one USB port. I'm using Windows 10, with the upcoming Anniversary Update that is basically an RTM version. For people wondering, th OS build is 14393.0 and is a part of the Windows Insider program (Release Preview Build).

I did a complete factory reset on this device, only to get the Kobo Glo HD working, but it did not help.

The device itself gets recognized and shows up as F:\ but you cannot access it.

In the Device Manager it shows up under Disk drives and it's called Kobo eReader-3.19.576 USB Device.

I've been reading around these forums this and this, and tried several of these "solutions".

Tried to restart the Surface and the Kobo
Been looking into USB settings of the Surface but you cannot seem to tweak them
Made a complete factory reset of the Surface
Latest software updates on both the PC and the Kobo

I've tried to manage the Kobo on other computers with the current version of Windows 10, and the Kobo works just fine there and I can manage it through Calibre all I want.

Any idea what to do? I'd love to be able to manage the Kobo only on my Surface Pro 3.

By the looks of it now, it seems to be troublesome with the 'newer' version of Windows that comes out 2nd of August (in a week) - else it might be some setting of the USB port that I might not be aware of.

Thanks in advance,
cable

That is a known issue with the last 8 or so Preview Builds. The two cumulative updates to 14393 that Microsoft has rolled out have not changed the issues that I and others are seeing. It's been reported on VMWare and HyperV VMs as well as Intel and AMD based physical computers.

Welcome to life on the bleeding edge.

DNSB · 07-25-2016, 11:12 PM

Quote:

Originally Posted by cable

Also worth noting is that I can manage the Kobo on other computers (accessing files, seeing how much storage is left, etc) through Windows Explorer.

Which I cannot do on this one (it's however shown in Windows Explorer, but no storage information is visible, just a plain drive).

I can manage my Kobo on my laptop from Windows 10 1511, Fedora and Ubuntu Linux on the physical side and various VMs running under VMWare Workstation 12. The only VM that has issues is the Windows 10 Preview VM. Windows XP, 7, 8.1, various flavours of Linux and OSX 10.11.5 all see both drives. Well, the OSX VM does need to be tweaked to see the .whatever folders.

If you go into Disk Management with the Windows Preview build, the internal storage on a Kobo will show as unallocated space.

JSWolf · 07-26-2016, 06:27 AM

I have a Surface 2 Pro. It's running the release of Win 10 Pro 64-bit. I have no problem with my H2O being recognized.

However, when the anniversary release of Windows 10 is released, I'm going to wait until there are reports of Kobo Readers working with it before I install.

anacreon · 07-26-2016, 08:42 AM

Quote:

Originally Posted by cable

Edit: Read an interesting fact here that the USB port on the SP3 is underpowered, so there's that.

I had a similar problem when I bought the Surface Book, solved when I bought a dock. The Microsoft help desk explained it was because the Surface Book has only 36W while the Surface dock has 65W. But I can't see why that would impact a new Windows version.

cable · 08-04-2016, 09:45 AM

I'm slightly disappointed as the Anniversary Update is officially released now and it still doesn't work.

I updated my SP3 to the latest official version.

Version: 1607
OS Build: 14393.10

I also uninstalled the Kobo eReader from the Device Manager, re-plugged it, still the same issue. I looked for the latest drivers as well with no success.

Has anyone successfully managed to get it to work on the latest Windows update?

07-25-2016, 10:58 AM	#1
cable Junior Member Posts: 5 Karma: 10 Join Date: Jul 2016 Device: Kobo Glo HD	Issues Managing Kobo Glo HD on the Surface Pro 3 Hi there, I'm using a Kobo Glo HD, with essentially the latest firmware, which is as we speak 3.19.5761. The device I'm using is a Surface Pro 3, which only has one USB port. I'm using Windows 10, with the upcoming Anniversary Update that is basically an RTM version. For people wondering, th OS build is 14393.0 and is a part of the Windows Insider program (Release Preview Build). I did a complete factory reset on this device, only to get the Kobo Glo HD working, but it did not help. The device itself gets recognized and shows up as F:\ but you cannot access it. In the Device Manager it shows up under Disk drives and it's called Kobo eReader-3.19.576 USB Device. I've been reading around these forums this and this, and tried several of these "solutions". Tried to restart the Surface and the Kobo Been looking into USB settings of the Surface but you cannot seem to tweak them Made a complete factory reset of the Surface Latest software updates on both the PC and the Kobo I've tried to manage the Kobo on other computers with the current version of Windows 10, and the Kobo works just fine there and I can manage it through Calibre all I want. Any idea what to do? I'd love to be able to manage the Kobo only on my Surface Pro 3. By the looks of it now, it seems to be troublesome with the 'newer' version of Windows that comes out 2nd of August (in a week) - else it might be some setting of the USB port that I might not be aware of. Thanks in advance, cable

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Surface Pro 3 and Kobo App with BlueStacks	k9reeder	Windows Devices	0	05-31-2015 08:44 AM
Kobo Glo - syncing issues!!	huynheri	Kobo Reader	3	03-04-2014 09:20 PM
Glo Kobo Glo Issues With Mac	Joseph R	Kobo Reader	16	05-14-2013 09:53 PM
Kobo Glo connection issues	feenix1363	Devices	21	11-01-2012 12:08 AM
Glo Kobo Glo Mac issues	phonetichalo	Kobo Reader	24	10-12-2012 03:24 AM

07-25-2016, 11:09 AM	#2
JSWolf Resident Curmudgeon Posts: 79,506 Karma: 145863177 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	The problem seems to be with the Windows 10 beta. That's why I would never install such on a machine I wanted to use for real work unless it was to be able to dual-boot.

07-25-2016, 11:39 AM	#3
PeterT Grand Sorcerer Posts: 13,403 Karma: 78880114 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	Have you tried following the instructions in the calibre forums for a device not being detected? While its unlikely to help, seeing what USB data calibre detects would be interesting.

07-25-2016, 01:06 PM	#6
PeterT Grand Sorcerer Posts: 13,403 Karma: 78880114 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	Are those other computers also on a preview build of Windows 10?

07-25-2016, 07:04 PM	#8
PeterT Grand Sorcerer Posts: 13,403 Karma: 78880114 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	People are having the same issue with the preview build on Intel based systems.

07-25-2016, 08:58 PM	#10
robko Wizard Posts: 2,454 Karma: 5469320 Join Date: Jul 2010 Device: Kobo	FWIW: Mounts fine on my Surface 3 (NOT Surface Pro) running currently released Win 10 (not preview). There are enough reports of it not mounting with the latest Win 10 preview build that it's hard to imagine that there isn't something related to that causing the issue. Whether that is dependent on hardware configuration as well as that build or not I can't say. Don't think we've seen any reports of anyone with that build saying it works on their computer, so my guess is something between the new build and Kobo hardware or firmware that don't like each other.

07-26-2016, 06:27 AM	#13
JSWolf Resident Curmudgeon Posts: 79,506 Karma: 145863177 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	I have a Surface 2 Pro. It's running the release of Win 10 Pro 64-bit. I have no problem with my H2O being recognized. However, when the anniversary release of Windows 10 is released, I'm going to wait until there are reports of Kobo Readers working with it before I install.

08-04-2016, 09:45 AM	#15
cable Junior Member Posts: 5 Karma: 10 Join Date: Jul 2016 Device: Kobo Glo HD	I'm slightly disappointed as the Anniversary Update is officially released now and it still doesn't work. I updated my SP3 to the latest official version. Version: 1607 OS Build: 14393.10 I also uninstalled the Kobo eReader from the Device Manager, re-plugged it, still the same issue. I looked for the latest drivers as well with no success. Has anyone successfully managed to get it to work on the latest Windows update?

Advert

Advert