-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
-
×InformationNeed Windows 11 help?Check documents on compatibility, FAQs, upgrade information and available fixes.
Windows 11 Support Center. -
- HP Community
- Notebooks
- Notebook Wireless and Networking
- The WIFI LED F12 key does not change color by enabling or di...

Create an account on the HP Community to personalize your profile and ask a question
03-09-2017 03:08 PM
Thank you very much for your reply.
"To resolve this issue, run Windows Update to download and install the latest driver, or reinstall ... from Recovery Manager." This is exactly what I did: Windows 10 downloaded the latest driver 1.1.17.1. This enabled the wireless button as described.
BUT the only thing not working properly is the change of light of this key according to its status. So it's not the issue described in the service advisory since I can change the status of the airplane mode without any problem.
03-09-2017 03:51 PM - edited 03-10-2017 09:01 AM
I can't believe that I found the solution:
- disable airplane mode
- enable WiFi (if not already when airplane mode off)
- enable Bluetooth
- disable airplane mode
Now the LED shows the right color when it's off. And to add this, I'm using it after several Hibernation/Sleeps since a full restart.
@MrRobot: Please pass this to the right team which is developing the Wireless Button driver. This is definitly a bug in the driver. It should show the correct light (in this case red) even if Bluetooth was not active by the time of activating airplane mode. PLEASE!!!
I don't want to have Bluetooth activated constantly just for the Wireless Button to work correctly, it's unneccessary expecially when on battery.
For a hopefully TEMPORARY workaround, I recommend to disable the Bluetooth adapter in device manager, if it's bearable.
Then everything works exactly like I expected it to work and how it works till the first sleep/hibernation.
I thank you very much for your assistance, help and time. And please provide this feedback to the development team.
EDIT:
Some experiments with this tell me: Yes it is definitely related to the Bluetooth driver.
When resuming sleep mode, then the light is broken again, but when I toggle Bluetooth and toggle airplane mode afterwards, it works again.
EDIT2:
Uninstalling the Bluetooth driver completely solved the issue. So it's definitely related to the Bluetooth driver.
03-10-2017 12:46 PM
Hi @Marcel93, I am the @Chimney_83. It looks like you were interacting with @A4Apollo, but he is out of the office today so I'll take over from here.
Thanks for the reply and glad that the issue is resolved. Please do post your technical queries on our Forums for assistance.
Chimney_83
I am an HP Employee
03-10-2017 02:12 PM - edited 03-10-2017 02:14 PM
Thanks for your reply. @Chimney_83
I would not call this a solution to the issue. This is more a workaround for a bug that's present.
Due to this I am not able to use Bluetooth (its driver is currently not installed but the light is working as expected)
This is also the reason why my other HP/Compaq devices don't share this issue (they don't have a Bluetooth card).
So PLEASE pass this to the developers to fix this in a future driver update. I guess there are more people around using the Windows 10 Anniversary Update who don't have the knowledge about their machine to "fix/circumvent" this.
03-10-2017 02:30 PM
Greetings @Marcel93,
I have brought your issue to the attention of an appropriate team within HP.
They will likely request information from you in order to look up your case details or product serial number.
Please look for a private message from an identified HP contact.
Additionally, keep in mind not to publicly post personal information (serial numbers and case details).
Thank you for visiting the HP Support Forum.
Chimney_83
I am an HP Employee
05-07-2017 03:57 AM
Are there any news on this topic?
I did not yet receive any private message until today..
Also, there is still no driver update available to fix this.
- « Previous
- Next »