Big thanks to Windows Update

[Steve]

My Bluetooth dongle was natively supported by Windows x64.

So I thought it wouldn't be an issue to let WU install an update to its driver a couple of weeks ago.

But no, it went and broke it.

Hilariously, the device manager said all was fine... but bums was it! The light wasn't flashing on it any more and nothing would connect with it. And of course, there was no way to uninstall it, and by the time I noticed (took me a while because I trust that my phone-sync kind of JustWorks[TM]) I didn't want to System Restore. Driver rollback wasn't supported either... go figure.

So, I delved into C:\windows\inf and sorted by modified date. I found the right inf file and removed that sucka, the uninstalled and replugged the dongle... boom it works again.

So thanks Windows Update, thanks for pushing WHQL certified drivers that break my bluetooth device onto me... no really, thanks.

[aidanjt]

If Microsoft developed a real package manager there wouldn't be half the problems there are with cruft and broken installs :/

[TheAnimus]

If Microsoft developed a real package manager there wouldn't be half the problems there are with cruft and broken installs :/

Completely disagree, the package deployment worked fine.

If MS spent the money on the WHQL testing on actually testing it, made no profit on it at all, then the quality of the drivers would be much better and more stable.

WHQL in my mind is a bit of a tax, just like the windows logo program. Boo.

[master811]

I had exactly the same problem with my laptop's bluetooth driver, I thought ooo a new driver update must get that, what a bad idea that was. Took me forever to remove the damn thing, as driver rollback wouldn't work, and my normal bluetooth driver didn't overwrite the new one at first.

[directhex]

you're lucky - my bluetooth dongle has zero x64 support. cheers broadcom for tight licensing restrictions on bluetooth drivers, preventing updates for older dongles

[aidanjt]

Completely disagree, the package deployment worked fine.

And of course, there was no way to uninstall it.

I guess our opinions of 'fine' differ somewhat. fglrx packages works 'fine' too if you want to look at it that way.

[MarcLister]

I have a Bluesoleil dongle. Utterly crap and bloated software. Got two processes running wasting about 20K ram. Planning to get 2 x MSI dongles from Scan when I have the cash for a Samsung 400/500Gb disk and an IcyBox.

[dangel]

Windows update drivers - not a good thing. Drivers are optional though, so the choice is yours isn't it?

[this_is_gav]

I have a Bluesoleil dongle. Utterly crap and bloated software. Got two processes running wasting about 20K ram. Planning to get 2 x MSI dongles from Scan when I have the cash for a Samsung 400/500Gb disk and an IcyBox.

Do you know that the MSI dongles don't use the BlueSoleil software too? There's generally 2 common platforms for Bluetooth in my experience - WIDCOMM and BlueSoleil. Other players usually just stick one of these in a different case, sometimes changing device names in the drivers too.

[Steve]

I just use the Windows Bluetooth stack, whatever that's based on.

[MarcLister]

Do you know that the MSI dongles don't use the BlueSoleil software too? There's generally 2 common platforms for Bluetooth in my experience - WIDCOMM and BlueSoleil. Other players usually just stick one of these in a different case, sometimes changing device names in the drivers too.

I do Gav, I do. Bleddyn, off another forum, told me that the MSI dongles used a small driver file. I've downloaded it off the MSI site. He also had a BlueSoleil dongle and chucked it in the bin and got the MSI dongle.

[this_is_gav]

Fair enough then, just thought I'd make you aware of the possible drawbacks to your scheme

[MarcLister]

Fair enough then, just thought I'd make you aware of the possible drawbacks to your scheme

All plans are 100 Gav proof.

[WLC-1989]

Microsoft driver support isn't that great, full stop. I'm still waiting for x64 drivers and software for my 'Microsoft Fingerprint Reader'; months on, and neither the OEM nor Microsoft intend to create such software, even though Microsoft have advertised the product as the future of computer security...

[acrobat]

Windows update drivers - not a good thing. Drivers are optional though, so the choice is yours isn't it?

Drivers are optional? Thats not 100% true all the time is it? If something is working fine, and a new driver offered no improvements, then I suppose its optional. But when something is either not working properly, or even just not working to its full potential, then installing a new driver for it, is a requirement. So people should be able to run windows update and for it to always work, not screw something up. Microsoft are lazy incompetent slackers. Get back to work Microsoft!

[Paul Adams]

To clear up a misconception - Microsoft don't write drivers for 3rd party hardware, they always come from the vendors.
Even the ones published through Windows Update.

I believe dangel meant that driver downloads through Windows Update are "Recommended", not "Critical", as they are not part of the OS - I don't believe Automatic Updates will install device drivers by itself, you have to opt to do it.