[Alan_S]

Originally Posted by tshering

I would guess this is a coincidence. Maybe your usb cord has a loose connection or something like this and works only if in a certain position.

No, I'm sure it's not coincidence.

As you can see, I tested it enough to be sure that file Fsck0000.rec makes difference in problematic USB port. I tried and tried with same result.

Also, talking about USB cable, other devices on USB port that has problems work just fine, I'm sure in it.

So it isn't cable, file Fsck0000.rec makes real difference.

Originally Posted by JSWolf

If you run Windows, try running Windows in safe mode. Then plug the HD into the working USB port and try to eject it. If it does eject, then you know it's some piece of software you run when the computer starts up.

Actually, it's H2O, not HD, but, I resolved problem with ejecting device by following advice from Kobo. Deinstalling and installing Kobo desktop software again solved that problem.

Now I only have problem with one port sometimes malfunctioning (strange thing is that placing Fsck0000.rec file in device's root enables event problematic USB port to work flawlessly)

Originally Posted by yayo

I used to have a problem with my KOBO Aura (now I have a H2O) where my PC would recognize the reader's internal memory but wouldn't properly detect a microSD card inserted into the reader's external memory slot.

Thanks, but at the moment I don't have SD card at all in device and also there's no freezing of device nor notebook. I just get report that USB device malfunctioned.

This suggests that something is wrong with device. As I wrote, if I place Fsck0000.rec file in root of device, than everything is ok. Or, if I use different USB port, then also everything works.