[Nexus 7 Android Development] TToTT:
Not quite sure that I can agree with your statement of reinstalling drivers "shouldn't do anything", bud... Just the nature of Windows itself suggests that driver issues are going to happen, Windows is notorious for it. Between drivers being "mistaken", overwritten, and updates that are really more like being reverted/downgraded, drivers are almost always being mishandled by Windows. Heck, one would figure that a driver called "Android ADB Composite Device" could be applicable to just about any android, but even in the mere changing of one device to another (Nexus 7 2012 to Note 3), 2 separate drivers try installing themselves as the same name, which in turn causes compatibility issues and connection issues between my devices and the computer. Checking around the forums, you can literally find dozens if not hundreds of people saying "Help, my nexus/android device wont connect via USB!"... It's because of the drivers. Having "too many" drivers or "close but not the right one" drivers both will drive people loony with difficulties, and flunder around thinking it "couldn't be the drivers, I just installed them!" Many times even just a reboot of the computer will orientate the computer between what was a good (working) driver and one that isn't working, and vise-versa. Windows takes drivers and makes them into a variable crap shoot, so sometimes yes, a reinstall can make a world of difference. Though that doesn't mean it always will.

I actually have a pretty good link that I wrote up in my signature from a couple years back describing said problem and how to fix it... Heck, I'd actually like to update it some, baring the time to do so...

Anyways, the real reason I meant to reply to you was to ask: In future updates to your Wuggy-goodness, are we going to see the 1.23 updated busybox? (crossing fingers)

I'll make it a point to have my signature show, so you can find the link in it that should help explain how to fix your issues... To be fair, Wug is not to blame for this, nor the update of his program, or anything else tying him to your computer... :P It's all a matter of how your computer is recognizing your device, and what driver it's using to do so, and even at what point in time it's recognizing it (since there's different drivers for both the device in it's normal operating state and the bootloader state in most cases, and that's before the device's declaration of what mode you want it to communicate to the computer in... MTP, Charge Only, PTP, etc.)

Chances are, telling your device to go from a MTP communication to a PTP communication (and allowing the driver to fully install, possibly requiring a restart of your computer) could be the answer to your problem. Sometimes your computer will like PTP better, allowing Wug's NRT program to work with it when MTP did not. It's been the culprit a couple of times for me over the months I've used NRT to update TWRP on my Grouper...

If all else fails, follow the (outdated) advice from the link in my signature... It's worked for me countless times for both my device and friends of mine IRL. Don't look at the forthcoming premise as the only bit of info you could take from the link; it's only a synapsis after all, but in short, it reads as:

"Too many drivers installed for the same device causes problems, remove all of them, and install ONE driver meant for your device, but not the goofy ones you find from Windows Update service or the "one size fits all" versions to be found from various developers... Something you can trust, like Google's OWN latest drivers, found here."...

And for clarification purposes, that previous statement doesn't reflect my views on Wug or any other developer's ability to provide us with quality drivers, it's only meant to state that Windows sees too many options as a cluster-of-no-fun waiting to happen.

Hope any of this can help.