Error code 0x80070035, The network path was not found

Friend has a persistent problem on his simple small biz network (No domain):
Can't connect to shared folders "Error code 0x80070035, The network path was not found"
Tried to help, read many posts and "advice recommendations", no go.
We spent hours to no avail.
Classic SNAFU. Everything works except that.
What could it be? Where, oh where is the fault buried?
Why is this so difficult in Windoz 10?

The difficulty here is that we have so little data to work with. I could start listing a million things to look at and to try, but let's start with a few questions to help narrow down the issue.

1) How is that you are trying to connect to share? For example, are you going into File Explorer, going into Network, then browsing for the computer and share to connect to? Are you directly typing in the path to connect to in File Explorer? Are you trying to connect from a command line? Are you using a premade shortcut? etc.

2) Did attempts to connect to this same share work in the past or is this a newly created share that never worked? If it worked before, can you think of anything that has changed.

3) Does this difficulty happen only with this share or with any share?

4) How are the machines connected to your network? Wireless? Ethernet?

The above are just a few questions to start with. Don't feel limited to answering only these questions. Feel free to provide as much detail as possible. For example, "These are steps that we took to try to connect to the share" and "these are the steps we took to try to troubleshoot the issue". You specifically note that you have read many posts so let us know what things you found that you have eliminated as NOT being the cause of the problem. This will allow us to not rehash the stuff that you have already tried and maybe give some more intelligent advice.

dalchina said:

Agreed, networking can be a nightmare in Win 10.

Is your friend's network a new configuration, or has this problem 'suddenly' occurred?
As usual, we have no history.
A: Existing but relatively new. Was once laptop-desktop then added 3 more computers over time. Desktop is sort of the "server" & storage with backup. Apparently problem started after one the notorious enforced "Windows updates".

Try3 has posted an extensive checklist.
A: Will check it

When someone says in general "Tried to help, read many posts and "advice recommendations", no go "
trying to provide advice is almost meaningless, as it will probably result in 'tried that already'.
A: Yes & No.
The web is more and more a marketing ploy of "advisors" & "helpers" who push a product and even often can't type correctly where needed. Most end up with "Clean reinstall of Windows" advice as last resort. Another way of declaring "we have no effing clue but do buy our product".
Why should I "...tear down my house and rebuild all because the front door jams?..."
Anyway...
A: I went to my own system and setup shared folders. Ended up with exactly the same issue!

Anyway, FWIW, have you tried everything here (except SMB1 assuming all are Win 10):
10 Ways to Fix Error Code 0x80070035 [With Pictures] - MiniTool Partition Wizard
A: Went through all these steps but to no avail. As if it has be like that. Except in #10 I get "The network name cannot be found"
Share Files and Folders Over a Network in Windows 10
Option 1
A: Went through all these steps but to no avail.


And posts from e.g.
Share Files and Folders Over a Network in Windows 10 post #108

A: Went through all these steps but to no avail. Don't even get the Windows Security login.
Extremely frustrating and needlessly effed up complexity. I know I'm not alone, there are many others which have the same issues. Why simple if it can be made dysfunctionally complex?

Thanks for your reply.

The issue remains and oddly enough, on his as well as on my experimental setup at home.
Why this has been developed into such a problem is incomprehensible to me.
I know, it's so safe and secure it won't start anymore to "protect" you from access!

Both systems are 22H2, up to date, run ESET and have the same login accounts.
I even uninstalled ESET on both, same jazz.
I changed/added other login accounts.
I verified/checked the credentials.

What works 100% best and guaranteed is: THE NETWORK PATH WAS NOT FOUND ERROR CODE: 0x80070035
I'm not alone with this! (published in 2018!).
Nowhere to date I or others seem to have found or published the "Eureka" answer.
As an old saying goes: "The fish stinks on the head first..."

Add some cynicism to it, the inane worthless "Troubleshooter" reports back: "Troubleshooter couldn't identify the problem".
I bet you "Troubleshooter" couldn't even identify if windows is installed or not... can it identify itself what it itself is?
Another glorious useless feature like on boot "Your PC needs to be repaired" and when executed comes up with "Could not repair PC"... (I'm convinced many are "mandated" by the legal dept.)
Find 1 person in the world who every had a successful "repair".

I'm about to give up and just use a 3rd part app and/or mem stick when file access/transfers are needed.
The time spent is soon not any longer worthwhile.

Perhaps I go back to the good old days and piece of mind, pull out my Remington portable typewriter, and write you a letter.
Such simple things did and still work quite well!

It is like a friend of mine jokes about the security obsessions with everything these days:
A future airliner will never take off because it does not meet it's own security checks & verifications...the onboard computer has determined..."I'm sorry [Capt] Dave, I'm afraid I can't do that...".
MCAS was already a first flavor of this.
He's got a point!

Asides from this perfect S.N.A.F.U. there many others around of which many "pull their hair out" with no results.
i.E. [unrelated] Error code 10 on Intel WiFi that came up after some update years ago. Intel drowns you with excuses and endless driver updates finally claiming the WiFi card is defective. Really?
So how come after I uninstall all driver updates, do a hard reboot & UEFI reset it works again with old 2019 drivers (until the next enforced update because "you ignoramus you have outdated drivers and we will update them!"). Intel's answer: silence is bliss.

Another [unrelated] one is the over 10 year old sudden start "initializing" failure of Nuance Dragon. Evidently Profile related. Clean uninstall/reinstall = same problem. But it works in all other user profiles on the same machine. The Event Error ID is totally irrelevant.
Most likely another security issue. Answers & solutions to date are = to shouting in space in a dark corner...

...and so on and so forth.

End of [justified] rant!

dalchina said:

Now as yet you've not given the full Windows build as requested by the forum when you wrote your first post
A: In the side panel of messages. always current. Windoze 10 19045.3324 resp 19045.3208 on client [probably by now also 19045.3324

Why may this be significant?

I've just found that this PC - 19045.3324 - now cannot see my other PC - 19045.3208

But that PC can see this one.

I wonder if that update has done something... I'm going to try uninstalling it.
A: Had same issues with previous versions. The web is full of folks having the problem. Sent you a link in previous msg. from a dude --Clive le Roux-- with identical issues, written in June 2018 (!!!) Ver. -1907. 785 users had the same question....! I've had it for years and eventually more or less gave up.
Who knows, maybe you have to pay M$ so they'll enable it? Bet you this is coming soon if not already on the way!
User= M$=

I had too...

PS Microsoft calls this a "quality update" whatever the f this means. But it seems to be an "newly" created issue... just found this (not read yet).