I use KIS on several home PCs and tablets on a home network. The PCs are 2x W10, 1x W7, all 2.4G wifi. KIS is fully up to date everywhere, W10 is 1903. With one of the PCs, I am having problems making it discoverable on the network - it is set up to be so, but sometimes is and sometimes isn't. Also, file transfer from this PC is unreliable. As far as I can see, the wifi signal is good everywhere (internet connection is good and fast). In investigating this, I have noticed that in KIS under protection >> firewall >> networks, not everything is now listed. It used to be that on each machine, two networks would be listed - an internet public connection, and a local connection. The former being the internet connection via the ISP, the latter being the local network. Now, on the 2x W10 machines, only the public connection is listed by KIS. I am not sure if this shows any light on my problem, but something has clearly changed. What is it that makes a network connection show up under firewall - or not?

(1) I noticed, KIS under protection >> firewall >> networks, not everything is now listed. It used to be that on each machine, two networks would be listed - an internet public connection, and a local connection. The former being the internet connection via the ISP, the latter being the local network. Now, on the 2x W10 machines, only the public connection is listed by KIS.(2) Also, file transfer from this PC is unreliable.

Hello nmw01223, Welcome!

1. Please tell us KIS version? build? patch(x)? x=letter
2. Please read:
3. https://community.kaspersky.com/kaspersky-internet-security-13/kis2020-my-ethernet-connection-can-t-set-local-or-trust-network-2443#post17821
4. (imo) It sounds same/similar to the first issue you're reporting.
5. If you confirm it is the same, it's a known problem, with a fix: patch 'e' mid October (proviso: final decision up to the developers). IF it's not the same, please provide images of the issue?
6. Issue (2), please clarify, add more exact detail, e.g. transfer to cloud? transfer to another pc via shared network? Examples of what happens, errors? Error reports? images, please?

Thank you:pray_tone3:!

20.0.14.1085(c) - all machines were updated in the last few days (since Friday 6/9). Yes, it does look to be the same problem. Machine_A does not usually show up under Network in Explorer on machine_B, and on trying to see all the shares by explicitly typing in \\machine_A in machine_B's Explorer it says "Windows cannot access \\machine_name" - 0x80004005 unspecified error. However - the other way round is OK, machine_B shows up on machine_A! (Both are running the same KIS version). Sometimes it does show up, however, but usually not for long. But, if I try to list an actual share under Network in Explorer on machine_B from machine_A - eg \\machine_A\sharename, then it does list OK. To be honest, I am not sure how much this has to do with KIS, it was only that when trying to resolve this I came across the anomaly of the networks not being listed correctly in KIS >> protection >> firewall >> networks. The file transfer issue is peer to peer on the local network. Big files can fail to copy part way through. No further information on that yet. All transfers to and from the internet are absolutely fine, reasonable speed, and wifi signal looks OK everywhere.

20.0.14.1085(c) - all machines were updated in the last few days (since Friday 6/9). Yes, it does look to be the same problem. Machine_A does not usually show up under Network in Explorer on machine_B, and on trying to see all the shares by explicitly typing in \\machine_A in machine_B's Explorer it says "Windows cannot access \\machine_name" - 0x80004005 unspecified error. However - the other way round is OK, machine_B shows up on machine_A! (Both are running the same KIS version). Sometimes it does show up, however, but usually not for long. But, if I try to list an actual share under Network in Explorer on machine_B from machine_A - eg \\machine_A\sharename, then it does list OK. The file transfer issue is peer to peer on the local network. Big files can fail to copy part way through. No further information on that yet. All transfers to and from the internet are absolutely fine, reasonable speed, and wifi signal looks OK everywhere. To be honest, I am not sure how much this has to do with KIS, it was only that when trying to resolve this I came across the anomaly of the networks not being listed correctly in KIS >> protection >> firewall >> networks.

Hello nmw01223, Thanks for posting back and the information:pray_tone3:

1. Did the issue exist after the machines updated to 1903 and before KIS 2020 updates?
2. Re Windows cannot access computer’ error code 0x80004005 & How to Fix Error 0x80004005 may help.
3. Putting aside the network anomaly for a moment, have you run the standard SFC Scannow, DISM Scan Health and checked the Network shares, if necessary remapped.
4. Also, (again, this is not for the network anomaly), when KIS updated to 2020, was 19.0.x uninstalled first? If not, on one machine you could uninstall KIS2020, save "License information" only, full shutdown, download and install fresh installer, full shutdown, restart, make sure KIS is active, run a manual database update, on completion, run a manual full scan, recheck "Windows cannot access \\machine_name" - 0x80004005"

