Calibre won't recognize my Kindle anymore

[AnthAttack]

I've been using Calibre to put books on my Kindle Keyboard since the beginning of the year. Haven't used Calibre in a month or two, so today i tried to add some new books but when i plug my Kindle in the computer Calibre doesn't recognize it. Can anyone help me figure out what the problem is?

Any help is greatly appreciated!

Debug Device Detection :

Version: 0.8.58
USB devices on system:
[u'usb\\root_hub&vid8086&pid2444&rev0005',
u'usb\\root_hub&vid8086&pid2442&rev0005',
u'usb\\vid_1949&pid_0004&rev_0100',
u'usb\\vid_413c&pid_5233&rev_0001',
u'usb\\vid_413c&pid_5233&rev_0001&mi_00',
u'usb\\vid_413c&pid_5233&rev_0001&mi_01',
u'usb\\vid_413c&pid_5233&rev_0001&mi_02',
u'usb\\vid_413c&pid_5233&rev_0001&mi_03']
Unable to get free space for drive: A
(21, 'GetDiskFreeSpaceEx', 'The device is not ready.')
Unable to get free space for drive: F
(21, 'GetDiskFreeSpaceEx', 'The device is not ready.')
Drives detected:
Available plugins: ADAM ALEX ALURATEK_COLOR ANDROID ARCHOS7O AVANT AZBOOKA BAMBOOK
BLACKBERRY BOEYE_BDX BOEYE_BEX BOOQ BOOX COBY COOL_ER CYBOOK DBOOK E52
E71X EB511 EB600 EBK52 ECLICTO EDGE EEEREADER ELONEX ESLICK EX124G
FOLDER_DEVICE_FOR_CONFIG GEMEI GER2 HANLINV3 HANLINV5 ILIAD INVESBOOK
IPAPYRUS IREXDR1000 IREXDR800 IRIVER_STORY ITALICA ITUNES JETBOOK
JETBOOK_COLOR JETBOOK_MINI KINDLE KINDLE2 KINDLE_DX KINDLE_FIRE KOBO
LIBREAIR LUMIREAD MENTOR MIBUK MOOVYBOOK N516 N770 N810 NEWSMY
NEXTBOOK NOOK NOOK_COLOR NUUT2 ODYSSEY ORIZON PALMPRE PDNOVEL
PDNOVEL_KOBO PI2 PICO PLAYBOOK POCKETBOOK301 POCKETBOOK360
POCKETBOOK360P POCKETBOOK602 POCKETBOOK701 PRS505 PRST1 README S60
SHINEBOOK SNE SOVOS SPECTRA STASH SUNSTECH_EB700 SWEEX TECLAST_K3
THEBOOK TREKSTOR USER_DEFINED VELOCITYMICRO WEBOS WEXLER

Looking for devices...
u'usb\\vid_1949&pid_0004&rev_0100'

Devices possibly connected: None

[kovidgoyal]

According to that debug output your kindle is not being correctly initialized by windows. Try resetting it, or try a different usb cable/port.

[AnthAttack]

Wow, thanks a lot! A quick reset seems to have fixed the problem.