[Bug] Compatibility bug with Portmaster 1.6.10

[XSpark0]

If i shutdown Portmaster and turn it back on, it will some 5 or 10 minutes later throw a Detected Compatibility Issue error and show Insecure in the app. Clicking on Restart in the app (have to like restart multiple times) temporarily fixes the issue until it returns again minutes later. I don't actually have compatibility issue i am not using another firewall except Portmaster, not using a VPN, and antivirus is simply the Kaspersky free edition which doesn't come with its own firewall. I am on Windows 11 23H2 and i am using Quad9 DNS.

The compatibility issue disappears on its own later if i shutdown pc and later turn it on again and sometimes without having to shutdown pc. That's why i think its a Portmaster bug and not an actual compatibility issue.

Logs:
2025-01-15-16-48-24.log
2025-01-15-16-48-24.error.log

[Maizwa]

I too am having the same issue... I am using the same windows and version but using mullvad's DNS, it gave me a notification that is having a compatibility issue for some reason.

[Maizwa]

I too am having the same issue... I am using the same windows and version but using mullvad's DNS, it gave me a notification that is having a compatibility issue for some reason.

Ok, I fixed it. This is what I did:

1. Open the command prompt (cmd.exe) as an administrator.
2. Before connecting identify the name of the connected network interface. In the case below it is "Local Area Connection"

netsh interface show interface

3. Connect to the VPN. Once connected proceed to the next step.
4. Flush the DNS resolver cache

ipconfig /flushdns

5. Disable the DNS configuration for the Interface identified in step 1

netsh interface IPv4 set dnsserver "Local Area Connection" static 0.0.0.0 both

6. Test for DNS leak -> https://dnsleaktest.com
7. After disconnecting, reconfigure the adapter to renew the previous DNS settings

netsh interface IPv4 set dnsserver "Local Area Connection" dhcp

8. Once again, flush the DNS resolver cache.

ipconfig /flushdns

9. Done

Thanks to https://dnsleaktest.com