Hi Frameworkers,
I’ve just updated my 11th-gen Intel Framework 13 to Windows 11 after fighting it for two and half hours. The normal error messages that are so vague they’re meaningless, having to run a downloadable installer as admin because Windows Update can’t manage it, freeing up an extra 25GB of disk space, and culling particular background processes before running the tool. I must learn about dual-booting Linux soon, arrrgh!
Now “successfully” running Win11 and running the Framework driver package installer - three times - I have no Bluetooth. This died first when completing Windows updates in preparation for the update, and then is still MIA.
The installer claims to have installed the Bluetooth driver but I can’t see it in device manager, add any devices or turn it on anywhere.
Help? :(
You must log in or register to comment.
Sadly this is just how it goes for Windows sometimes. You’re right in your suspicion that Linux’s driver infrastructure is miles ahead, and this wouldn’t have happened on Linux.
Still, if I were you, I’d try doing an in-place reinstall, then double checking the driver package is the correct one, and then try to apply it. That should be the closest to a clean install without deleting any data.
Failing that… I’ll be honest. I hate troubleshooting Windows. Hours of headaches spent with vague error messages and no documentation. When I have an issue on Windows and an in-place reinstall doesn’t do it, I just take a quick backup and reinstall the OS clean. It’s not worth fighting with. It’s so complex 1 thing may have gone wrong out of 10 thousand different things and you don’t have the tools to properly trouble-shoot it anyway unless you’re like a senior Windows sysadmin. It’s more time effective, and it also gives you the benefits of a clean Install - all the small errors and things that pile up over time on Windows just go away, any unnecessary software you didn’t really want to uninstall is no longer there, etc.
Tbf, DOS and computers back then were simpler than today, making it easier to troubleshoot comparatively.
Win 3.1 added a bit more complexity on top of that. Basically we built more complex structures on top of older simpler ones to make it more and more user friendly. The more user friendly, the more complex the underlying tech to make it user friendly (harder for techie people to troubleshoot since there is so much more going on).
That’s why SBCs like the RPi are gaining traction. It’s like going back a few steps so people have an easier time learning some of the underlying basics of computing.
DOS troubleshooting sucked. I still have nitemares about battling QEMM 386 to free up a few more KB to get a game running.
For me troubleshooting wasn’t the issue with memory. Especially once I know the difference between extending expanded etc etc. Of course I forgot them all now lol. Manga shoes typically revolve around irqs and other resources. However once I got a mental map of all my devices and what resources they were using I can typically resolve conflicts unless I have two devices that conflicts no matter what you change. Then it’s not really a troubleshooting issue it’s more of a resource issue and I know it.
I remember making a multichoice auto exact file that lets me customize how to set up memory management for specific set of games