Windows 10: My W10 show "Flight mode" icon when the WiFi works. How to make it show the right mode?

After a Windows 10 update some month ago it shows always "Airplane Mode" also when the WiFi works perfectly. When I click the network icon Airplane icon down to the right it shows that both WiFi and Airplane mode is on. If I click the Airplane the Airplane mode stops and the WiFi icon is shown. What can be done to make W10 show the right network mode?

:)

 

Force always start in flight mode

Thank you Macboatmaster. But you have described the standard manual way of turning off WiFi which was what I was trying to automate at each restart/sign off/shutdown. And having tested the reg DWORD change I have found puzzling results so still dont know why the tutorial by Brink suggests this method when I cannot seem to get the expected results. In the interests of helping fellow low-altitude operatives such as me I am now trying the options on a second machine ... Starting from..

default DWORD = 0 Current radio status is... wifi = 1 bluetooth = 1 flight = 0 Action centre shows wifi black for 1/on ... bluetooth black for 1/on ... flight grey for 0/off Clicking bluetooth or wifi in actions turns each individually on or off. Clicking flight in actions turns both bluetooth and wifi off. So far as expected. So changed default DWORD to 1 (had hex selected first go then as decimal second go) Restart. Actions show bluetooth, wifi and flight all as black/on. Machine is online. Clicking flight once has no effect on wifi or bluetooth. Clicking flight second time turns off bluetooth and wifi. Clicking wifi and bluetooth changes those radio states but leaves flight black/on. System tray shows flight mode regardless of wifi/bluetooth state. Only clicking flight mode changes system tray icon. Still switches wifi and bluetooth states as expected. So the button clicking still controls radio states but the display of flight mode can obscure the actual radio state. Now clicked flight mode to black/on. Restart. Still in flight mode with both bluetooth and wifi off. Back to default DWORD = 0 Flight mode is black/on. Restart. This time actions shows flight/bluetooth/wifi as grey/off. System tray shows globe and machine is offline. Clicking flight on/off only changes flight button and has no effect on bluetooth or wifi. Clicking bluetooth or wifi changes those radio states as expected so machine can be put online again. When online the flight button works as expected to change bluetooth and wifi radio states. Running out of time this morning to do more ... But I still dont appreciate the purpose of this reg method as this machine still relies on previous radiostates prior to restart ... or have I missed something ? Seems to me that the DWORD controls the flight mode button colour/on/off status but does not shut off the radios unless that was their states prior to restart. Willing to accept that I have missed the point but still seeking an automated way to keep radios off without havig to remember flight mode at every restart/sign of/ shutdown. Lazy perhaps but just trying for a bit of consistency. Paul

 

Flight mode icon and wifi&bluetooth icon are lid at the same time

Hi, Ben

I have tried. As soon as I turn either Bluetooth or WIFI off, the flight mode icon turned grey immediately. After I turned all of them off(Bluetooth, wifi, flight mode), I restarted the device. After restart, the Bluetooth and wifi are still off as before,
but the flight mode icon is blue again. It looks like flight mode icon is always blue when restart, but it is false indication as the flight mode is actually off.

Xiaoyang

 

WiFi faster in flight mode

I have had issues for several weeks whereby in normal mode my wireless on a Dell E7450 gives speeds of 200-300Kb/s (measured using fast.com) however if I switch on Flight Mode and activate WiFi I get 75Mb/s.

This is 100% repeatable across multiple access points.

I have tried switching off Bluetooth and running normally i.e. no in Flight Mode, the result is the same. I have deleted the WiFi drivers and reinstalled them yet the issue remains.

Any suggestions what may be causing this issue?

I am running Win10 1909 build 18363.752