WiFi - failed to start device

not_MrFrost · October 3, 2023

Hi everyone! I started having some problems with the WiFi, since I changed from Zorin OS to Linux Mint. I don't really understand how it happens, I'll try to explain.

I come home, boot up the PC, press F12 and choose to boot in ubuntu (Linux Mint). When I log in, I have to internet (it doesn't even show that I can connect with wifi). Restart, don't touch anything, since the PC should boot automatically in Windows. It freezes to the start up screen, where you see the mobo logo and down you see the keys you need to press to enter the bios or to choose where to boot. I have to force a restart, now it boots normally, it goes in Windows, and I also have to wifi there. I then have to uninstall the device from device manager, since it gives me error code 10, failed to boot device. Then, turn off the computer, turn off or unplug the psu, hold the power button for 20 seconds, boot up again, and now the wifi works.

So, in short, since I installed Linux Mint (dual boot), I've had this problem. It seems like, when I boot in Linux first, and not Windows, it messes with the wifi driver or something? And it's strange that, when I restart the pc, it freezes while booting up. Anyone can help?

Also, when I boot up again in Linux, everything works fine, on both ends. I'll try to do various combinations to see if I can cause the problem, so at least we now what triggers it.

Thanks!

UPDATE: Ok, so I did an experiment. The pc if off, I turn it on, and boot in Windows 11. No problem here. I turn off the pc, and on again (not restart, I completely turn it off, then on), boot in Linux first, and as I expected, I have the wifi failure. I turn it off, then on again, and boot directly in Windows. Device Manager doesn't show me any error, and the wifi says that I'm connected to my home wifi, but it show no Internet available, and when I search for other wifi networks, it doesn't find anything. When I try to uninstall "Realtek WiFi 6E" (or something like that), it load and loads, and then the pc crashed with a glitched BLOD, but it might be my fault here, because I was trying out some keyboard shortcuts to open the task manager, because I didn't remember what it was, so I was pushing random buttons. Anyway, after the pc crashed, I did the standard procedure as I said before; uninstall the device (successfully this time), turn off the pc, unplug or turn the switch off on the psu, hold power button for 20 seconds, boot up the pc in Windows, and everything works again (tho I have to write again the password for the wifi). I should try to do the same thing, but booting in Linux first, and not Windows... maybe later.

not_MrFrost · October 3, 2023

Ok, so, I did the post, but then I found the solution by myself lol. While writing the update, I got a "lightbulb above my head" moment: maybe fast boot/quick boot in Windows was giving me problems? Because I remember watching a video, where they explain that when you restart the system, the pc actually completelly turn off and on again, but when you turn off the pc, it doesn't actually completely turn off, if you understand what I mean. And it was strange, because rebooting the pc, and going in Linux, I had no problem, but turning it off, and then booting in Linux, there I had problems. So I did just that; booted in windows, turn off fast boot, turn off the pc, turn on again BUT I booted directly in Linux. As a matter of fact, I'm writing right now from Linux, with no Wi-Fi issues. So, my hypothesis, is that the Windows drivers "clashed" with the Linux drivers, because of the fast / quick boot.

At this point, this post is more of a blog, and not a discussion for help lol.