AlanB

@FLOOD and accepting @Jsdn ‘s hypothesis that this problem is indeed just a problem with disabling the Firewall in the free edition. Just to state the obvious, hopefully TS will see the commercial incentive… I am sure many users of the free version do not have the environment to cause this problem. However VM usage isn’t uncommon, so, many free users will experience this annoyance. Why would these users then even consider upgrading?

OK, I set the hosts file as requested, shutdown, powered up and logged in. The prompts were the same.

Here are a typical 3 prompts images. Each is followed by an identical “Attention” confirmation prompt which I cannot screen-grab, so photo instead. I had assumed that one of those was Windows Sandbox, but when I started that, Kaspersky prompted for Adapter #6. VirtualBox and VmWarePlayer are obviously setting up networks at boot, but I am not sure if anything else is (or how to check). I thought that this might help recognise the networks. >ipconfig Windows IP Configuration Ethernet adapter Ethernet: Connection-specific DNS Suffix . : home Link-local IPv6 Address . . . . . : fe80::a556:22e9:1a0d:c9eb%19 IPv4 Address. . . . . . . . . . . : 192.168.0.9 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.0.254 Ethernet adapter VirtualBox Host-Only Network: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::693c:7868:69b1:ead2%5 IPv4 Address. . . . . . . . . . . : 192.168.56.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : Ethernet adapter VMware Network Adapter VMnet1: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::e1d9:5d4f:8609:fc30%21 IPv4 Address. . . . . . . . . . . : 192.168.42.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : Ethernet adapter VMware Network Adapter VMnet8: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::f541:dbc9:c5ff:7d63%16 IPv4 Address. . . . . . . . . . . : 192.168.193.1 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : Ethernet adapter Ethernet 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Ethernet adapter vEthernet (Ethernet): Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::ed40:573d:c3e6:dee5%15 IPv4 Address. . . . . . . . . . . : 172.19.144.1 Subnet Mask . . . . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . . . . : Ethernet adapter vEthernet (VirtualBox Host): Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::c5f4:5be2:c65e:df59%37 IPv4 Address. . . . . . . . . . . : 172.22.176.1 Subnet Mask . . . . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . . . . : Ethernet adapter vEthernet (VMware Network ): Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::f551:215e:b22d:f6d0%43 IPv4 Address. . . . . . . . . . . : 172.17.64.1 Subnet Mask . . . . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . . . . : Ethernet adapter vEthernet (VMware Network ) 2: Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::b80d:2a97:7ee9:58b8%55 IPv4 Address. . . . . . . . . . . : 172.18.144.1 Subnet Mask . . . . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . . . . : Ethernet adapter vEthernet (Ethernet 2): Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::38b6:1cd0:ec4a:3492%44 IPv4 Address. . . . . . . . . . . : 172.30.224.1 Subnet Mask . . . . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . . . . : Ethernet adapter vEthernet (Default Switch): Connection-specific DNS Suffix . : Link-local IPv6 Address . . . . . : fe80::3c28:6fa0:e770:ddeb%75 IPv4 Address. . . . . . . . . . . : 172.31.240.1 Subnet Mask . . . . . . . . . . . : 255.255.240.0 Default Gateway . . . . . . . . . : Original hosts? Are you referring to C:\Windows\System32\drivers\etc\hosts? If so, I will need to go and look for one; I think that it would be only comment lines but I cannot remember for sure.

The alerts show after login, no interaction is required with Kaspersky or any other app (Kaspersky obviously auto-starts).

OK, didn’t realise that the Enable Traces would work through a restart. The number of network prompts seems to vary. From Sleep and Hibernate I have only ever seen 3 prompts. Since I have been doing the Restarts to grab the traces, I have seen 7, 5 and this time it was just 3 (No, Restrict, Yes). Hope it is all as required this time 😀

OK, I think that I have done what you wanted, from a clean start. The first prompt appeared before I could navigate to and start traces, but I start traces before I responded. I think that I actually got 7 prompts that time, I gave different responses… No, Restrict, Yes, No, Restrict, Yes, No. Then stopped trace and packaged it Have attached the new Traces and a Detailed report as requested. Hope that helps.

Hope this is what you need. For the traces I… on my PC (already booted) I got the support page ready put the system to sleep woke the system and logged in before the first of the problem prompts appeared I started the traces waited for and responded to the three network prompts stopped the traces generated a local report which is attached. Also supplied the get system info report. The PC was running with all of my browsers etc on it, if this means there is too much dross in the report, let me know and I will try to find time where I can grab the traces when nothing else is running… just let me know.

KSC Free 20.0.14.1085 (k) Same problem with 3 virtual networks (Ms Sandbox, VM Workstation Player & Oracle Virtual Box). I get prompted for all 3 after every start, resume from suspend and resume from hibernate. It only started a couple of weeks ago.