# \[SOLVED\] Bios 3.17 and dual boot wifi

**URL:** <https://community.frame.work/t/solved-bios-3-17-and-dual-boot-wifi/31424>\
**Category:** Linux\
**Created:** [May 24, 2023, 6:36pm UTC](https://community.frame.work/t/solved-bios-3-17-and-dual-boot-wifi/31424 "2023-05-24T18:36:54Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Jonathan\_Haas](https://avatars.discourse-cdn.com/v4/letter/j/90ced4/32.png) [@Jonathan\_Haas](https://community.frame.work/u/Jonathan_Haas)\
**Post date:** [May 25, 2023, 11:06am UTC](https://community.frame.work/t/solved-bios-3-17-and-dual-boot-wifi/31424/2 "2023-05-25T11:06:35Z")

</div>

That’s completely normal with dual-booting with Windows, even with other PCs/Laptops. Windows somehow takes “ownership” of the Wifi card and keeps it assigned to itself until you do a cold shutdown/reboot.

You might have to fiddle with Windows settings to fix the issue, disable fast boot, fiddle with the energy options of the Wifi chip. I’m unfortunately not sure about the exact setting that would fix this behaviour.

---

_[View the full topic](https://community.frame.work/t/solved-bios-3-17-and-dual-boot-wifi/31424)._