Please keep us posted? Thank you.

Not 100% sure, but looking back, I think not. Probably only after 2020 updates. Those 0x80004005 links have some useful points that I will try. IPV6 is currently enabled, for instance. I'll try SFC, but think I'd better do a full partition backup first. 'Repairs' can have interesting results. Yes, 19.x was fully uninstalled before installing 2020. I always do that sort of thing. I'll come back when I have some answers.

Not 100% sure, but looking back, I think not. Probably only after 2020 updates. Those 0x80004005 links have some useful points that I will try. IPV6 is currently enabled, for instance. I'll try SFC, but think I'd better do a full partition backup first. 'Repairs' can have interesting results. Yes, 19.x was fully uninstalled before installing 2020. I always do that sort of thing. I'll come back when I have some answers.

Hello nmw01223, Thanks for posting back:clap_tone3:

1. atm the conversion to IPv6 is very low, I can't remember the number, but it's low. Until the full transition occurs, there's no need (for anyone, unless their IP provider has issued an IPv6 address), to have IPv6 enabled.
2. I'm TOTALLY sure you know this, but, before the partition, create restore point(s), sysimage & backups
3. IF, after doing all the windows "stuff", if NW share is still reporting errors, I'd still do a fresh install.

1. And, if after 1 to 3, NW share issue remains, look at adding exclusions, and then (this is bigger than Texas), if there's still an issue, escalate to Technical Support.

(imo) 0x80004005 is not related to patch(e) due mid October. AND, keep me posted please:pray_tone3:? Best regards!

An update. None of the suggestions under 0x80004005 made any difference. I have not tried sfc /scannow yet on anything. What I have done is reinstalled KIS again on machines B and C below (from scratch, same version - 20.0.14.1085(c)), which has changed things, or at least my perception of them. This is now how things are:

1. There are three relevant PCs - two laptops, one running W7 (A), the other W10 (1903) (B), and one desktop also running W10 (1903) (C).
2. All run KIS 20.0.14.1085(c).
3. Using Explorer >> Network, A lists machines A, B and C, B lists A and B but not C, C lists A and B but not C (ie itself).
4. So C does not get 'discovered'.
5. Network connections are set to private (home in the W7) case, not public, and the machines should in theory be discoverable.
6. But - typing in \\C in the B network address bar now does list all C's shares, and they can be accessed OK (not so previously).
7. A lists all the networks correctly in KIS firewall networks, B and C just show the public internet connection.

Part of the reason for not running sfc /scannow on C (which is the suspect one) is that whilst I have backups, if a reinstall from scratch was needed, for various reasons it would be a huge undertaking. C actually was a W7 machine that has gone right through all the Windows upgrade process from W7 to W10 (1903) over the years. B was installed from scratch last Friday so is unlikely to be an issue. So what it comes down to now is the missing displayed machine name of C on two PCs (B and C) - though all C's shares are now accessable and file copying seems OK (they weren't before), and incorrect listing of networks in KIS under firewall, also on B and C. Not sure if the two points are related or not, but they both run W10 (1903) and 20.0.14.1085(c) KIS. The machine that is totally happy is W7. This has now gone from being a problem to a minor irritation (though not really sure what has changed), so I guess I'll wait until KIS builds (d) or (e) come out and see what happens.

Correction to the above - machine B is now installed with 20.0.14.1085(d). Must have updated itself since the reinstall - possibly C has as well, haven't checked. B still only lists the public internet connection under KIS firewall, though.

Correction to the above - machine B is now installed with 20.0.14.1085(d). Must have updated itself since the reinstall - possibly C has as well, haven't checked. B still only lists the public internet connection under KIS firewall, though.An update. None of the suggestions under 0x80004005 made any difference. I have not tried sfc /scannow yet on anything. What I have done is reinstalled KIS again on machines B and C below (from scratch, same version - 20.0.14.1085(c)), which has changed things, or at least my perception of them. This is now how things are:

1. There are three relevant PCs - two laptops, one running W7 (A), the other W10 (1903) (B), and one desktop also running W10 (1903) (C).
2. All run KIS 20.0.14.1085(c).
3. Using Explorer >> Network, A lists machines A, B and C, B lists A and B but not C, C lists A and B but not C (ie itself).
4. So C does not get 'discovered'.
5. Network connections are set to private (home in the W7) case, not public, and the machines should in theory be discoverable.
6. But - typing in \\C in the B network address bar now does list all C's shares, and they can be accessed OK (not so previously).
7. A lists all the networks correctly in KIS firewall networks, B and C just show the public internet connection.

