Kobo not seen after windows 10 upgrade

[davidfor]

Originally Posted by mikeywilliams25

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!

Yes, delete the drivers. USBDeview will probably be enough. But, there was some discussion on this in the Kobo forum with some more suggestions. See https://www.mobileread.com/forums/sho...d.php?t=263579.

[pasgener]

Originally Posted by davidfor

Yes, delete the drivers. USBDeview will probably be enough. But, there was some discussion on this in the Kobo forum with some more suggestions. See https://www.mobileread.com/forums/sho...d.php?t=263579.

This is not a USB driver problem, rather it is a problem with how the internal memory on the kobo is formatted. Windows 10 (especially anniversary edition) cannot reliable read the internal memory, so fails to "migrate" or recognize the device. For some reason Windows 7 can read the internal memory just fine. This problem seemed to occur after a recent update to the kobo internal software.

Connecting the device to a Windows 7 PC, then coping all the files off the kobo (as a backup), then reformating the internal drive of the kobo as a new FAT32 drive, then copying all the files back onto the device fixes the problem (Windows 10 can then read the device afterwards, and can sync with it).

Any hard reset (or factory reset) reformats the internal drive, and so recreates the problem. So make sure that you update your kobo first (wirelessly or connected to a Windows 7 PC), then reformat and replace all you data.

I've done this successfully now with a Kobo Glo HD and Kobo Touch (which I had thought was dead!)

Kobo really needs to fix this problem moving forward -- having a "corrupt" FAT32 partition on their devices is ridiculous.

[davidfor]

Originally Posted by pasgener

This is not a USB driver problem, rather it is a problem with how the internal memory on the kobo is formatted. Windows 10 (especially anniversary edition) cannot reliable read the internal memory, so fails to "migrate" or recognize the device. For some reason Windows 7 can read the internal memory just fine. This problem seemed to occur after a recent update to the kobo internal software.

Connecting the device to a Windows 7 PC, then coping all the files off the kobo (as a backup), then reformating the internal drive of the kobo as a new FAT32 drive, then copying all the files back onto the device fixes the problem (Windows 10 can then read the device afterwards, and can sync with it).

Any hard reset (or factory reset) reformats the internal drive, and so recreates the problem. So make sure that you update your kobo first (wirelessly or connected to a Windows 7 PC), then reformat and replace all you data.

I've done this successfully now with a Kobo Glo HD and Kobo Touch (which I had thought was dead!)

Kobo really needs to fix this problem moving forward -- having a "corrupt" FAT32 partition on their devices is ridiculous.

Yes, you are right, my solution didn't work. But, did you read the thread? Or look at the date? If you had, you would have seen that the symptoms were different and that this was from a YEAR ago when Windows 10 was first released. At that time, MS change the way devices had to be detected, and hence calibre had to do some changes.

And of course, someone has to fix this the recent problem. But, this is a change that MS made, so why aren't they expected to fix it? Kobo might be wrong in what they are doing, but they have been doing this for at least five years, so why is it suddenly a problem? Kobo will probably do something, but that an only be done in new firmware and means anyone who doesn't want to update for other reasons is stuck.

[pasgener]

Originally Posted by davidfor

Yes, you are right, my solution didn't work. But, did you read the thread? Or look at the date? If you had, you would have seen that the symptoms were different and that this was from a YEAR ago when Windows 10 was first released. At that time, MS change the way devices had to be detected, and hence calibre had to do some changes.

And of course, someone has to fix this the recent problem. But, this is a change that MS made, so why aren't they expected to fix it? Kobo might be wrong in what they are doing, but they have been doing this for at least five years, so why is it suddenly a problem? Kobo will probably do something, but that an only be done in new firmware and means anyone who doesn't want to update for other reasons is stuck.

Agree -- plenty of blame to go around! Problem is that the kobo support line does not seem to be aware of this, and doesn't give any advice on how to fix the inability to sync with Windows 10 PCs.

[JSWolf]

This thread is NOT about the Win 10 Anniversary Update problem with Kobo Readers.

If you are running Win 10AU, go see https://www.mobileread.com/forums/sho...d.php?t=276349

[davidfor]

Originally Posted by pasgener

Agree -- plenty of blame to go around! Problem is that the kobo support line does not seem to be aware of this, and doesn't give any advice on how to fix the inability to sync with Windows 10 PCs.

There are reports that the Kobo support line do know what is going on. But, with the current problem, there is no good solution. The workarounds discussed in the main thread on this are not something that you can expect most users would be comfortable doing. I don't think they are something a support line can recommend.