The issue does not exist prior to Windows 7 UPDATES.
My Fuelband worked just fine on my desktop with Windows 7 until one of the updates.
I confirmed this again the other day.
I had to replace my dead hard drive. The Geek Squad loaded my HP Recovery Disks with virgin Windows 7.
I brought my PC home and the first thing I did was plug in my Fuelband.
It not only worked just fine, but it also loaded the software.
HOWEVER, after that, I updated Windows 7.
Today, when I plugged in my Fuelband, it no longer works... nor was the Nike+ Connect software anywhere to be found in my Programs.
I downloaded the software and of course it cannot "SEE" my fuelband when it is plugged into the PC.
I have to boot up an ancient laptop with Windows XP in order to download my Fuelband.
This issue is DIRECTLY related to something Microsoft did in one of its updates.
I've tested this theory multiple times after wiping hard drives and reinstalling Windows 7 and trying the Fuelband before and after the updates.
As usual, Microsoft blames Nike and Nike blames Microsoft.
In this case, because Windows 7 (UPDATED) is the only OS that does NOT "SEE" the Fuelband when it's plugged in, it is something within the updates.
Although I have not tested the following bandaid-fix this time, I have discovered in that past that uninstalling and reinstalling Nike+ Connect can work... but when it does work, it only works the first time right after installation... and then it's back to
not recognizing the Fuelband.
The System knows something is being plugged in and removed, based on the Windows alert sounds, however, at this point, there is no Hardware Remove icon in the system tray... and I cannot re-verify my past experiences where the System recognized the device as
the Fuelband.
My past experiences were of the System asking me how I'd like to handle the Fuelband... i.e. the options for any drive, such as open as a file, etc.
With so many updates that can impact the security of a system, I've never taken the time to load them one-by-one until pinpointing which update is responsible for the issue... however, it is within the first 10 or 11 that come up immediately after reloading
Windows 7 on a hard drive.