[Tranquility]

Hello everyone,

Because I love to mess with my phone, install new custom ROMs and just do fun stuff in general I come across a problem that's quite common all the time. The ADB function not working while fastboot does work.
Users who have Linux most of the time don't have this issue as its supported a bit better (surprise surprise ;p)

Using the proper drivers and/or sync managers help in most cases for the ADB function to work. However, this isn't always the case.
I'll briefly go through the steps I have performed to fix my issue with my Android 4.4.4 phone (performed on Windows 8.1) and hopefully this will be helpful to the other geeks around here.
Apologies for the 'image heavy' additions, these were added to make the steps even more clear (should I have add red markers too?)
Edit: Added spoiler tags instead.

1] attach your phone with a USB-cable to your computer;
2] open device manager (Windows + Pause button brings you to system -> Device Manager in the left pane)
Spoiler (Click to View)

3] under "Other Devices" or "Android Devices" you should find your phone
Spoiler (Click to View)

4] right click & "Update Driver Software..."

5] click/navigate to "Browse your computer for driver software"
Spoiler (Click to View)

6] click/navigate to "Let me pick from a list of device drivers on my computer" > A list will appear
Spoiler (Click to View)

7] select the right driver for your phone's brand
Spoiler (Click to View)

8] or select the default Android Composite ADB interface
Spoiler (Click to View)

9] You should be able to use ADB now!
Spoiler (Click to View)

Comments and feedback are welcome. This can be anything to improve the 'guide' and ease of readability for the users.

[newgonhowzter]

Awesome, thanks for this. I was having this exact problem. You would think newer Android OS + Newer PC OS = More reliability.

Another problem I had even after correct drivers were installed was getting my PC to request ADB authorization. I found connecting my phone and opening eclipse was the only way to force the request. "ADB devices" or any other commands did not seem to work, they would be denied. Anyways, thought I would toss that in if someone ends up in the same boat.

[Tranquility]

Awesome, thanks for this. I was having this exact problem. You would think newer Android OS + Newer PC OS = More reliability.

Another problem I had even after correct drivers were installed was getting my PC to request ADB authorization. I found connecting my phone and opening eclipse was the only way to force the request. "ADB devices" or any other commands did not seem to work, they would be denied. Anyways, thought I would toss that in if someone ends up in the same boat.

Thanks for the info! Fortunately I didn't have this issue yet and apparently not a lot of people around here are familiar with ADB or got it working out of the box.