Closed JensGJ closed 1 year ago
I've tested the behaviour on my secondary machine - running Windows 10 + Oh My Posh 12.7.1.
It shows exactly the same - e.g. no SSID and a name property that contains not only the interfacedescription from the Wi-Fi netadapter but the description plus some strange WFP filter information that does not appear anywhere if I run Get-NetAdapter wi-fi | fl *
I suspect that the tool Admin By Request (https://www.adminbyrequest.com/) might be causing the problem - but haven't access to a machine without the tool to verify.
@JensGJ I'll add the functionality back as it used to be. The way we fetch the networks receives everything, so there might be some strange things which are hard to filter.
This issue has been automatically locked since there has not been any recent activity (i.e. last half year) after it was closed. It helps our maintainers focus on the active issues. If you have found a problem that seems similar, please open a discussion first, complete the body with all the details necessary to reproduce, and mention this issue as reference.
Code of Conduct
What happened?
The connection section is not able to display the SSID of the WIFI connection. Additionally the Name property displays not only the expected name (from the interfacedescription property of the network adapter) but the name followed by the value "-WFP Native MAC Layer LightWeight Filter-0000".
I've used the wifi section earlier - where the display of the SSID property worked fine as well as the Signal and RecieveRate properties that was part of the wifi section.
In the current connection section I have now (with the template
{{ if eq .Type \"wifi\"}} {{ .SSID }} : {{ .Name }} \uf1eb ...
) I would expect the following value:B535_5E6E : Intel(R) Wi-Fi 6E AX210 160MHz
Instead I get this:
: Intel(R) Wi-Fi 6E AX210 160MHz-WFP Native MAC Layer LightWeight Filter-0000
Calling
oh-my-posh debug
reveals a number of errors regarding wlan:Running oh-my-posh 12.13.0 with PowerShell under Windows 11 H2
Theme
What OS are you seeing the problem on?
Windows
Which shell are you using?
powershell
Log output