New
#11
EUREKA! YAHOOO!! Error code 0x80070035, The network path was....
EUREKA! YAHOOO!!
"Error code 0x80070035, The network path was not found"
I found it! The cause! By George, I think he’s [I] got it!
This is my third weekend I have wasted away 12 to 14+ hours trying to find where "the dog lies buried".
Like so many (I counted thousands by now) most of the "solutions" and "answers" directions to the issue "ended up in the wrong part of town". Nothing ever resolved it. On the way to all, I learned something again about the mindset, mentality, attitudes, culture and ideologies out there on the Internet.
(Hint: when one dog pees on a fire hydrant all other dogs will go and pee also on this fire hydrant, but with barking so all know...)
As I suspected, it is good old Windows 10 style buried, hidden, camouflaged, obtuse, distributed and hidden all around settings and of course with the suspicious hard to find, if ever and if, proper documentation.
As suspected, "policies" is one of many convoluted and referencing to other settings that cause this to stop working. Upgrades being the most likely cause due to Microsoft setting authoritarian "snow plow" style in their safety and security obsession many user and policy settings back to default, disabled and/or off/on without recording and saving the last state prior to the update. whatever is "safest" for them. I smell lawyer liability-thinking behind all this, courtesy the most litigious nation in the world...
All combined in the right order and context it works flawlessly. One off, and you end up hiking around the world finding that one special missing "screw" whilst everybody tells you they have them or want to sell you something else they claim "fits and will work".
I now need now to find out which one or which combination of several settings has the profound impact creating this notorious "error code 0X80070035, The network path was not found".
I am currently disassembling my steps in the "classic scientific verification approach", documenting it for myself to artificially re-create the problem again. Then I will "reassemble" everything again to see if I successfully eliminated and solved the artificially re-created problem. Once I have verified all that, I can, like a scientific experiment, share it and everybody can create and re-create it and come to the same conclusion hopefully.
This also, that I don't give some others here the opportunity again bashing me with cynic lecturing and ridicule and chastise me as recently about something I could not find documented thus believed to be an undocumented feature and only found out by taking a risky trial & error approach possibly frying hardware. For some this was enough to "load the canons" and fire away.
Since I have to work to earn a living and Microsoft doesn't pay me to correct their mistakes and flaws, I guess I'll need about a week until I can post the results.
“We can not solve our problems with the same level of thinking that created them”
― Albert Einstein
- - - Updated - - -
Don't bother! Reinstall your updates!
Found the culprit!
It's a combination of several "policy" settings that need to harmonize and a handful of other little shit settings, just for fun to make it more complicated.
It's quite quirky! But when it works it works beautifully!
Read my long post.
Will do "destroy & rebuild" to confirm all and then publish all soon.
I'm off now, my head is smoking.