Part of the reason for not running sfc /scannow on C (which is the suspect one) is that whilst I have backups, if a reinstall from scratch was needed, for various reasons it would be a huge undertaking. C actually was a W7 machine that has gone right through all the Windows upgrade process from W7 to W10 (1903) over the years. B was installed from scratch last Friday so is unlikely to be an issue. So what it comes down to now is the missing displayed machine name of C on two PCs (B and C) - though all C's shares are now accessible and file copying seems OK (they weren't before), and incorrect listing of networks in KIS under firewall, also on B and C. Not sure if the two points are related or not, but they both run W10 (1903) and 20.0.14.1085(c) KIS. The machine that is totally happy is W7. This has now gone from being a problem to a minor irritation (though not really sure what has changed), so I guess I'll wait until KIS builds (d) or (e) come out and see what happens.

Hello nmw01223, (1) Thank you for replying and the "bigger picture". From the sound of it, there's been progress:ok_hand_tone3:. (2) Isn't it s:cry:d, your W:older_woman_tone3::older_man_tone4:7 is happy, yet about to be ⚰ in 3.5 months? So many folks, when reporting issues with multiple machines with different opsys, say, "on W7, everything works!" (3) I have no issues about not using sfc scannow, suggestion was based on sfc "sometimes" shines a light.

1. (4) For clarity, 20.0.14.1085 (d) released September 5, 2019. Patch D fixes the vulnerability which could be used for acquiring unauthorized permissions in Windows.

-- (a) Have you remapped the shares? (b) If KIS if OFF, does everything work? (c) Have you set all the affected machines in SafeMode and checked? (e) Re: "0x80004005" - have you contacted MS? (f) Have you contacted Technical Support? If (a) to (e) have been done or are done & "0x80004005" remains, & if you decide to contact TS, they'll need traces run as the issue is replicated, GSI & Windows logs, images, if a visual representation "shows" the issue clearly, a dot point history (do a spreadsheet, it much easier) &, even use C:projector:mStudio, make sure they understand, you're not asking for a fix for "firewall >networks, all devices not visible", you know there's a (e) fix, due mid Oct... Let me know how you go please? Best regards K Technical Support - select LOCATION, select General Product Use, select from available options:

1. Phone (not available all regions)
2. Online Chat (not available all regions)
3. Via MyKaspersky account web portal , log in, create an INC request.

GSI & Windows Logs Collecting information for Technical Support Diagnostics (Links) Library KIS 2020 Library

Another update, and to answer your questions: Machine C has now automatically updated itself to 20.0.14.1085(d), and ... its machine name now does turn up in Explorer >> Network on both machines B and C (haven't looked at A, but it was OK there in the first place). If I look at networks under KIS firewall on machine C, it does now list the local network (connected) as well. Oddly it is listed as a hyperV virtual ethernet adapter - but (a) there are no virtual machines on this PC and (b) there is no active ethernet connection either - it is wifi. Nonetheless, something is there. Machine B still only lists the public network under KIS firewall - but machine name and shares from C are now all visible and accessable, so what the hell! So to answer points (a) to (e) above: a. I was going to remap one or more shares to see what happened, but as it is now all working, not much point. b. When it previously wasn't working, stopping KIS protection had no effect on whether machine C name showed up under Explorer >> Network. c. No, was going to, see (a). d. No, not contacted MS (never had much luck with that in the past), and anyway, 0x80004005 only occurs when a machine's shares cannot be explicitly listed (eg "machine is not available..."). Since I reinstalled KIS as previously stated, they now can. e. No, again I was going to, but thought I'd see how I got on with the forum first. (I have found KIS technical support very good in the past). So, it largely seems to have resolved itself, the only outstanding point being the listing of networks on B under KIS firewall. I feel therefore I'll just leave it all for now and see what happens. If things start to break again - I'll be back. Thanks for all your help and information.

Hello nmw01223, What a ride! Some of your comments make me :rofl:. I'm glad there's progress:clap_tone3: Re "contacting MS", if the issue turned out. not to be KIS related, then, even if you've had "not so happy experiences", it's always worth a shot. Anyway, with the "suggestions" thus far, you have a working guide of what to do & what's needed, if necessary. Hopefully "you'll be back" to let us know if B fixes, by itself, or with (d) or (e)? Not just if there's more / new problems:wink:! Best regards