Thread: Kobo not seen after windows 10 upgrade
View Single Post
Old 08-12-2016, 09:34 PM   #18
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by pasgener View Post
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.
davidfor is offline   Reply With Quote