I have a digital camera that acts as Wi-Fi access point. It broadcasts SSID but it is not visible in list of networks in charm bar. On the other hand it is visible via netsh command:

Interface name : Wi-Fi
There are 10 networks currently visible.

SSID 7 : DIRECT-F3E0:ILCE-5000
    Network type            : Infrastructure
    Authentication          : WPA2-Personal
    Encryption              : CCMP

Note there are no filters:

Allow list on the system (group policy)
---------------------------------------
    <None>

Allow list on the system (user)
-------------------------------
    <None>

Block list on the system (group policy)
---------------------------------------
    <None>

Block list on the system (user)
-------------------------------
    <None>

The question is why ? I am aware I can setup a manual wifi connection but it will be visible in the networks list even it is not broadcasting. That's not convenient. After all it is just another wifi access point.

It is Broadcom wifi adapter. I suspect the length of SSID or special characters like ':' might be the issue but I can not change the generated SSID format by the camera.

Thanks, Petr

• Edited by Petr Vones Sunday, June 14, 2015 7:29 AM

Will this SSID be visible with other Windows machines?

Yes, it is. I suspect there is a bug in the Broadcom wifi driver but I use most recent version available. Any other ideas like specific ETW log ?

• Edited by Petr Vones Tuesday, June 16, 2015 11:32 AM

Hi Petr,

What is the model of the network adapter on this specific machine?

Broadcom BCM4324 WLAN Device, driver version 5.93.102.10.

Petr

Hi Petr,

It seems that you have got the latest driver.

Have you tried to connect to the wifi since it can be found by the command line? Is there any error message recorded in the Event Viewer?

Best regards

Caused by the latest version 5.93.102.10 of Broadcom BCM4324 driver. Downgrading to previous version 5.93.100.20 solved it.

• Edited by Petr Vones 16 hours 10 minutes ago
• Marked as answer by Petr Vones 16 hours 10 minutes ago

Caused by the latest version 5.93.102.10 of Broadcom BCM4324 driver. Downgrading to previous version 5.93.100.20 solved it.

• Edited by Petr Vones Monday, August 03, 2015 3:12 PM
• Marked as answer by Petr Vones Monday, August 03, 2015 3:12 PM